Nautilus segmentation fault in libcairo.so.2

Bug #637994 reported by Terrax
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: nautilus

After todays updates, my background won't load like if the gnome startup procedure hangs. Gnome also tries to start multible nautilus, but fails in segmentation faults.

My dmesg gets spammed with errors like:
[ 1844.523907] show_signal_msg: 4 callbacks suppressed
[ 1844.523912] nautilus[4562]: segfault at 4 ip b7097b36 sp bfb6b0e0 error 4 in libcairo.so.2.11000.0[b707e000+ae000]
[ 1844.941380] nautilus[4569]: segfault at 4 ip b700cb36 sp bfca2bc0 error 4 in libcairo.so.2.11000.0[b6ff3000+ae000]
[ 1845.349670] nautilus[4576]: segfault at 4 ip b7100b36 sp bff8c8a0 error 4 in libcairo.so.2.11000.0[b70e7000+ae000]
[ 1845.771784] nautilus[4583]: segfault at 4 ip b7196b36 sp bfca3060 error 4 in libcairo.so.2.11000.0[b717d000+ae000]
[ 1846.210631] nautilus[4592]: segfault at 4 ip b7086b36 sp bf9b1650 error 4 in libcairo.so.2.11000.0[b706d000+ae000]
[ 1846.629666] nautilus[4599]: segfault at 4 ip b70e0b36 sp bfaf0890 error 4 in libcairo.so.2.11000.0[b70c7000+ae000]
[ 1847.038234] nautilus[4606]: segfault at 4 ip b70f5b36 sp bfede030 error 4 in libcairo.so.2.11000.0[b70dc000+ae000]

It is easy to reproduce the bug, by opening nautilus followed by gnome-settings-daemon.
I am quite sure this bug was introduced with nautilus 1:2.31.92-0ubuntu1.

The bug is present with and without compiz.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: nautilus 1:2.31.92-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-20.29-generic-pae 2.6.35.4
Uname: Linux 2.6.35-20-generic-pae i686
Architecture: i386
Date: Tue Sep 14 13:53:09 2010
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta i386 (20100901.1)
ProcEnviron:
 LANG=da_DK.utf8
 SHELL=/bin/bash
SourcePackage: nautilus

Revision history for this message
Terrax (tball-es) wrote :
Revision history for this message
Pedro Villavicencio (pedro) 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 instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

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

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 (Ubuntu):
importance: Undecided → Medium
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.