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 142858 - Save state when all windows close
Save state when all windows close
Status: RESOLVED WONTFIX
Product: galeon
Classification: Deprecated
Component: User interface
1.3.14
Other Linux
: Normal minor
: ---
Assigned To: galeon-maint
galeon-maint
: 143181 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2004-05-20 18:12 UTC by Mikael Magnusson
Modified: 2011-02-14 13:06 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Mikael Magnusson 2004-05-20 18:12:46 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.
Comment 1 Crispin Flowerday (not receiving bugmail) 2004-06-03 21:50:19 UTC
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)
Comment 2 Mikael Magnusson 2004-06-17 00:19:29 UTC
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.)
Comment 3 Mark Howard 2004-07-04 12:47:36 UTC
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. 
Comment 4 Crispin Flowerday (not receiving bugmail) 2004-09-10 17:56:04 UTC
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.
Comment 5 Crispin Flowerday (not receiving bugmail) 2004-09-10 17:57:06 UTC
*** Bug 143181 has been marked as a duplicate of this bug. ***
Comment 6 Loïc Minier 2005-05-26 19:03:53 UTC
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.
Comment 7 Crispin Flowerday (not receiving bugmail) 2005-05-26 19:10:32 UTC
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...
Comment 8 Akhil Laddha 2011-02-14 13:06:17 UTC
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.