nautilus crashed with SIGSEGV in g_type_check_instance_cast()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
crash happens when i plug in my USB3 external drive into usb3 port but not always? this is a new Acer 5755-9674 work out of the box with Ubuntu 12.04. I have had 2 issues USB3 flaky at times and dim brightness keys back words. media key dont work except for volume. no big deal as they have a Cr#& lay out anyways. all other componets work fine. thanks it looks like a good release far better then 11.04. I am impressed with the quality and speed of fixes of this beta. I have not tested DVD drive or WIDI interface. Wish we could fix the The Windows bug on new computers.
Thanks
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: nautilus 1:3.3.91-0ubuntu4
ProcVersionSign
Uname: Linux 3.2.0-19-generic x86_64
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
Date: Sun Mar 18 14:44:03 2012
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
org.gnome.
org.gnome.
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: nautilus -n
SegvAnalysis:
Segfault happened at: 0x7f44b19c2ebc <g_type_
PC (0x7f44b19c2ebc) ok
source "0x16(%r8)" (0x330033706d2e86) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
g_type_
?? () from /usr/lib/
g_closure_invoke () from /usr/lib/
?? () from /usr/lib/
g_signal_
Title: nautilus crashed with SIGSEGV in g_type_
UpgradeStatus: Upgraded to precise on 2012-03-14 (4 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
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 #958592, 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.