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 652314 - crash in Disk Notifications: I was starting gnome on ...
crash in Disk Notifications: I was starting gnome on ...
Status: RESOLVED DUPLICATE of bug 651809
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-06-10 19:24 UTC by dominique.michel
Modified: 2011-06-11 01:30 UTC
See Also:
GNOME target: ---
GNOME version: 2.31/2.32



Description dominique.michel 2011-06-10 19:24:41 UTC
Version: 2.32.1

What were you doing when the application crashed?
I was starting gnome on gentoo from fvwm-crystal with Xephyr.


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

System: Linux 2.6.37-gentoo-3Dnew #4 SMP PREEMPT Sun Apr 24 02:42:56 CEST 2011 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 11002000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Crux
Icon Theme: crystalsvg
GTK+ Modules: gnomesegvhandler, canberra-gtk-module

Memory status: size: 219541504 vsize: 219541504 resident: 21803008 share: 14372864 rss: 21803008 rss_rlim: 18446744073709551615
CPU usage: start_time: 1307733747 rtime: 13 utime: 6 stime: 7 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]
0x00007f2ac500f39e in __libc_waitpid (pid=<value optimized out>, stat_loc=0x7fff6e747220, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:32
	in ../sysdeps/unix/sysv/linux/waitpid.c

Thread 1 (Thread 0x7f2ac663f8a0 (LWP 9669))

  • #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 ??
    from /usr/lib64/gtk-2.0/modules/libgnomesegvhandler.so
  • #4 <signal handler called>
  • #5 raise
    at ../nptl/sysdeps/unix/sysv/linux/raise.c line 64
  • #6 abort
    at abort.c line 92
  • #7 g_assertion_message
  • #8 g_assertion_message_expr
    at gtestutils.c line 1369
  • #9 gdu_pool_get_devices
    at gdu-pool.c line 2462
  • #10 update_unmount_dialogs
    at notification-main.c line 282
  • #11 update_all
    at notification-main.c line 75
  • #12 main
    at notification-main.c line 542

	Inferior 1 [process 9669] 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 (910 sec old) ---------------------
/etc/X11/gdm/Xsession: Beginning session setup...
Warning: Only changing the first 32 of 16 buttons.
which: no keychain in (/usr/local/bin:/usr/bin:/bin:/opt/bin:/usr/x86_64-pc-linux-gnu/gcc-bin/4.5.2:/usr/kde/3.5/bin:/usr/qt/3/bin:/usr/games/bin)
/etc/X11/gdm/Xsession: Setup done, will execute: /usr/bin/dbus-launch --exit-with-session /usr/bin/ssh-agent -- gnome-session --choose-session=FVWM-Crystal
** (gnome-session:6613): WARNING **: Option inconnue --choose-session=FVWM-Crystal
--------------------------------------------------
Comment 1 Akhil Laddha 2011-06-11 01:30:27 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 651809 ***