GNOME Bugzilla – Bug 142858
Save state when all windows close
Last modified: 2011-02-14 13:06:17 UTC
If galeon is started in server mode with 'galeon -s', there is no way to exit it except killall galeon-bin (maybe you have a signal to exit cleanly i don't know about?), and therefore the menushortcuts are never saved, and quit from the menu doesn't do it either.
Using "galeon -q" should quit server mode, and hence save state, but that isn't ideal. We should probably save all the state when the last galeon window is closed (history, favicon cache, bookmarks, and accels)
Is it hard to make File/Quit also quit server mode? I looked at the code, but it's all magic CORBA stuff i have no clue how it works. (If you want to close all windows but not exit server mode, there could be a File/Close All added perhaps.)
It would probably be better to save state even more often than that, for example immediately when a bookmark is changed. Debian bug #242786 notes that galeon server processes are very often long lived (I have them running for many days at a time). When this happens, it is very likely that some plugin will cause problems and galeon need to be killed. This will lose any changes to bookmarks made since galeon was started, possibly a few days ago. This has happened on my machine a few times and been reported in the Debian bts before. When it happens, it is increadibly annoying. Since this bug causes data loss, I'd suggest that the severity should be a lot higher.
Bookmarks, history, and the favicon cache are saved every 5 minutes if there have been any changes, so you only lose the last few minutes changes if there is a crash. If you are losing more than that, then it is a separate bug. Saving data when a change happens isn't really a good idea, especially for things such as the history and favicon cache. I think the bug here is that when all windows dissappear, we should save the current state.
*** Bug 143181 has been marked as a duplicate of this bug. ***
I was about to file a new bug to talk about Debian bug <http://bugs.debian.org/308314>, but the solution Crispin proposes for this bug is the very same thing the submitter of the Debian bug is requesting. I'm personally ok with the way session are saved right now, but I must admit that new users have a hard time learning the difference between "quitting" Galeon and closing it's last window.
Loïc, this bug is only relevant for server mode, the report in your debian bug is about normal galeon behaviour. There are quite of a lot of reports similar to you debian bug, but we have decided that they are all WONTFIX...
Thanks for taking the time to report this bug. However, you are using a version that is too old and not supported anymore. Galeon developers won't be fixing or back porting any fixes for this version. Please upgrade to latest stable Galeon version to receive bug fixes. We are sorry it could not be fixed for your version.