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 651155 - Targa image file: Icon has zero width
Targa image file: Icon has zero width
Status: RESOLVED OBSOLETE
Product: gdk-pixbuf
Classification: Platform
Component: loaders
2.23.x
Other Linux
: Normal normal
: ---
Assigned To: gdk-pixbuf-maint
gdk-pixbuf-maint
Depends on:
Blocks:
 
 
Reported: 2011-05-26 14:21 UTC by mazes80
Modified: 2016-12-28 18:08 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
File from the crack attack project (256.04 KB, image/x-tga)
2011-05-26 14:21 UTC, mazes80 		Details
File issued from the pacmanarena project (192.04 KB, image/x-tga)
2011-05-26 14:22 UTC, mazes80 		Details

Description mazes80 2011-05-26 14:21:03 UTC 
Created attachment 188672 [details]
File from the crack attack project

Images used in various project were previously successfully handled by the gdk-pixbuf loaders.
A regression happened for those files possessing incorrect header (I don't know if it's invalid or just not well formed), but I can't exactly remember the version of gdk-pixbuf which introduced it.
At least I tested on my gentoo host with versions 2.21.1 and 2.23.3: the thrown exception is the same: Icon has zero width.

You can see more details about this on the gentoo bug I reported:
http://bugs.gentoo.org/show_bug.cgi?id=366313

This bug has two files attached one issued from the pacmarena and one from the crack-attack projects.
Comment 1 mazes80 2011-05-26 14:22:20 UTC 
Created attachment 188673 [details]
File issued from the pacmanarena project
Comment 2 Gilles Dartiguelongue 2016-01-05 23:48:42 UTC 
mazes sent me an update on December 24th, saying the issue is fixed for him with gdk-pixbuf in gentoo. This fix seems to have landed in 2.30+ releases.
Comment 3 Bastien Nocera 2016-12-28 18:08:55 UTC 
This works fine indeed.