nautilus crashed with SIGSEGV in g_datalist_id_set_data_full()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus-actions (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
Binary package hint: nautilus-actions
nautilus crash when booting probably because of dropbox
ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: nautilus-actions 2.30.0-0ubuntu1
ProcVersionSign
Uname: Linux 2.6.32-19-generic i686
NonfreeKernelMo
Architecture: i386
CheckboxSubmission: 453bb42ee10eb5b
CheckboxSystem: edda5d4f616ca79
CrashCounter: 1
Date: Wed Apr 7 23:24:05 2010
Disassembly: => 0x288a400: Cannot access memory at address 0x288a400
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
ProcCmdline: nautilus --sm-client-id 101216fbf4301db
ProcEnviron:
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x288a400: Cannot access memory at address 0x288a400
PC (0x0288a400) not located in a known VMA region (needed executable region)!
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: nautilus-actions
StacktraceTop:
?? ()
?? () from /usr/lib/
g_datalist_
?? () from /usr/lib/
g_object_unref () from /usr/lib/
Title: nautilus crashed with SIGSEGV in g_datalist_
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
visibility: | private → public |
StacktraceTop: id_set_ data_full () from /lib/libglib- 2.0.so. 0 libgobject- 2.0.so. 0 libgobject- 2.0.so. 0 file_info_ list_free (files=0x9881d30)
?? ()
g_datalist_
?? () from /usr/lib/
g_object_unref () from /usr/lib/
nautilus_