gvfsd-trash crashed with SIGSEGV in g_main_context_prepare()

Bug #257038 reported by FajardXorg
6
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: gvfs

I logged in and a window from wireless network secret kept showing and this is what happen. "crashed report"

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Disassembly: 0xb724b0d9:
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/lib/gvfs/gvfsd-trash
Package: gvfs-backends 0.99.4-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: /usr/lib/gvfs/gvfsd-trash --spawner :1.8 /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=en_US.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.26-5-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message
FajardXorg (rehevoli) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
IA__g_main_context_prepare (context=0x93b2210, priority=0xbf935dc8)
g_main_context_iterate (context=0x93b2210, block=1, dispatch=1, self=0x93a9778)
IA__g_main_loop_run (loop=0x93b2868) at /build/buildd/glib2.0-2.17.6/glib/gmain.c:2928
daemon_main (argc=4, argv=0xbf935f44, max_job_threads=10,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

Changed in gvfs:
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.