nautilus crashed with SIGSEGV in g_closure_invoke()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus (Ubuntu) |
Expired
|
Low
|
Unassigned |
Bug Description
Binary package hint: nautilus
I was copying file from external hard drive (USB).
It seems that i launched too many instances of copy from the same hard drive to the same destination.
ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: nautilus 1:2.30.1-0ubuntu1.1
ProcVersionSign
Uname: Linux 2.6.32-28-generic x86_64
NonfreeKernelMo
Architecture: amd64
CheckboxSubmission: 1368d427e35e94d
CheckboxSystem: edda5d4f616ca79
Date: Sun Feb 13 16:09:12 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
ProcCmdline: nautilus
ProcEnviron:
LANG=fr_FR.utf8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x4cf79e: mov 0x18(%rdi),%rdx
PC (0x004cf79e) 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/
Title: nautilus crashed with SIGSEGV in g_closure_invoke()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers
XsessionErrors:
(polkit-
(gdu-notificat
(update-
visibility: | private → public |
This crash has the same stack trace characteristics as bug #407768. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.