nautilus crashed with SIGSEGV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Tried to open a folder with sudo privileges on an external hard drive using 'gksudo nautilus /media/
Command returned:
Initializing nautilus-gdu extension
** (nautilus:31312): DEBUG: Syncdaemon not running, waiting for it to start in NameOwnerChanged
Then exited
Description: Ubuntu oneiric (development branch)
Release: 11.10
nautilus:
Installed: 1:3.1.3-0ubuntu2
Candidate: 1:3.1.3-0ubuntu2
Version table:
*** 1:3.1.3-0ubuntu2 0
500 http://
100 /var/lib/
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: nautilus 1:3.1.3-0ubuntu2
ProcVersionSign
Uname: Linux 3.0.0-5-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Tue Jul 19 22:32:07 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110705.1)
ProcCmdline: nautilus /media/Media
ProcEnviron:
PATH=(custom, no user)
LANG=en_GB.UTF-8
LANGUAGE=en_GB:en
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f0fb88ad17a: movlpd (%rsi),%xmm2
PC (0x7f0fb88ad17a) ok
source "(%rsi)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%xmm2" ok
Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
?? () from /lib/x86_
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: nautilus crashed with SIGSEGV
UpgradeStatus: Upgraded to oneiric on 2011-07-17 (2 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 #805968, 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.