GNOME Bugzilla – Bug 602697
Crash in gdu_pool_get_devices at gdu-pool.c line 1345
Last modified: 2012-11-12 21:09:15 UTC
Version: 0.3 What were you doing when the application crashed? booting up Distribution: Unknown Gnome Release: 2.28.0 2009-10-23 (Foresight Linux) BugBuddy Version: 2.28.0 System: Linux 2.6.30.9-4-fl.smp.gcc4.1.x86_64 #1 SMP Wed Nov 4 11:21:22 UTC 2009 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10603000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: nimbus Icon Theme: gnome-brave GTK+ Modules: canberra-gtk-module, gnomebreakpad Memory status: size: 148398080 vsize: 148398080 resident: 7290880 share: 5615616 rss: 7290880 rss_rlim: 18446744073709551615 CPU usage: start_time: 1258968383 rtime: 3 utime: 2 stime: 1 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/libexec/gdu-notification-daemon' Using host libthread_db library "/lib64/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0x7f9abad986e0 (LWP 2741)] 0x00007f9ab90fb9c5 in waitpid () from /lib64/libpthread.so.0
+ Trace 219240
Thread 1 (Thread 0x7f9abad986e0 (LWP 2741))
---- 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 --------------------- (gdu-notification-daemon:2741): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed beagled will run in the background. Use beagle-status to check progress of beagled. For log files check /home/Quigui/.beagle/Log/current-Beagle. [35;01mwarning: No hp: or hpfax: devices found in any installed CUPS queue. Exiting.[0m [01mHP Linux Imaging and Printing System (ver. 3.9.8)[0m [01mSystem Tray Status Service ver. 2.0[0m Copyright (c) 2001-9 Hewlett-Packard Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Could you please install some debugging packages [1], start the application as normal, and reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the Details, now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance! [1] More details can be found here: http://live.gnome.org/GettingTraces
*** Bug 603578 has been marked as a duplicate of this bug. ***
*** Bug 604213 has been marked as a duplicate of this bug. ***
Tried to install those apps without success. Conflicts with glib and gtk.
*** Bug 606131 has been marked as a duplicate of this bug. ***
*** Bug 606187 has been marked as a duplicate of this bug. ***
*** Bug 608641 has been marked as a duplicate of this bug. ***
Bug 608641 has better traces
+ Trace 220351
*** Bug 610422 has been marked as a duplicate of this bug. ***
*** Bug 610476 has been marked as a duplicate of this bug. ***
*** Bug 598065 has been marked as a duplicate of this bug. ***
*** Bug 612829 has been marked as a duplicate of this bug. ***
*** Bug 613285 has been marked as a duplicate of this bug. ***
*** Bug 613505 has been marked as a duplicate of this bug. ***
Confirming
(In reply to comment #1) > Thanks for taking the time to report this bug. > Unfortunately, that stack trace is missing some elements that will help a lot > to solve the problem, so it will be hard for the developers to fix that crash. > Could you please install some debugging packages [1], start the application as > normal, and reproduce the crash, if possible? > > Once bug-buddy pops up, you can find the stacktrace in the Details, now > containing way more information. Please copy that stacktrace and paste it as a > comment here. Thanks in advance! > > [1] More details can be found here: http://live.gnome.org/GettingTraces More traces were send, do they contain enough information? Regards
Maybe this downstream comment could help: http://bugs.gentoo.org/show_bug.cgi?id=309349#c9 "gdu-notification-daemon crashes with a segmentation violation in gdu_pool_get_devices(), because it cannot get a connection to devkit-disks-daemon. This in turn is not started by dbus-daemon (as it is supposed to be), because /usr/libexec/dbus-daemon-launch-helper cannot be executed by user messagebus. gdu_pool_get_devices should of course handle this gracefully, but changing group ownership of dbus-daemon-launch-helper to messagebus fixes it (and missing suspend/hibernate/shutdown entries as well, because devkit-power-daemon is also affected). I haven't fully considered yet, whether this causes any other problems, but haven't noticed anything so far."
(In reply to comment #16) > More traces were send, do they contain enough information? Where? How?
In duplicated bug reports
*** Bug 614149 has been marked as a duplicate of this bug. ***
I believe this bug may also be effecting "gvfs-gdu-volume-monitor" (in /usr/libexec), as demonstrated by repeated segfaults in kern.log: Mar 27 23:19:28 frodo kernel: gvfs-gdu-volume[4913]: segfault at c ip b76e863a sp bfbad0b0 error 4 in libgdu.so.0.0.0[b76db000+21000] Mar 27 23:19:33 frodo kernel: gvfs-gdu-volume[4993]: segfault at c ip b782363a sp bfcc8f00 error 4 in libgdu.so.0.0.0[b7816000+21000] Mar 27 23:21:35 frodo kernel: gvfs-gdu-volume[5390]: segfault at c ip b76bd63a sp bf914980 error 4 in libgdu.so.0.0.0[b76b0000+21000] Mar 27 23:21:39 frodo kernel: gvfs-gdu-volume[5498]: segfault at c ip b76a663a sp bfe874c0 error 4 in libgdu.so.0.0.0[b7699000+21000] Mar 28 10:34:47 frodo kernel: gvfs-gdu-volume[11821]: segfault at c ip b77d463a sp bf8fa1e0 error 4 in libgdu.so.0.0.0[b77c7000+21000] Mar 28 18:22:55 frodo kernel: gvfs-gdu-volume[30823]: segfault at c ip b782963a sp bf93c2a0 error 4 in libgdu.so.0.0.0[b781c000+21000] Mar 28 18:22:59 frodo kernel: gvfs-gdu-volume[30864]: segfault at c ip b77dc63a sp bfc2cf90 error 4 in libgdu.so.0.0.0[b77cf000+21000] Mar 29 02:51:50 frodo kernel: gvfs-gdu-volume[1854]: segfault at c ip b780f63a sp bfb12920 error 4 in libgdu.so.0.0.0[b7802000+21000] Tracing the core dump that results from this indicates that update_drives is calling gdu_pool_get_presentables with a NULL pointer which is then dereferenced to produce the segfault. Obvious fix is to check for NULL pointers and not try to dereference them. Stack trace is: Core was generated by `/usr/libexec/gvfs-gdu-volume-monitor'. Program terminated with signal 11, Segmentation fault.
+ Trace 221144
*** Bug 614708 has been marked as a duplicate of this bug. ***
*** Bug 615036 has been marked as a duplicate of this bug. ***
*** Bug 617380 has been marked as a duplicate of this bug. ***
*** Bug 617860 has been marked as a duplicate of this bug. ***
*** Bug 621355 has been marked as a duplicate of this bug. ***
*** Bug 621603 has been marked as a duplicate of this bug. ***
*** Bug 621813 has been marked as a duplicate of this bug. ***
*** Bug 625819 has been marked as a duplicate of this bug. ***
*** Bug 627295 has been marked as a duplicate of this bug. ***
ed@capella ~ $ /usr/libexec/gdu-notification-daemon (gdu-notification-daemon:6283): libgdu-WARNING **: Couldn't get daemon properties ====================================================================== Error constructing GduPool: (unspecified error) This error suggests there's a problem with your udisks or D-Bus installation. ====================================================================== (gdu-notification-daemon:6283): GLib-GObject-WARNING **: invalid (NULL) pointer instance (gdu-notification-daemon:6283): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed (gdu-notification-daemon:6283): GLib-GObject-WARNING **: invalid (NULL) pointer instance (gdu-notification-daemon:6283): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed (gdu-notification-daemon:6283): GLib-GObject-WARNING **: invalid (NULL) pointer instance (gdu-notification-daemon:6283): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed (gdu-notification-daemon:6283): GLib-GObject-WARNING **: invalid (NULL) pointer instance (gdu-notification-daemon:6283): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed ** libgdu:ERROR:gdu-pool.c:2459:gdu_pool_get_devices: assertion failed: (pool != NULL)
*** Bug 632389 has been marked as a duplicate of this bug. ***
*** Bug 633264 has been marked as a duplicate of this bug. ***
last dupe in 2.30.x
*** Bug 642569 has been marked as a duplicate of this bug. ***
*** Bug 642678 has been marked as a duplicate of this bug. ***
*** Bug 645275 has been marked as a duplicate of this bug. ***
*** Bug 645863 has been marked as a duplicate of this bug. ***
*** Bug 646785 has been marked as a duplicate of this bug. ***
*** Bug 646787 has been marked as a duplicate of this bug. ***
*** Bug 648630 has been marked as a duplicate of this bug. ***
Open bug in launchpad.net: https://bugs.launchpad.net/bugs/418300 "Was restarting gnome-do, as it was using too much cpu on startup." bug in version [0]2.32.1-0ubuntu4 https://launchpadlibrarian.net/72956969/_usr_lib_gnome-disk-utility_gdu-notification-daemon.1000.crash
+ Trace 227371
*** Bug 651933 has been marked as a duplicate of this bug. ***
*** Bug 652405 has been marked as a duplicate of this bug. ***
*** Bug 651809 has been marked as a duplicate of this bug. ***
*** Bug 652444 has been marked as a duplicate of this bug. ***
*** Bug 655645 has been marked as a duplicate of this bug. ***
*** Bug 655681 has been marked as a duplicate of this bug. ***
*** Bug 656210 has been marked as a duplicate of this bug. ***
last dupe in 2.32.x
*** Bug 656962 has been marked as a duplicate of this bug. ***
*** Bug 657604 has been marked as a duplicate of this bug. ***
*** Bug 657929 has been marked as a duplicate of this bug. ***
*** Bug 658037 has been marked as a duplicate of this bug. ***
*** Bug 658300 has been marked as a duplicate of this bug. ***
*** Bug 658515 has been marked as a duplicate of this bug. ***
*** Bug 658618 has been marked as a duplicate of this bug. ***
*** Bug 659988 has been marked as a duplicate of this bug. ***
*** Bug 661637 has been marked as a duplicate of this bug. ***
*** Bug 662006 has been marked as a duplicate of this bug. ***
*** Bug 662444 has been marked as a duplicate of this bug. ***
*** Bug 665270 has been marked as a duplicate of this bug. ***
As of gnome-disk-utility 3.4 everything was rewritten to use udisks2 and GDBus. Since this bug is for an old version, closing as OBSOLETE. Thanks for taking the time to report this bug. However, you are using a version that is too old and not supported anymore. GNOME developers are no longer working on that version, so unfortunately there will not be any bug fixes for the version that you use. By upgrading to a newer version of GNOME you could receive bug fixes and new functionality. You may need to upgrade your Linux distribution to obtain a newer version of GNOME. Please feel free to reopen this bug if the problem still occurs with a newer version of GNOME.