After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 662444 - crash in Disk Notifications: Logging in to gnome acco...
crash in Disk Notifications: Logging in to gnome acco...
Status: RESOLVED DUPLICATE of bug 602697
Product: gnome-disk-utility
Classification: Core
Component: notifications
2.32.x
Other All
: Normal critical
: ---
Assigned To: gnome-disk-utility-maint
gnome-disk-utility-maint
Depends on:
Blocks:
 
 
Reported: 2011-10-22 08:01 UTC by gcyoung
Modified: 2011-10-23 18:07 UTC
See Also:
GNOME target: ---
GNOME version: 2.31/2.32



Description gcyoung 2011-10-22 08:01:33 UTC
Version: 2.32.1

What were you doing when the application crashed?
Logging in to gnome account


Distribution: Gentoo Base System release 2.1
Gnome Release: 2.32.1 2011-10-21 (Gentoo)
BugBuddy Version: 2.32.0

System: Linux 3.0.6-gentoo #3 SMP Fri Oct 21 22:22:00 BST 2011 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 11004000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome
GTK+ Modules: gnomesegvhandler, canberra-gtk-module

Memory status: size: 215732224 vsize: 215732224 resident: 23130112 share: 14127104 rss: 23130112 rss_rlim: 18446744073709551615
CPU usage: start_time: 1319273947 rtime: 12 utime: 9 stime: 3 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/libexec/gdu-notification-daemon'

[Thread debugging using libthread_db enabled]
0x00007fe5b06eacde in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 0x7fe5b11678a0 (LWP 1824))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 g_spawn_sync
    from /usr/lib64/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /usr/lib64/libglib-2.0.so.0
  • #3 bugbuddy_segv_handle
    from /usr/lib64/gtk-2.0/modules/libgnomesegvhandler.so
  • #4 <signal handler called>
  • #5 raise
    from /lib64/libc.so.6
  • #6 abort
    from /lib64/libc.so.6
  • #7 g_assertion_message
    from /usr/lib64/libglib-2.0.so.0
  • #8 g_assertion_message_expr
    from /usr/lib64/libglib-2.0.so.0
  • #9 gdu_pool_get_devices
    from /usr/lib64/libgdu.so.0
  • #10 update_all
  • #11 main
A debugging session is active.

	Inferior 1 [process 1824] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]


---- Critical and fatal warnings logged during execution ----

** GLib-GObject **: g_object_unref: assertion `G_IS_OBJECT (object)' 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 
** GLib-GObject **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed 


----------- .xsession-errors ---------------------
(gdu-notification-daemon:1824): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
(gdu-notification-daemon:1824): GLib-GObject-WARNING **: invalid (NULL) pointer instance
(gdu-notification-daemon:1824): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
**
libgdu:ERROR:gdu-pool.c:2462:gdu_pool_get_devices: assertion failed: (pool != NULL)
** Message: Initializing gksu extension...
Initializing nautilus-gdu extension
(nautilus:1817): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.Spawn.ChildSig
gnome-session[1748]: WARNING: Could not connect to ConsoleKit: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
gnome-session[1748]: WARNING: Could not connect to ConsoleKit: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
system-config-printer-applet: failed to connect to system D-Bus
--------------------------------------------------
Comment 1 André Klapper 2011-10-22 18:51:55 UTC
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 ***
Comment 2 gcyoung 2011-10-23 18:07:52 UTC
This was reported automatically as a bug as I logged in to my account. I examined the output and found a reference to consolekit. It seems my system was missing the init script for constolekit.

I executed "rc-update add consolekit default" , rebooted and all was well.

Apologies for any inconvenience!