nautilus crashed with SIGABRT in raise()

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

Bug Description

Bug follows installation of nvidia-173 driver. nvidia-173 driver was installed in vain attempt of run Ububtu desktop on this clunk laptop, which has a geForce 530 chipset. The Ububtu-2D desktop has been put to sleep, this clunk laptop will not support either Ububtu or gnome desktop, this is gnome-classic running (not very well). I will have to use gnome-classic (no effects) or xfce desktop on this clunk.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: nautilus 1:3.5.5-0ubuntu3
ProcVersionSignature: Ubuntu 3.5.0-10.10-generic 3.5.1
Uname: Linux 3.5.0-10-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.4-0ubuntu6
Architecture: i386
Date: Wed Aug 15 06:56:31 2012
ExecutablePath: /usr/bin/nautilus
GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'800x550+69+24'"
ProcCmdline: nautilus -n
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
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: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
hcmeyer (hcmeyer) 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
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.