nautilus crashed with SIGSEGV in g_file_query_info()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
When i launch Nautilus in root, Nautilus crash. I am on Oneiric. See the details from my terminal below:
Initializing nautilus-
(nautilus:7377): GLib-GObject-
(nautilus:7377): GLib-GIO-CRITICAL **: g_file_has_prefix: assertion `G_IS_FILE (file)' failed
(nautilus:7377): GLib-GIO-CRITICAL **: g_file_has_prefix: assertion `G_IS_FILE (file)' failed
Initializing nautilus-gdu extension
** (nautilus:7377): DEBUG: Syncdaemon not running, waiting for it to start in NameOwnerChanged
Thx.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: nautilus 1:3.1.3-0ubuntu1
ProcVersionSign
Uname: Linux 3.0-3-generic i686
Architecture: i386
CrashCounter: 1
Date: Wed Jul 6 14:31:58 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110619)
ProcCmdline: nautilus
ProcEnviron:
PATH=(custom, no user)
LANG=fr_FR.UTF-8
LANGUAGE=fr_FR:en
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x109ce18: movzbl (%eax),%ecx
PC (0x0109ce18) ok
source "(%eax)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%ecx" ok
Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
?? () from /lib/i386-
?? () from /usr/lib/
?? () from /usr/lib/
g_file_query_info () from /usr/lib/
?? () from /usr/lib/
Title: nautilus crashed with SIGSEGV in g_file_query_info()
UpgradeStatus: Upgraded to oneiric on 2011-07-05 (1 days ago)
UserGroups:
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 #777611, 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.