Firefox doesn't start until I delete sessionstore.js

VERIFIED INCOMPLETE

Status

()

VERIFIED INCOMPLETE
12 years ago
9 years ago

People

(Reporter: jlp.bugs, Unassigned)

Tracking

2.0 Branch
x86
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

12 years ago
I noticed this problem on two Linux computers. One is running Gentoo Linux and another is running Mandriva Linux 2007. In both cases I have Firefox 2.0.0.1 installed.

Reproducable: always

Steps to reproduce:
1. Have Firefox open with a couple of tabs open
2. Logout of KDE desktop or restart the computer (leave Firefox open)
3. When you come back and log into your desktop Firefox is automatically started by X session management
4. Firefox asks you if you would like to restore session
5. Click Yes

Actual result:
Firefox doesn't start at all and no window with remebered tabs is open.

Expected result:
Firefox should restore the last bowser session and open the tabs.

Workaround:
I had to delete sessionstore.js in my ~/.mozilla/firefox profile folder in order to get Firefox starting again.
(Reporter)

Comment 1

12 years ago
Ups, I made a mistake. Steps 4 and 5 don't happen at all. Firefox just doesn't start. And if you try to start Firefox and have multiple profiles set up it does ask you to select a profile, but if you select a profile which should restore session nothing happens until you delete sessionstore.js for that profile.

Comment 2

12 years ago
1. Can you reproduce this issue on a clean profile with no extensions?
2. Does this also happen when you use a precompiled stock build from mozilla.org?

If 1 is not the case, you might want to figure out which extension is to blame and inform its author. If 2 is not the case, you might want to inform your distro's maintainer that they've introduced a bug which isn't present upstream.

If both 1 and 2 are the case, try setting the pref javascript.options.showInConsole to true in about:config, regularly close Firefox and when the issue happens again the next time, run firefox -jsconsole and report any errors listed in there.

Updated

12 years ago
Severity: major → normal
Keywords: qawanted

Comment 3

11 years ago
Jure: Please reopen this bug when you see this issue again, the answer to both questions from comment #2 is "yes" and you can give the information requested in the third paragraph of comment #2.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → INCOMPLETE

Updated

10 years ago
Keywords: qawanted
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.