segfault induced by user switching

Bug #153381 reported by Ian Jackson on 2007-10-16
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Ubuntu Desktop Bugs

Bug Description

Binary package hint: nautilus

I switched users back and forth a few times during testing of a gutsy d-i 20071016.1 i386 oem install.

One of the users' sessions seems to have failed to shut down properly. I logged in again to be confronted with four warnings of the form
 The panel encountered a problem while loading "OAFID:GNOME_FastUserSwitchApplet"
 The panel encountered a problem while loading "OAFID:GNOME_Deskbar_Applet"
 The panel encountered a problem while loading "OAFID:GNOME_Panel_TrashApplet"
 The panel encountered a problem while loading "OAFID:GNOME_MixerApplet"

I opened a terminal (which worked) and investigated and found that the nautilus from the previous session was spinning on the CPU. It was continuously writing the following message over and over again into nautilus-debug-log.txt:
 0x8177510 2007/10/16 19:10:32.9014 (USER): debug log dumped due to signal 11

I have sent it a SIGSTOP. Please advise what steps I should take to preserve appropriate debug information.

(Launchpad suggested that this might be related to bug 150471. In answer to the question asked there: compiz is not enabled on this system because it has a blacklisted video card.)

Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instuctions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.
If you are using Kubuntu or Xubuntu you can file the crash using "/usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash" in a terminal - where _my_crash_report.crash is the crash you would like to report.

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. Thanks in advance for your cooperation and understanding.

Changed in nautilus:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: New → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers