After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 84753 - Galeon crashes with certain favicon files
Galeon crashes with certain favicon files
Status: RESOLVED DUPLICATE of bug 56837
Product: galeon
Classification: Deprecated
Component: general
unspecified
Other Linux
: Normal major
: ---
Assigned To: galeon-maint
Yanko Kaneti
Depends on:
Blocks:
 
 
Reported: 2002-06-10 15:48 UTC by Luke Plant
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Luke Plant 2002-06-10 15:48:01 UTC
Problem: Galeon (v 1.2.5, Mozilla 1.0) crashes when loading some pages due
to problem with the favicon file.

Severity:  galeon crashes immediately

Reproducibility: always

Steps to reproduce:
1) Make sure browser automatically downloads favicon file (I can't remember
if there is a galeon option for this)
2) Point browser to:
http://www.cstr.ed.ac.uk/festival


The problem seems to be the favicon.ico file:  
http://www.cstr.ed.ac.uk/favicon.ico

I get this error message when running galeon from command line:

** ERROR **: file io-ico.c: line 342 (DecodeHeader): assertion failed:
(State->LineBuf != NULL)
aborting...
Aborted

When I download the favicon.ico file and attempt to look at it with gthumb,
I get an *identical* error message.  Gimp refuses to open it ("Not a GIcon
file: favicon.ico!"), other conversion utilities either seg fault
(icontopbm) or fail with "failed: 32bit color depth not supported"
(icontoxbm, Sam Barker).  So it appears to be an unusual .ico file, with
32bit colour or something.   The only programs that can actually display
the file (that I've found so far) are gqview and Mozilla (it looks sensible
with them).

Because of the same thing happening in gthumb, this seems to be due to bugs
in another part of Gnome, but not sure quite where (haven't found it
reported anywhere). I'm putting it here as it does cause a major problem
here.  Sorry if that was wrong.
Comment 1 Luke Plant 2002-06-10 16:03:29 UTC
OK, so I figured this was to do with gdk-pixbuf.  Upgraded gdk-pixbuf
to 0.17 (from 0.11), and the problem disappears.  So should there be
some kind of dependency put in - gdk-pixbuf >= 0.17 ?

Comment 2 Yanko Kaneti 2002-06-10 16:20:25 UTC

*** This bug has been marked as a duplicate of 56837 ***
Comment 3 Yanko Kaneti 2002-06-10 16:26:05 UTC
I've upped the dependancy to 0.14.0 the version in redhat 7.3, which
also fixes this