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 617860 - crash in Disk Notifications: Updated to latest stable...
crash in Disk Notifications: Updated to latest stable...
Status: RESOLVED DUPLICATE of bug 602697
Product: gnome-disk-utility
Classification: Core
Component: notifications
2.28.x
Other All
: Normal critical
: ---
Assigned To: gnome-disk-utility-maint
gnome-disk-utility-maint
Depends on:
Blocks:
 
 
Reported: 2010-05-06 07:19 UTC by Torbjörn Svensson
Modified: 2010-05-06 08:38 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28



Description Torbjörn Svensson 2010-05-06 07:19:51 UTC
Version: 2.28.1

What were you doing when the application crashed?
Updated to latest stable (amd64) packages as of 2010-05-06 09.00 CEST, Gnome 2.28.2 included. After upgrade, I loged out of X and restarted consolekit and hald. Loged out of the terminal and loged back in and run startx. During startup of gnome, I got this bug-buddy. I have successfully been able to reproduce this, so it's not a one timer.


Distribution: Gentoo Base System release 1.12.13
Gnome Release: 2.28.2 2010-05-06 (Gentoo)
BugBuddy Version: 2.28.0

System: Linux 2.6.31-gentoo-r6_try2 #1 SMP Wed Jan 27 22:19:07 CET 2010 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10706000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome
GTK+ Modules: canberra-gtk-module, gnomebreakpad

Memory status: size: 161443840 vsize: 161443840 resident: 7593984 share: 6021120 rss: 7593984 rss_rlim: 18446744073709551615
CPU usage: start_time: 1273129951 rtime: 1 utime: 1 stime: 0 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]
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
0x00007f2a7c1bf915 in __libc_waitpid (pid=18799, stat_loc=0x7ffff9e9c370, 
    options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:32
	in ../sysdeps/unix/sysv/linux/waitpid.c

Thread 1 (Thread 0x7f2a7d48b6f0 (LWP 18787))

  • #0 __libc_waitpid
    at ../sysdeps/unix/sysv/linux/waitpid.c line 32
  • #1 IA__g_spawn_sync
    at gspawn.c line 386
  • #2 IA__g_spawn_command_line_sync
    at gspawn.c line 700
  • #3 run_bug_buddy
    at gnome-breakpad.cc line 369
  • #4 check_if_gdb
    at gnome-breakpad.cc line 440
  • #5 bugbuddy_segv_handle
    at gnome-breakpad.cc line 223
  • #6 <signal handler called>
  • #7 gdu_pool_get_devices
    at gdu-pool.c line 1348
  • #8 update_unmount_dialogs
    at notification-main.c line 317
  • #9 update_all
    at notification-main.c line 81
  • #10 main
    at notification-main.c line 701

	Inferior 1 [process 18787] 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
Comment 1 Akhil Laddha 2010-05-06 08:38:41 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 ***