GNOME Bugzilla – Bug 631282
[Win32] Gnumeric closes on a minimise
Last modified: 2018-02-10 03:41:25 UTC
With Gnumeric having been automatically started with a particular spreadsheet in the startup group in windows, if I click on the minimise control (3rd from top right) the application closes instead of minimising. I have seen this behaviour many times - it may be 100% repeatable on my PC, and the only factor that is key seems to be that Gnumeric was started in the way I described. [The actual startup item was a shortcut to "C:\Users\Liam\Documents\_Trading\My system\2010'.gnumeric". (clicking on the minimise control works normally if Gnumeric has been started manually, even if it was by clicking on the same startup item).
Sounds weird.
Created attachment 183489 [details] print screen of the task manager window
I want to confirm Bug 631282 When I start gnumeric first and then: [File -> Open -> Filename.xls] everything is ok. When I minimize program I can see button on windows taskbar. But when I click in windows explorer file *.xls without opening gnumeric first, file is loading, but when I click on minimize button program is closing, no button is visible on windows taskbar and program don't ask me about saving or discard changes in file even if I do something with data in it. When I open and minimize in this way two, three or more files in Windows task manager every file is leaving working process (see atached picture).
So according to the image of the task manager, Gnumeric is _not_ closing or quitting. As asked, the window is just being minimized and Gnumeric continues running. The problem is that you don't seem to get a button on the Windows taskbar. That seems to be a GTK or Windows bug to me.
*** Bug 662134 has been marked as a duplicate of this bug. ***
*** Bug 655089 has been marked as a duplicate of this bug. ***
There appear to be othe rGTK bugs related to the task bar, for example bug #573862 relates to Gimp on Windows and faulty interaction with the taskbar.
In view of bug #573862 this is likely in gtk.
We're moving to gitlab! As part of this move, we are closing bugs that haven't seen activity in more than 5 years. If this issue is still imporant to you and still relevant with GTK+ 3.22 or master, please consider creating a gitlab issue for it.