Ubuntu
gvfs package

gvfsd-trash crashed with SIGSEGV in g_idle_funcs()

Bug #263394 reported by zobbychris@hotmail.com on 2008-08-31

This bug report is a duplicate of: Bug #251910: gvfsd-trash crashed with SIGSEGV in g_idle_funcs(). Edit Remove

Affects		Status	Importance	Assigned to	Milestone
	gvfs (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: gvfs

computer zobby04 amd64bit testing alpha4

ProblemType: Crash
Architecture: amd64
Disassembly: 0x7f1b951ea9ac:
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/lib/gvfs/gvfsd-trash
Package: gvfs-backends 0.99.5-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: /usr/lib/gvfs/gvfsd-trash --spawner :1.14 /org/gtk/gvfs/exec_spaw/0
ProcEnviron:
SHELL=/bin/bash
PATH=/home/zobby/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
LANG=fr_FR.UTF-8
Signal: 11
SourcePackage: gvfs
StacktraceTop:
?? ()
?? () from /lib/libpthread.so.0
?? ()
g_idle_funcs () from /usr/lib/libglib-2.0.so.0
g_main_context_dispatch ()
Title: gvfsd-trash crashed with SIGSEGV in g_idle_funcs()
Uname: Linux 2.6.27-2-generic x86_64
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare

Tags:

Revision history for this message

zobbychris@hotmail.com (zobbychris) wrote on 2008-08-31:

Dependencies.txt Edit (2.0 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (10.9 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (791 bytes, text/plain; charset="utf-8")
Registers.txt Edit (918 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (839 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (1.4 KiB, text/plain; charset="utf-8")

Revision history for this message

breize (breize) wrote on 2008-08-31:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 251910, so it 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. Feel free to continue to report any other bugs you may find.