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 317570 - Crashes on new image in XP
Crashes on new image in XP
Status: RESOLVED NOTGNOME
Product: GIMP
Classification: Other
Component: General
2.2.x
Other Windows
: High critical
: ---
Assigned To: GIMP Bugs
GIMP Bugs
: 320635 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-09-30 03:51 UTC by Carla
Modified: 2008-01-15 13:01 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Carla 2005-09-30 03:51:17 UTC
Steps to reproduce:
1. Start GIMP
2. New Image
3. OK the size, etc. (default options in my case)
4. gimp-2.2 needs to close, send error report, yada yada yada.  Happens every time.


Stack trace:
Sorry...  Windows won't let me copy it, and I certainly don't want to type it
all out by hand.  

Error Signature
AppName: gimp-2.2.exe     AppVer: 0.0.0.0     ModName: libglib-2.0.0.dll
ModVer: 2.6.6.0           Offset: 0004117d

Exception code 0xc0000005

Hope that gives people something to go on.  

Other information:
Today, I've had this happen on two separate x86 machines running XP.  Upgraded
GIMP from 2.2.4 to 2.2.6 to see if the problem would be corrected, but it wasn't
and is still reproducible.  (Uninstalled 2.2.4 before installing 2.2.6)  Both
have GIMP, GTK 2.6.9, GIMP help, GIMP animation package, and Gaim (which also
uses GTK, but the error happens whether Gaim is running or not).  Can provide
more complete computer statistics on request.
Comment 1 Sven Neumann 2005-09-30 12:43:20 UTC
This isn't by any chance the well-known problem that is dealt with in the FAQ
(http://gimp-win.sourceforge.net/faq.html) and also in bug #304702 ?
Comment 2 Carla 2005-09-30 13:07:03 UTC
I don't think it is.  I don't have MS Sans Serif set as a default font for
anything, anywhere, and this is happening without any font warning messages and
before I open the GIMP text editor.  (Also, it's XP, not NT4 nor Me nor 9x.  And
my locale isn't China.  Just so that's cleared up.)
Comment 3 weskaggs 2005-09-30 15:58:31 UTC
This could be bug #311141, whose effects on GIMP are described in bug #312872. 
The workaround suggested there is to try removing the line that says
"appears-as-list" from your gtkrc file (not sure where that is located on a
Windows system).  Please try that, if you can.
Comment 4 Sven Neumann 2005-09-30 22:20:43 UTC
Setting to NEEDINFO until the bug reporter has tried the suggested workaround
and reported back.
Comment 5 Carla 2005-10-03 22:07:04 UTC
I found the gtkrc file in <C:\Documents and Settings\mylogin\.gimp-2.2>.  There
is no "appears-as-list" line in that file.  
Comment 6 Michael Schumacher 2005-10-04 16:05:30 UTC
There is another one, somewhere in the GTK+ installation directory, which is
located in %CommonProgramFiles%
Comment 7 Carla 2005-10-07 00:51:08 UTC
There are 7 copies of gtkrc in C:\Program Files\Common Files\GTK\2.0\ ; 4 called
simply gtkrc, 1 called gtkrc.old, 1 called gtkrc.plain, and 1 called
gtkrc.gtkwimp.  The one called gtkrc.gtkwimp, located in C:\Program Files\Common
Files\GTK\2.0\share\themes\Default\gtk-2.0, is the only one that has
"appears-as-list" in it.  Commenting this line did nothing -- GIMP still crashed
when I tried to make a new image.  
Comment 8 weskaggs 2005-10-07 16:11:26 UTC
Thanks for the info
Comment 9 Mariano Kamp 2005-11-03 09:51:28 UTC
I also ran in the same bug, using Win XP, checked the fonts, they are all
Trebuchet or Tahoma.
Btw. you can see the new image window first and then it crashs.
You can also open an image add a new layer, resize it, get rid of the original
layer and start working.

I have GTK+ 2.6.9 rev a.

A file containing "appears-as-list" is according to google desktop not indexed
on my computer.
I am also running a Windows-Search and will feed back if that turns something
up, otherwise it also came back empty handed.
Comment 10 weskaggs 2005-11-03 19:22:14 UTC
*** Bug 320635 has been marked as a duplicate of this bug. ***
Comment 11 weskaggs 2005-11-03 19:27:33 UTC
Note that the reporter of bug 320635 says that he developed this problem with a
previously working GIMP, after installing OpenOffice.org, which apparently
upgraded Gtk+ to 2.6.9 rev a.  So this would seem to point suspicion toward the
Gtk+ installation.

Anyway, since three people have now reported what seems to be the same bug, I am
going to go ahead and confirm.
Comment 12 Mike Laporte 2005-11-04 01:41:28 UTC
Found that it only crashes if the width of the new image is greater than the
height ... 

Examples: 420 wide X 300 height = crash
          420 X 420 = no crash
          420 X 440 = no crash

Hope this helps.
Comment 13 weskaggs 2005-11-04 15:04:12 UTC
Well, that's bizarre.  Mike, I presume you tried several different combinations,
and ruled out that it's, say, height < 360, or something like that, that is
causing the crash?

One thing that would be very useful would be for you, or one of the other people
experiencing this bug, to try reinstalling the Gtk+ package from
gimp-win.sourceforge.net, and reporting back whether it makes the problem go away.
Comment 14 Mariano Kamp 2005-11-04 15:37:41 UTC
Tried that. Works ;-)
Comment 15 Mike Laporte 2005-11-04 16:40:50 UTC
Ok, it gets weirder... using 420 for width, I played around with the height and
found that anything below 385 would crash GIMP, anything above would work.  If I
up the width to 500, then nothing seems to work, whether the height is greater
or lower... (i tried 500x400, 500x480,500x500,500x510,500x600).

I also noticed that the GIMP crashes after displaying the window, but before
updating the control menu icon (top left).  When it works, it changes from the
default GIMP icon to a scaled down version of the blank image.

I'll see about re-installing GTK+...
Comment 16 Mariano Kamp 2005-11-04 16:45:55 UTC
I already did reinstall and it works fine now.
Comment 17 Mike Laporte 2005-11-04 17:31:58 UTC
10-4.  I did too (GTK+ 2.6.9), and all is well now.

Thanks!
Comment 18 weskaggs 2005-11-04 17:36:14 UTC
Okay, I think we have sufficient evidence that OpenOffice is responsible for
this problem.  I am going to resolve this bug report as NOTGNOME and have opened
a bug report for OO.o, pointing to this one.  The bug report is

http://www.openoffice.org/issues/show_bug.cgi?id=57371

Thanks for helping to pin this down.
Comment 19 weskaggs 2005-11-04 18:34:52 UTC
To follow up, it seems that OO.o actually has nothing to do with this problem --
the offending "Gtk+ 2.6.9 rev a" apparently came along with Gaim instead.
Comment 20 Mike Laporte 2005-11-04 21:52:38 UTC
Well, I cannot dispute this, I do have GAIM installed and I cannot say beyond a
doubt that I had tried creating a new image in GIMP since GAIM's installation. 
I just happened to try it after OO.o's installation.

Cheers!