nautilus crashed with SIGSEGV in g_type_check_instance_cast()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
eror occured twice same scenario - latest updates loaded in between errors
a) connected Kindle 2 device
b) recognised device (note this has not occured previously - device previously not recognised at all that I could determine)
c) initiated Calibre (note - not sure whether Calibre has anything to do with crash)
d) device no longer recognised by either Calibre or system
Seems there may be a problem with USB devices from previous errors - however you must be making progress as this is the first time that 12.04 has recognised the Kindle 2 devcie at all
Keep up the good work
Using Dell 6410 - latest bios updated
12.04 LTS - latest updates loaded (as of 29 Feb 2012)
Calibre updates direct via Calibre site (not via repository)
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: nautilus 1:3.3.90-0ubuntu2
ProcVersionSign
Uname: Linux 3.2.0-17-
ApportVersion: 1.93-0ubuntu2
Architecture: i386
Date: Wed Feb 29 22:01:09 2012
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
org.gnome.
org.gnome.
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120125)
ProcCmdline: nautilus -n
ProcEnviron:
LANGUAGE=en_AU:en
PATH=(custom, no user)
LANG=en_AU.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0xb6bd49fe <g_type_
PC (0xb6bd49fe) ok
source "(%edx)" (0xaaaaaaaa) 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 /lib/i386-
Title: nautilus crashed with SIGSEGV in g_type_
UpgradeStatus: Upgraded to precise on 2012-02-18 (10 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
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 #929064, 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.