gvfsd-trash crashed with SIGSEGV in g_idle_funcs()

Bug #269612 reported by Kai Arne
8
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: gvfs

just start buntu intrepid ibex 8.10 and the gvfsd-trash crashed

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Disassembly: 0x7f9badb7899c:
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/lib/gvfs/gvfsd-trash
Package: gvfs-backends 0.99.7.1-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: /usr/lib/gvfs/gvfsd-trash --spawner :1.6 /org/gtk/gvfs/exec_spaw/1
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=nb_NO.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-3-generic x86_64
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare

Revision history for this message
Kai Arne (kaiarne5) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
?? () from /lib/libpthread.so.0
?? ()
g_idle_funcs () from /usr/lib/libglib-2.0.so.0
IA__g_main_context_dispatch (context=0x1c95190)

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Andreas Moog (ampelbein) wrote :

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 252174, 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.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.