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 625819 - crash in Disk Notifications: Logging into new user/gn...
crash in Disk Notifications: Logging into new user/gn...
Status: RESOLVED DUPLICATE of bug 602697
Product: gnome-disk-utility
Classification: Core
Component: notifications
2.30.x
Other All
: Normal critical
: ---
Assigned To: gnome-disk-utility-maint
gnome-disk-utility-maint
Depends on:
Blocks:
 
 
Reported: 2010-08-02 11:11 UTC by robert.bradbury
Modified: 2010-08-03 06:57 UTC
See Also:
GNOME target: ---
GNOME version: 2.29/2.30


Description robert.bradbury 2010-08-02 11:11:52 UTC 
Version: 2.30.1

What were you doing when the application crashed?
Logging into new user/gnome session.  gdu-notification-daemon fails an assertion and aborts.

System has mounted remote NFS devices which may be contributing to the problem.

GDB trace information:

+ Trace 223079

Thread 1 (Thread 0xb6763810 (LWP 897))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    at ../sysdeps/unix/syscall-template.S line 82
  • #2 IA__g_spawn_sync
    at gspawn.c line 386
  • #3 IA__g_spawn_command_line_sync
    at gspawn.c line 700
  • #4 bugbuddy_segv_handle(int)
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 __kernel_vsyscall
  • #7 *__GI_raise
    at ../nptl/sysdeps/unix/sysv/linux/raise.c line 64
  • #8 *__GI_abort
    at abort.c line 92
  • #9 IA__g_assertion_message
  • #10 IA__g_assertion_message_expr
    at gtestutils.c line 1329
  • #11 gdu_pool_get_devices
    at gdu-pool.c line 2459
  • #12 update_unmount_dialogs
    at notification-main.c line 317
  • #13 update_all
    at notification-main.c line 81
  • #14 main
    at notification-main.c line 701 

	Inferior 1 [process 897] 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 


----------- .xsession-errors (21 sec old) ---------------------
+ break
+ '[' -n '' ']'
+ xinitdir=/usr/X11R6/lib/X11/xinit
+ startup=/home/chrome/.xsession
+ userresources=/home/chrome/.Xresources
+ usermodmap=/home/chrome/.Xmodmap
+ sysresources=/usr/X11R6/lib/X11/xinit/.Xresources
+ sysmodmap=/usr/X11R6/lib/X11/xinit/.Xmodmap
++ /etc/X11/chooser.sh
+ '[' -n /etc/X11/Sessions/Gnome ']'
++ /etc/X11/chooser.sh
+ exec /etc/X11/Sessions/Gnome
--------------------------------------------------
Comment 1 Akhil Laddha 2010-08-03 06:57:53 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 ***