gvfsd-trash crashed with SIGSEGV in _dbus_message_iter_check()

Bug #261622 reported by roadrunner777
6
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
Incomplete
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gvfs

I suspect a change in the upstream has caused this, if I had more time I would find it. I am really bussy----EEEEE invalid! HAHAH! Sorry.
Anyway, this is reproducible on 2 different machines and only after upgrading to the latest versions of no less than 52 packages. Something has broken dbus along the way. Not sure what. Probably will be fixed by the time I narrow it down.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/lib/gvfs/gvfsd-trash
Package: gvfs-backends 0.99.5-0ubuntu1
ProcCmdline: /usr/lib/gvfs/gvfsd-trash --spawner :1.14 /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:
 ?? () from /lib/libdbus-1.so.3
 dbus_message_iter_get_arg_type () from /lib/libdbus-1.so.3
 ?? () from /usr/lib/gio/modules/libgvfsdbus.so
 g_main_context_prepare () from /usr/lib/libglib-2.0.so.0
 ?? () from /usr/lib/libglib-2.0.so.0
Title: gvfsd-trash crashed with SIGSEGV in dbus_message_iter_get_arg_type()
Uname: Linux 2.6.27-rc4 i686
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare

Tags: apport-crash
Revision history for this message
roadrunner777 (roadrun777) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:_dbus_message_iter_check (iter=0xb7e01560)
dbus_message_iter_get_arg_type (iter=0xb7e01560)
_g_dbus_bus_list_names_with_prefix (connection=0x8102ac8,
IA__g_main_context_prepare (context=0x80f7210,
g_main_context_iterate (context=0x80f7210, block=1,

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 :

thank you for your bug report. how did you trigger the crash? was that after an upgrade only? could be a mismatch between the version installed and the running one

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