nautilus crashed with SIGSEGV in g_closure_invoke()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: nautilus
I was copying files off of a USB hard drive into my home folder. I then plugged in my thumb drive and copied a folder of music from the thumb drive. I clicked on a folder of digital pictures on the thumb drive and it did not select so i clicked a few more times to try and select it. I thought compiz was going to crash so I tried moving the window to see if that was what happened but the window responded. The contents on the window however did not. Then I got the crash report window after nautilus disappeared.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: nautilus 1:2.32.
ProcVersionSign
Uname: Linux 2.6.38-7-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Sat Apr 2 09:24:41 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110330)
ProcCmdline: nautilus
ProcEnviron:
LANGUAGE=en_US:en
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x4d4c8e: mov 0x18(%rdi),%rdx
PC (0x004d4c8e) ok
source "0x18(%rdi)" (0x00000018) not located in a known VMA region (needed readable region)!
destination "%rdx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
?? ()
?? ()
?? ()
g_closure_invoke () from /usr/lib/
?? () from /usr/lib/
Title: nautilus crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
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 #711429, 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.