GNOME Bugzilla – Bug 687045
Window mode not saved on Logoff event
Last modified: 2012-10-29 18:51:52 UTC
How to reproduce: ================= Use case 1: Switch from Single-Window Mode to Multi Window Mode ---------------------------------------------------------------- 1. Uncheck Windows/Single Window Mode to switch to Multi Window Mode. 2. In the operating systems main menu logoff. Use case 2: Switch from Multi Window Mode to Single Window Mode ---------------------------------------------------------------- 1. Check Windows/Single Window Mode to switch to Single Window Mode. 2. In the operating systems main menu logoff. Expected result: ================ The next time GIMP starts in Multi Window Mode (use case 1) or Single Window Mode (use case 2). Actual result: ============== On Linux (Gnome 2.30, KDE) and Windows 7: ------------------------------------------ On Windows a short message window pops up on Logoff, but it closes to fastly to be read. The Window mode settings get lost, e.g. the next time GIMP starts in Single Window Mode (use case 1) or Multi Window Mode (use case 2). On Mac OS X 10.6.8: ------------------- GIMP stops the Logoff, Reboot or Shutdown process. 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.
Why is this a separate bug? GIMP handles none of these events, and all the symtomps caused are just side effects of bug #687044.
Indeed both bugs were found during the same test. I filed them separately because they describe different symptoms: bug #678044 is about the data loss on aborting GIMP, this one about losing the Window Mode. If it's better to handle I had no problems I they were filed together in bug #680744.
Correction: If it's better to handle I had no problems I they were filed together in bug #678044.
Yeah, please let's handle them together. It's the same bug, just different symtoms.
*** This bug has been marked as a duplicate of bug 678044 ***
Sorry, thick fingers ;-) *** This bug has been marked as a duplicate of bug 687044 ***