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 381107 - GIMP crashes when first action is to create a new file
GIMP crashes when first action is to create a new file
Status: RESOLVED DUPLICATE of bug 314529
Product: GIMP
Classification: Other
Component: General
2.2.x
Other Windows
: Normal critical
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2006-12-01 00:46 UTC by Terry Lee Sanders
Modified: 2008-01-15 13:17 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Terry Lee Sanders 2006-12-01 00:46:17 UTC
Steps to reproduce:
1. Open GIMP
2. Choose "File/New"
3. (Do not open an existing file first--once a file has been opened--even if it is subsequently closed--creating a new file appears to proceed normally.


Stack trace:


Other information:
The new file's screen pops up, but the disk continues to access for several seconds, then Windows says the program has to shut down and offers to send a report to Microsoft.  I have a copy of the dump if it would be useful; however, your instructions on Bug Buddy seem to assume Linux and/or the Gnome desktop.  If I have misread the instructions, please let me know.
Comment 1 Terry Lee Sanders 2006-12-01 00:51:24 UTC
I thought I had stated in the above report that I am using the Windows XP version of GIMP, but it is not listed above.  Sorry about that.  If this is the wrong forum to report this problem, please let me know.

It also appears this was reported as a Bug Buddy problem, not a GIMP problem.  If so, please do accept my apologies.
Comment 2 Tor Lillqvist 2006-12-01 09:29:30 UTC
No, the "dump" produced by Windows is usually not useful.

As far as I know nobody else has reported something like this before.

One thing you could do is run gimp with output going to a log file. Unfortunately,  how to do that is not straightforward, you must know what you are doing. But as you seem to be a GNOME user, too, maybe you are ;)

So, do this: open a command prompt window, and make sure your PATH includes the GIMP's "bin" folder, and GTK+'s "bin" folder if they aren't the same. Then run gimp with the command: 
        gimp-2.2 --verbose >gimp.log 2>&1

(Yes, that *is* cmd.exe syntax.)

After gimp has crashed, do you see any error message in the gimp.log file?
Comment 3 Michael Schumacher 2006-12-01 09:44:03 UTC
Could this be a duplicate of bug #314529?
Comment 4 Sven Neumann 2006-12-01 10:59:57 UTC
Setting to NEEDINFO until the bug reporter has told us what version of GIMP and GTK+ he's using and where he got them from.
Comment 5 Terry Lee Sanders 2006-12-02 15:44:41 UTC
re comments so far

GIMP is version 2.2.13, downloaded from the main site.  I received a CD-ROM from a friend, and installed an earlier version from that.  2.2.13 was an update to that earlier version.  I will try to find the original disk if the ORIGINAL version might help you.

I am not sure how to determine the version of GTK+ I have.  The folder titles include one titled "2.0" and another titled "2.4.0"  Since the only thing I do with GTK+ is install updates to GIMP (which is done automatically with Windows XP), I don't know how to start it independently, much less check the version.

As you can tell, I am not exactly a skilled Gnome Desktop user.  Sorry to be so vague--anything I can do to make more sense of this, let me know.
Comment 6 Michael Schumacher 2007-01-14 14:58:48 UTC
You could read bug 314529 which was linked to above and try to figure out if the problem described there applies to your system.
Comment 7 Terry Lee Sanders 2007-01-14 17:50:21 UTC
re Michael Schumacher's comment #6

I reviewed 314529, including the comment giving reinstallation instructions.  Per those instructions I uninstalled GTK+ and downloaded the latest version, then reinstalled GIMP 2.2.13.  I then successfully opened a new file.

For general information, I learned during the uninstall that my version of GTK+ was 2.9, revision a.

Thank you all for your help.
Comment 8 Michael Schumacher 2007-01-14 19:10:20 UTC

*** This bug has been marked as a duplicate of 314529 ***