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 661637 - crash in Disk Notifications: Nothing
crash in Disk Notifications: Nothing
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-13 09:08 UTC by josef.kohout
Modified: 2011-10-13 09:31 UTC
See Also:
GNOME target: ---
GNOME version: 2.31/2.32



Description josef.kohout 2011-10-13 09:08:57 UTC
Version: 2.32.1

What were you doing when the application crashed?
Nothing


Distribution: Gentoo Base System release 2.0.3
Gnome Release: 2.32.1 2011-09-19 (Gentoo)
BugBuddy Version: 2.32.0

System: Linux 3.0.4-gentoo #1 SMP Sun Sep 18 14:47:09 CEST 2011 i686
X Vendor: The X.Org Foundation
X Vendor Release: 11004000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome
GTK+ Modules: gnomesegvhandler, canberra-gtk-module

Memory status: size: 19329024 vsize: 19329024 resident: 6463488 share: 5316608 rss: 6463488 rss_rlim: 18446744073709551615
CPU usage: start_time: 1318496877 rtime: 4 utime: 3 stime: 1 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]
0xffffe424 in __kernel_vsyscall ()

Thread 1 (Thread 0xb69b97e0 (LWP 2395))

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

	Inferior 1 [process 2395] 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 ---------------------
TI:11:07:59	TH:0x80748f8	FI:gpm-main.c	FN:main,220
 - This program cannot start until you start the dbus system service.
It is <b>strongly recommended</b> you reboot your computer after starting this service.
Traceback:
	gnome-power-manager() [0x80618bf]
	gnome-power-manager() [0x805660e]
	/lib/libc.so.6(__libc_start_main+0xe6) [0xb6d98de2]
	gnome-power-manager() [0x804e8b1]
(gnome-panel:2390): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.Spawn.Child
** Message: Initializing gksu extension...
(nautilus:2392): 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[2325]: WARNING: Could not connect to ConsoleKit: Failed to connect to socket /var/run/dbus/system_bus_socket: Adresář nebo soubor neexistuje
gnome-session[2325]: WARNING: Could not connect to ConsoleKit: Failed to connect to socket /var/run/dbus/system_bus_socket: Adresář nebo soubor neexistuje
--------------------------------------------------
Comment 1 Akhil Laddha 2011-10-13 09:31:44 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 ***