nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__BOXED() ejecting SD card
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: nautilus
This is the trace requested in bug#683972.
I opened a new bug because a) I do not know how to manually divert the apport output to an existing bug and b) maybe this is a different issue.
The bug happened when ejecting (right-click then choose "safely eject drive") a digital camera SD card.
In the log I have
Jan 11 08:28:23 romano-asus kernel: [ 6648.776803] usb 1-5: USB disconnect, address 10
Jan 11 08:28:23 romano-asus kernel: [ 6648.847565] nautilus[1774]: segfault at 40 ip 0808a882 sp bff5b9d0 error 4 in nautilus[
Jan 11 08:28:58 romano-asus dbus-daemon: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.227" (uid=1153 pid=9784 comm="nautilus) interface=
ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: nautilus 1:2.32.0-0ubuntu1.1
ProcVersionSign
Uname: Linux 2.6.35-24-generic i686
Architecture: i386
Date: Tue Jan 11 08:28:24 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Release i386 (20100429.4)
ProcCmdline: nautilus
ProcEnviron:
PATH=(custom, user)
LANG=en_GB.utf8
SHELL=/bin/zsh
SegvAnalysis:
Segfault happened at: 0x808a882: mov (%esi),%eax
PC (0x0808a882) ok
source "(%esi)" (0x00000040) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
?? ()
g_cclosure_
?? () from /usr/lib/
g_closure_invoke () from /usr/lib/
?? () from /usr/lib/
Title: nautilus crashed with SIGSEGV in g_cclosure_
UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare tape video
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #699664, 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.