GNOME Bugzilla – Bug 687044
GIMP does not handle Logoff, Reboot and Shutdown events
Last modified: 2018-05-24 13:22:41 UTC
How to reproduce: ================= Use case 1: ----------- 1. Create a new file. 2. Edit this file. 3. In the operating systems main menu select Logoff, Reboot or Shutdown. Use case 2: ----------- 1. Open an existing file. 2. Edit this file. 3. In the operating systems main menu select Logoff, Reboot or Shutdown. Expected result: ================ 1. GIMP interrupts the Logoff, Reboot or Shutdown process. 2. GIMP asks the user to save the unsaved files. 3. After the files are saved and GIMP quits, the Logoff, Reboot or Shutdown process is continued. Actual result: ============== On Linux (Gnome 2.30): ---------------------- A message window shortly pops up, telling that GIMP doesn't support saving the settings. GIMP is shut down without confirmation. All opened files get lost. There are no differences between Single and Multi Window Mode. On Linux (KDE 4.8): ------------------- GIMP is shut down without confirmation. All opened files get lost. There are no differences between Single and Multi Window Mode. On Windows 7, 32 bit: --------------------- A message window shortly pops up, but cannot be read, as it is closed too fastly before it can show its message. GIMP is shut down without confirmation. All opened files get lost. There are no differences between Single and Multi Window Mode. On Mac OS X 10.6.8: ------------------- _In Single Window Mode:_ Only if the GIMP window is not minimized it's brought into the foreground. _In Multi Window Mode:_ Only if the GIMP window is not minimized it's brought into the foreground. Otherwise only the GIMP menubar and either the toolbox or the dock windows show up, but not the main window and the other floating window (dock windows or toolbar). GIMP stops the Logoff, Reboot or Shutdown process, but doesn't tell the user to save all dirty files. After a short period of time OS X tells 'You haven't been logged out because the application GIMP failed to quit. To try logging out again, quit GIMP and choose Apple menu > Log Out'. It happens always.
Increasing severity to 'Critical' as data gets lost.
No way.
I'm sorry, but I don't understand this. I know, the use case doesn't occur that much and the priority 'Normal' reflects this. The reason why I filed this bug is the data loss. The site 'A bugs life cycle' ( https://bugzilla.gnome.org/page.cgi?id=fields.html#importance) holds severity 'Critical' for this. Nowadays every application on every OS or windowing system I checked asks the user to save his data and leave the application in a clean way on logoff. Can you tell a bit more about the reasons for just 'No way', please?
I would even say this is an enhancement request. Shutting down the machine without saving your documents, of course that's data loss. But, um, it's a but like pulling the power plug. How do these events get delivered at all, and by what system? I have never seen them.
On linux the session manager sends a SaveYourself event, it looks like GnomeClient handles this but I don't see anything in pure gtk: http://developer.gnome.org/libgnomeui/stable/libgnomeui-gnome-client.html#GnomeClient-save-yourself On MacOS the application delegate (assigned using NSApplication) gets sent the applicationShouldTerminate message.
*** Bug 687045 has been marked as a duplicate of this bug. ***
Nowadays people got used to software which can be closed unexpectedly, especially with smartphones and tablets, and applications are expected to save their work when they are asked to. If not mistaken, when this happens, an application receives a SIGTERM signal before it is fully terminated, no? Of course, the GNOME API from comment 5 looks nicer, but reacting to system signals appropriately could be a start. I believe this report is quite tied with bug 138373 (autosave) of bug 148931 (save before crash). Then on next start, if a logout happened on a dirty image, GIMP could propose to restore work-in-progress.
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gimp/issues/431.