nautilus crashed with SIGSEGV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I'm not sure what I did, Nautilus/Files simply crashed while it was open.
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: nautilus 1:3.5.90.
ProcVersionSign
Uname: Linux 3.5.0-17-generic x86_64
ApportVersion: 2.6.1-0ubuntu1
Architecture: amd64
Date: Fri Oct 5 17:08:27 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
b'org.
b'org.
b'org.
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120327)
ProcCmdline: nautilus
SegvAnalysis:
Segfault happened at: 0x7f07f6e18923: mov 0x30(%rbx),%rdi
PC (0x7f07f6e18923) ok
source "0x30(%rbx)" (0x00005657) not located in a known VMA region (needed readable region)!
destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: nautilus crashed with SIGSEGV
UpgradeStatus: Upgraded to quantal on 2012-10-04 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
mtime.conffile.
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 #1054297, 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.