gvfsd-trash crashed with SIGSEGV in g_main_context_prepare()

Bug #268314 reported by Duncan Lithgow
6
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gvfs

I don't know the source of this crash. This is almost identical to bug #268246

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Disassembly: 0xb714a0d9:
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.5 /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=da_DK.UTF-8
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 ?? ()
 g_main_context_prepare () from /usr/lib/libglib-2.0.so.0
 ?? () from /usr/lib/libglib-2.0.so.0
 g_main_loop_run () from /usr/lib/libglib-2.0.so.0
 ?? ()
Title: gvfsd-trash crashed with SIGSEGV in g_main_context_prepare()
Uname: Linux 2.6.27-2-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video

Revision history for this message
Duncan Lithgow (duncan-lithgow) wrote :
description: updated
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
IA__g_main_context_prepare (context=0x86042f0, priority=0xbfb55b88)
g_main_context_iterate (context=0x86042f0, block=1, dispatch=1, self=0x85fb778)
IA__g_main_loop_run (loop=0x86045a8) at /build/buildd/glib2.0-2.18.0/glib/gmain.c:2983
daemon_main (argc=4, argv=0xbfb55d04, max_job_threads=10,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for the bug report. This particular bug has already been reported, but feel free to report any other bugs you find.

Changed in gvfs:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: New → Invalid
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.