nautilus crashed with SIGSEGV in dbus_connection_unregister_object_path()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
crash
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: nautilus 1:3.4.0-0ubuntu2
ProcVersionSign
Uname: Linux 3.2.0-23-generic i686
ApportVersion: 2.0.1-0ubuntu3
Architecture: i386
CrashCounter: 1
Date: Sat Apr 14 20:19:40 2012
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
org.gnome.
org.gnome.
org.gnome.
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120408)
ProcCmdline: nautilus -n
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x321bf84: mov 0x18(%eax),%esi
PC (0x0321bf84) ok
source "0x18(%eax)" (0x0000384e) not located in a known VMA region (needed readable region)!
destination "%esi" ok
Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
?? () from /lib/i386-
?? () from /lib/i386-
dbus_connectio
?? () from /usr/lib/
?? () from /usr/lib/
Title: nautilus crashed with SIGSEGV in dbus_connection
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
XsessionErrors: (compiz:1815): GConf-CRITICAL **: gconf_client_
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 #972826, 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.