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 167527 - 'Save as' file name with no extension causes crash on Windows
'Save as' file name with no extension causes crash on Windows
Status: RESOLVED DUPLICATE of bug 112401
Product: GIMP
Classification: Other
Component: General
2.2.x
Other All
: Normal critical
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2005-02-15 21:34 UTC by Dan Eliot
Modified: 2008-01-15 12:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Dan Eliot 2005-02-15 21:34:08 UTC
Steps to reproduce:
1. Use the Save As Dialog, save a graphic with the default filename that comes 
up (UNTITLED).
2. 
3. 


Stack trace:


Other information:
The bug could be fixed easily by changing the default SAVE AS name to 
UNTITLED.XCF instead of just UNTITLED.  This seems like a good safety idea 
anyway, so that is someone is careless and uses the default graphic name, at 
least it will maintain the layers.
Comment 1 Dan Eliot 2005-02-15 21:39:27 UTC
This bug happened on a Windows 98SE system.  I know Win 9x systems are not 
supported, but I think having an extension on the default graphic is logical 
for ALL Operating Systems.
Comment 2 Sven Neumann 2005-02-15 22:03:58 UTC

*** This bug has been marked as a duplicate of 165684 ***
Comment 3 Nathan Summers 2005-02-15 22:31:15 UTC
Not so fast -- there is still a crash going on. This reminds me a lot of bug
#163740.

Reporter, does it appear that a box with an error message tries to come up?
Comment 4 Michael Schumacher 2005-02-15 22:45:58 UTC
Doesn't crash here. I get an error message "Unknow filetype".
Comment 5 Sven Neumann 2005-02-15 23:08:37 UTC
Of course it doesn't crash. The summary of this bug report is completely
misleading (thanks, Nathan). The crash that the user was seeing is just another
occurence of bug #112401. Can't this stupid Wimp theme finally be removed from
the installer if it is causing so much trouble...?
Comment 6 Sven Neumann 2005-02-15 23:13:07 UTC
Bug reporter, please uninstall the GTK+ theme that has been installed from the
GIMP installer. It contains hardcoded fonts which can, under some circumstances,
trigger bug #112401, causing the application to crash. This is triggered by
harmless informative message dialogs such as the one you get when saving without
an extension.
Comment 7 Sven Neumann 2005-02-15 23:14:18 UTC
I'll leave it up to the bug reporter to decide whether he wants his report to
become a duplicate of bug #112401 or rather bug #165684. Please choose one.
Comment 8 Nathan Summers 2005-02-15 23:21:45 UTC
Sven, once again you're out of line with the sarcastic comments.  The summary is
in no way misleading.  You mistake a suggested solution for the bug report.  THe
report is that it crashed.  The solution proposed is to change the default
filename (which is a good idea in its own right, but doesn't solve the
underlying problem.)

You're right in that it's probably bug #163740, which is one of the many
manifestations of bug #112401, but without further info from the reporter, it's
impossible to say for sure, thus the request for info and the NEEDINFO status.
Comment 9 Michael Schumacher 2005-02-16 01:11:36 UTC
AFAIK this theme is now part of GTK+ and the default on Win32...
Comment 10 Sven Neumann 2005-02-16 01:16:06 UTC
About time that we get an installer with GTK+-2.6 then. If the theme is part of
GTK+, we can at least fix it (if that hasn't been done already when it was
included).
Comment 11 Dan Eliot 2005-02-16 01:26:14 UTC
Sorry if my bug report was unclear.  We received two warning/error dialogs in 
Windows 98SE.  One discussing the "San Serif" font issue, which then leads to 
a second dialog and forced closure of GIMP.  If the exact messages are needed, 
I will reproduce the messages tomorrow in my lab.

My suggested solution (more of a workaround I guess) was to simply have an 
extension added to the default "UNTITLED" file name provided by GIMP.  We (my 
students and I) found that we did not get the error when we added .XCF, .GIF, 
or some other appropriate extension to the filename.

It further seemed to me that if GIMP were to have a default, UNTITLED.XCF 
would be a safer default that would help avoid silly user mistakes like 
forgetting an extension.
Comment 12 Dan Eliot 2005-02-16 01:29:37 UTC
Error messages are the same as those mentioned in bug #163740
Comment 13 Nathan Summers 2005-02-16 01:56:02 UTC

*** This bug has been marked as a duplicate of 163740 ***
Comment 14 Sven Neumann 2005-02-16 09:55:20 UTC
Closing as a duplicate of bug #112401. Bug #163740 is resolved INVALID. It
doesn't make any sense to resolve this one as a duplicate of an invalid report.

*** This bug has been marked as a duplicate of 112401 ***
Comment 15 Sven Neumann 2005-02-16 10:02:01 UTC
Dan, your suggestion has already been taken care of (see bug #165684). GIMP 2.4
will automatically add the .xcf extension if none is specified.