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 449849 - Large images don't load
Large images don't load
Status: RESOLVED FIXED
Product: gnome-control-center
Classification: Core
Component: [obsolete] about-me
2.19.x
Other All
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-06-21 18:53 UTC by David Ronis
Modified: 2008-02-13 00:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description David Ronis 2007-06-21 18:53:51 UTC
Please describe the problem:
I've noticed this in several applications recently (gnome-about-me, pidgin, evolution-contacts).  If I try to change my image I get a popup allowing me to select a file.  Selecting a small image works but selecting a large (color) one fails (In evolution's contact editor, I get a query the the image is large and should it be resized).  What happens is that the top 1/5-1/10'th of the image looks right, while the rest is dark.

Two images that work are black & white, 19242 (JPG) and  98620 (GIF) bytes long.

One that doen't work is color 379735 (JPG) bytes long.


Steps to reproduce:
1. System->Preferences->About Me
2. double click on the image
3. in the select file popup choose a new image.


Actual results:


Expected results:


Does this happen every time?
yes


Other information:
I'm following garnome's svn trunk.  My base system has GNOME-2.6 installed and things work properly here.
Comment 1 David Ronis 2007-09-26 17:17:00 UTC
I've just upgraded to GNOME 2.20.0.  The problem is still here; however, I've noticed that the login-photo tool (System->Preferences->Login Photo) works with the same image (I don't know if it was broken earlier).  I bet that it's doing less (or no) file reduction.

Comment 2 David Ronis 2008-02-13 00:22:40 UTC
I just upgraded to 2.21.91--the problem seems to have been fixed.
I'm going to close this.