Closed
Bug 373948
Opened 18 years ago
Closed 18 years ago
Camino didn't set PreviousSessionTerminatedNormally to NO on start-up
Categories
(Camino Graveyard :: Preferences, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 373949
People
(Reporter: fishywang, Unassigned)
Details
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en; rv:1.8.1.2pre) Gecko/20070223 Camino/1.1b
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en; rv:1.8.1.2pre) Gecko/20070223 Camino/1.1b
PreviousSessionTerminatedNormally in org.mozilla.Camino.plist is used by Camino on startup to determine whether it need to restore (crashed) session for user.
As in my understanding about this logic, the properly behavior should be:
1. Camino set its value to NO on start-up
2. Camino set its value to YES on clean quit
As a result of this behavior, after Camino normally quits, its value is YES and didn't need to be restored next start. And if Camino quitted unclean (crashed, forced quit, etc.), it have no chance to set it to YES, so it's NO, and in the next start-up it can restore the session.
Reproducible: Always
Steps to Reproduce:
1.Start Camino and quit it normally
2.execute 'defaults read org.mozilla.Camino PreviousSessionTerminatedNormally' in Terminal, and it prints 'YES'
3.Start Camino again, and keep it running
4.execute 'defaults read org.mozilla.Camino PreviousSessionTerminatedNormally' again
Actual Results:
it prints 'YES'
Expected Results:
it should print 'NO'
As a result of this, Camino only restore crashed sessions if I set 'PreviousSessionTerminatedNormally' to 'NO' before starting it. not automatically after any crash. This makes the crash recovery feature unusable.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
Updated•18 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•