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 648630 - crash in Disk Notifications: Just started gnome-sessi...
crash in Disk Notifications: Just started gnome-sessi...
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-04-25 17:55 UTC by me
Modified: 2011-04-25 19:43 UTC
See Also:
GNOME target: ---
GNOME version: 2.31/2.32


Description me 2011-04-25 17:55:08 UTC 
Version: 2.32.1

What were you doing when the application crashed?
Just started gnome-session is all.


Distribution: Gentoo Base System release 1.12.14
Gnome Release: 2.32.1 2011-04-25 (Gentoo)
BugBuddy Version: 2.32.0

System: Linux 2.6.38-gentoo-r2 #1 SMP Sat Apr 16 13:42:21 PDT 2011 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10904000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome
GTK+ Modules: canberra-gtk-module, gnomesegvhandler

Memory status: size: 187363328 vsize: 187363328 resident: 10346496 share: 8417280 rss: 10346496 rss_rlim: 18446744073709551615
CPU usage: start_time: 1303754051 rtime: 3 utime: 1 stime: 2 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]
0x00007f9327b1cb3e in __libc_waitpid (pid=<value optimized out>, stat_loc=0x7fffd83eb8b0, options=<value optimized out>) at ../sysdeps/unix/sysv/linux/waitpid.c:32
	in ../sysdeps/unix/sysv/linux/waitpid.c

+ Trace 226874

Thread 1 (Thread 0x7f93290f9900 (LWP 19923))

  • #0 __libc_waitpid
    at ../sysdeps/unix/sysv/linux/waitpid.c line 32
  • #1 g_spawn_sync
    at gspawn.c line 392
  • #2 g_spawn_command_line_sync
    at gspawn.c line 706
  • #3 run_bug_buddy
    at gnome-segvhanlder.c line 240
  • #4 bugbuddy_segv_handle
    at gnome-segvhanlder.c line 191
  • #5 <signal handler called>
  • #6 raise
    at ../nptl/sysdeps/unix/sysv/linux/raise.c line 64
  • #7 abort
    at abort.c line 92
  • #8 g_assertion_message
  • #9 g_assertion_message_expr
    at gtestutils.c line 1369
  • #10 gdu_pool_get_devices
    at gdu-pool.c line 2459
  • #11 update_unmount_dialogs
    at notification-main.c line 282
  • #12 update_all
    at notification-main.c line 75
  • #13 main
    at notification-main.c line 542 

	Inferior 1 [process 19923] 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
Comment 1 Fabio Durán Verdugo 2011-04-25 19:43:02 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 ***