nautilus crashed with SIGSEGV in g_main_context_dispatch()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Nautilus crash report came up after launching Home Folder from the launcher bar.
Crash did not happen when I launched it again.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: nautilus 1:3.1.3-0ubuntu1
ProcVersionSign
Uname: Linux 3.0.0-5-generic-pae i686
NonfreeKernelMo
Architecture: i386
CrashCounter: 1
Date: Sun Jul 17 10:12:58 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110705.1)
ProcCmdline: nautilus -n
ProcEnviron:
LANGUAGE=en_GB:en
LANG=en_GB.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x810e88d: mov 0x308(%eax),%eax
PC (0x0810e88d) ok
source "0x308(%eax)" (0xaaaaadb2) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
?? ()
?? () from /lib/i386-
g_main_
?? () from /lib/i386-
g_main_loop_run () from /lib/i386-
Title: nautilus crashed with SIGSEGV in g_main_
UpgradeStatus: Upgraded to oneiric on 2011-07-12 (4 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #804724, 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.