nautilus crashed with SIGSEGV in gtk_widget_destroy()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Not sure what was happening when it crashed - I noticed this after.
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: nautilus 1:3.5.90.
ProcVersionSign
Uname: Linux 3.5.0-21-generic x86_64
ApportVersion: 2.6.1-0ubuntu9
Architecture: amd64
Date: Sat Jan 5 12:30:03 2013
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/nautilus
GsettingsChanges: b'org.gnome.
InstallationDate: Installed on 2010-10-11 (817 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
MarkForUpload: True
ProcCmdline: nautilus -n
SegvAnalysis:
Segfault happened at: 0x7fb392cda60e <gtk_widget_
PC (0x7fb392cda60e) ok
source "(%rbx)" (0x19000000) not located in a known VMA region (needed readable region)!
destination "%rdx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
gtk_widget_destroy () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: nautilus crashed with SIGSEGV in gtk_widget_
UpgradeStatus: Upgraded to quantal on 2012-10-27 (69 days ago)
UserGroups: adm admin cdrom dialout lp lpadmin netdev plugdev sambashare whoopsie
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 #1095873, 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.