GNOME Bugzilla – Bug 621355
crash in Disk Notifications: Crash during starting Gn...
Last modified: 2010-06-12 11:05:13 UTC
Version: 2.28.1 What were you doing when the application crashed? Crash during starting Gnome Desktop. dmesg: [ 140.551538] gvfs-gdu-volume[2042]: segfault at 18 ip 00007fd443058298 sp 00007fffea9733c0 error 4 in libgdu.so.0.0.0[7fd44304c000+23000] [ 144.341899] gvfs-gdu-volume[2069]: segfault at 18 ip 00007f438e8b3298 sp 00007fffe10f69d0 error 4 in libgdu.so.0.0.0[7f438e8a7000+23000] Note: - there are some NULL pointer dereferences on model->priv->pool since the "pool" property seems not to be set. palimpsest crashes likely due to the same cause: Program received signal SIGSEGV, Segmentation fault. gdu_pool_get_presentables (pool=0x0) at gdu-pool.c:1381 1381 ret = g_list_copy (pool->priv->presentables); - happened with devicekit-disks-009 - still happens with udisks-1.0.1 as replacement - this might be a misconfiguration to my system. Still, a crash is harder to diagnose than a slightly more explanatory error message. Distribution: Gentoo Base System release 2.0.1 Gnome Release: 2.28.2 2010-05-16 (Gentoo) BugBuddy Version: 2.28.0 System: Linux 2.6.34-gentoo #2 PREEMPT Thu May 20 09:35:38 CEST 2010 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10899000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: oxygen GTK+ Modules: canberra-gtk-module, gnomebreakpad Memory status: size: 179232768 vsize: 179232768 resident: 8335360 share: 6635520 rss: 8335360 rss_rlim: 18446744073709551615 CPU usage: start_time: 1276331474 rtime: 2 utime: 2 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/libexec/gdu-notification-daemon' Traceback (most recent call last): File "/usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.2200.5-gdb.py", line 9, in <module> from gobject import register File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in <module> import gdb.backtrace ImportError: No module named backtrace 0x00007f5cfb43bace in waitpid () from /lib/libpthread.so.0
+ Trace 222365
Thread 1 (process 1989)
Inferior 1 [process 1989] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ---- Critical and fatal warnings logged during execution ---- ** GLib-GObject **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed ** GLib-GObject **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed ** GLib-GObject **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed ** GLib-GObject **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed ----------- .xsession-errors --------------------- warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be available. warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be available. warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be available. warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be available. warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be available. warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be available. warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be available. warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be available. --------------------------------------------------
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. *** This bug has been marked as a duplicate of bug 602697 ***