firefox crashes after log out or restart when browser.sessionstore.resume_from_crash set to false

Bug #605175 reported by Paulo Marcel Coelho Aragão
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
firefox (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: firefox

Hi

I'm running:

firefox: 3.6.6+nobinonly-0ubuntu0.10.04.1
Ubuntu: Ubuntu 10.04 LTS

This is how this bug shows up:

1. Open firefox, load about:config, set preference browser.sessionstore.resume_from_crash to false
2. Log out or restart
3. Open firefox: it will open and close, automatically, without any intervention
4. Open firefox again: it will open and stay opened

I also tried:

1. Remove ~/.mozilla: the bug happens in the same way
2. Inspect ~/.xsession-errors: no error messages from firefox
3. Log out or restart with firefox closed: the bug doesn't happen
4. Set browser.sessionstore.resume_from_crash to true: the bug doesn't happen
5. Google extensively in search of a method for logging firefox startup but found nothing

Does anybody know how to work around this bug ?

Thanks a lot !

Paulo

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: firefox 3.6.6+nobinonly-0ubuntu0.10.04.1
ProcVersionSignature: Ubuntu 2.6.32-23.37-generic-pae 2.6.32.15+drm33.5
Uname: Linux 2.6.32-23-generic-pae i686
Architecture: i386
Date: Tue Jul 13 16:53:47 2010
FirefoxPackages:
 firefox 3.6.6+nobinonly-0ubuntu0.10.04.1
 firefox-gnome-support 3.6.6+nobinonly-0ubuntu0.10.04.1
 firefox-branding 3.6.6+nobinonly-0ubuntu0.10.04.1
 abroswer N/A
 abrowser-branding N/A
InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Release i386 (20100429.4)
ProcEnviron:
 LANGUAGE=pt_BR:en
 LANG=pt_BR.utf8
 SHELL=/bin/bash
SourcePackage: firefox

Revision history for this message
Paulo Marcel Coelho Aragão (marcelpaulo) wrote :
Revision history for this message
Paulo Marcel Coelho Aragão (marcelpaulo) wrote :

I forgot to say: I'm running Ubuntu 10.04 LTS Netbook Edition

Paulo

Revision history for this message
penalvch (penalvch) wrote :

Paulo Marcel Coelho Aragão, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal:
cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y upgrade && sudo apt-get -y install firefox-dbg && sudo service apport start force_start=1

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line:
gksudo gedit /etc/apport/crashdb.conf

and comment out the line:
'problem_types': ['Bug', 'Package'],

by changing it to:
# 'problem_types': ['Bug', 'Package'],

Save, close, and try to file the crash report again via:
ubuntu-bug /var/crash/_my_crash_report.crash

Please follow https://wiki.ubuntu.com/MozillaTeam/Bugs when you file this crash report so the necessary information is provided.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

Changed in firefox (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.