nautilus crashed with SIGSEGV
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| nautilus (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Got this out of nothing:
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-0ubuntu2
Architecture: amd64
CheckboxSubmission: 0126eb8c2d63dc5
CheckboxSystem: bb422ca46d02494
Date: Wed Oct 10 18:14:48 2012
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
b'org.
b'org.
b'org.
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcCmdline: nautilus -n
SegvAnalysis:
Segfault happened at: 0x7fa9fb00c8b3: mov 0x30(%rbx),%rdi
PC (0x7fa9fb00c8b3) ok
source "0x30(%rbx)" (0x002b76ac) not located in a known VMA region (needed readable region)!
destination "%rdi" ok
SegvReason: reading unknown 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-09-10 (29 days ago)
UserGroups: adm admin cdrom debian-tor dialout lpadmin plugdev sambashare vboxusers
| Jan Simon (jan-simon) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| visibility: | private → public |
| tags: | removed: need-amd64-retrace |
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.