gvfsd-smb crashed with SIGSEGV in g_main_context_dispatch()

Bug #295582 reported by tankdriver
6
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gvfs

I copied tons of data from intrepid to intrepid.

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/lib/gvfs/gvfsd-smb
NonfreeKernelModules: nvidia
Package: gvfs-backends 1.0.2-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: /usr/lib/gvfs/gvfsd-smb --spawner :1.5 /org/gtk/gvfs/exec_spaw/10
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=de_AT.UTF-8
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/libgio-2.0.so.0
 ?? () from /usr/lib/libgio-2.0.so.0
 g_main_context_dispatch ()
 ?? () from /usr/lib/libglib-2.0.so.0
Title: gvfsd-smb crashed with SIGSEGV in g_main_context_dispatch()
Uname: Linux 2.6.27-7-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags: apport-crash
Revision history for this message
tankdriver (stoneraider-deactivatedaccount) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:command_read_cb (source_object=0x15110f0, res=0x150e920, user_data=0x7f511800d660)
async_ready_callback_wrapper (source_object=0x15110f0, res=0x150e920,
read_async_cb (data=<value optimized out>, condition=<value optimized out>,
IA__g_main_context_dispatch (context=0x150d410)
g_main_context_iterate (context=0x150d410, block=1, dispatch=1, self=<value optimized out>)

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in gvfs:
importance: Undecided → Medium
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
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.