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 139572 - Avoid duplicate error windows when loading or saving fails
Avoid duplicate error windows when loading or saving fails
Status: RESOLVED DUPLICATE of bug 92604
Product: GIMP
Classification: Other
Component: Plugins
git master
Other All
: Normal enhancement
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2004-04-09 11:19 UTC by Raphaël Quinet
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Raphaël Quinet 2004-04-09 11:19:27 UTC
When a file plug-in fails to open a file, it usually displays an error
message before exiting.  After that, the GIMP pops up a second window
with another error message such as: "GIMP Message / Opening 'testfile'
failed: Plug-in could not open image".  This second message is
redundant if the plug-in has already popped up its own error window.

To reproduce: "touch empty.png empty.jpg empty.gif" and then try to
load these files.  If the plug-in crashes or exits incorrectly (see
bug #139571), you also get two error messages.

Besides the codes returned by the file plug-ins to indicate success or
failure, we may need to use a special code meaning: "I failed but I
already gave a detailled report to the user about it so please
propagate the error upstream silently."

Alternatively, we could leave the exit codes as they are now and
simply remove the error message "Opening 'testfile' failed: Plug-in
could not open image" and ensure that all error messages from the
plug-ins mention which file could not be opened.  It would also be
nice to modify plug_in_recv_message() in app/plug-in/plug-in.c and
improve the message displayed when a file plug-in has crashed so that
it displays the name of the file that could not be loaded or saved,
but I don't know how this information could be accessed in that
function.

(Note: I thought that a similar bug had been reported earlier, but I
could not find it.)
Comment 1 Sven Neumann 2004-04-09 12:36:01 UTC

*** This bug has been marked as a duplicate of 92604 ***
Comment 2 Raphaël Quinet 2004-04-09 13:07:05 UTC
Thanks for finding the duplicate.  I was searching for bugs related to loading the
files, not saving them.