nautilus crashed with SIGABRT in raise()

Bug #937329 reported by ubername
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
New
Undecided
Unassigned

Bug Description

Just rebooted after today's updates - system is generally unstable though - I regularly get a generic 'System problem' message - so I wouldn't spend a much time on this bug report. I notice quite a few bugs with the same title of this were updated recently, so I nearly just added this to one of those, but they were all for 64 bit arch.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: nautilus 1:3.3.5-0ubuntu3
ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
Uname: Linux 3.2.0-17-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 1.92-0ubuntu1
Architecture: i386
Date: Mon Feb 20 17:35:39 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 org.gnome.nautilus.window-state geometry '640x968+1281+24'
 org.gnome.nautilus.window-state maximized true
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
ProcCmdline: nautilus -n
Signal: 6
SourcePackage: nautilus
StacktraceTop:
 raise () from /lib/i386-linux-gnu/libc.so.6
 abort () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libc.so.6
 __assert_fail () from /lib/i386-linux-gnu/libc.so.6
 _XAllocID () from /usr/lib/i386-linux-gnu/libX11.so.6
Title: nautilus crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to precise on 2012-01-28 (23 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
ubername (ubername) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #905686, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
visibility: private → public
tags: removed: need-i386-retrace
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.