Bug#548723: gvfs: Crashes in GTK file selectors

Erich Schubert erich at debian.org
Mon Sep 28 12:50:38 UTC 2009


Package: gvfs
Version: 1.4.0-1
Severity: minor
Justification: breaks unrelated software

Audacity started crashing on file export, and debugging I found that it's
not just audacity, but all GTK file selectors crash for me now.

For example gedit on file open:
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff0987476 in ?? () from /lib/libdbus-1.so.3
(gdb)  bt
#0  0x00007ffff0987476 in ?? () from /lib/libdbus-1.so.3
#1  0x00007ffff098795a in ?? () from /lib/libdbus-1.so.3
#2  0x00007ffff0976131 in ?? () from /lib/libdbus-1.so.3
#3  0x00007ffff0976179 in ?? () from /lib/libdbus-1.so.3
#4  0x00007ffff0975214 in ?? () from /lib/libdbus-1.so.3
#5  0x00007ffff0976248 in ?? () from /lib/libdbus-1.so.3
#6  0x00007ffff0975214 in ?? () from /lib/libdbus-1.so.3
#7  0x00007fffecdfce53 in ?? ()
   from /usr/lib/gio/modules/libgioremote-volume-monitor.so
#8  0x00007fffece02e86 in ?? ()
   from /usr/lib/gio/modules/libgioremote-volume-monitor.so
#9  0x00007fffece042a6 in ?? ()
   from /usr/lib/gio/modules/libgioremote-volume-monitor.so
#10 0x00007ffff5d0edbd in g_object_newv () from /usr/lib/libgobject-2.0.so.0
#11 0x00007ffff5d0f907 in g_object_new_valist ()
   from /usr/lib/libgobject-2.0.so.0
#12 0x00007ffff5d0fa4c in g_object_new () from /usr/lib/libgobject-2.0.so.0
#13 0x00007ffff6478bd4 in g_volume_monitor_get () from /usr/lib/libgio-2.0.so.0
#14 0x00007ffff712730c in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#15 0x00007ffff5d299e5 in g_type_create_instance ()
   from /usr/lib/libgobject-2.0.so.0
#16 0x00007ffff5d0e74b in ?? () from /usr/lib/libgobject-2.0.so.0
#17 0x00007ffff5d0edbd in g_object_newv () from /usr/lib/libgobject-2.0.so.0

Of course I'm not sure its gvfs to blame, but there is this
libgioremote-volume-monitor in the backtrace. I guess I might be able to
resolve this by a restart, since there might be a daemon persistently
running while I did a system update. Still gvfs should be a bit more robust
here and not crash other applications because of some dbus communication
error?

I understand that this will be hard for you to reproduce.

P.S. I resolved it by killing gvfs-hal-volume-monitor
and gnome-volume-manager.
So indeed it seems that the gvfs libraries got different data via dbus from
the daemon than they were expecting, which lead to the crash?

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.30-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages gvfs depends on:
ii  libc6                         2.9-26     GNU C Library: Shared libraries
ii  libdbus-1-3                   1.2.16-2   simple interprocess messaging syst
ii  libgconf2-4                   2.26.2-3   GNOME configuration database syste
ii  libglib2.0-0                  2.22.0-1   The GLib library of C routines
ii  libhal1                       0.5.13-3   Hardware Abstraction Layer - share
ii  libudev0                      146-3      libudev shared library
ii  x11-utils                     7.4+1      X11 utilities

Versions of packages gvfs recommends:
ii  dbus                          1.2.16-2   simple interprocess messaging syst
ii  exo-utils                     0.3.102-1  Utility files for libexo
ii  gnome-mount                   0.8-2      wrapper for (un)mounting and eject
ii  hal                           0.5.13-3   Hardware Abstraction Layer

Versions of packages gvfs suggests:
ii  gvfs-backends                 1.4.0-1    userspace virtual filesystem - bac

-- no debconf information






More information about the pkg-gnome-maintainers mailing list