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 603578 - crash in Disk Notifications: Loging on
crash in Disk Notifications: Loging on
Status: RESOLVED DUPLICATE of bug 602697
Product: gnome-disk-utility
Classification: Core
Component: notifications
0.4
Other All
: Normal critical
: ---
Assigned To: gnome-disk-utility-maint
gnome-disk-utility-maint
Depends on:
Blocks:
 
 
Reported: 2009-12-02 11:35 UTC by mar_defy420
Modified: 2009-12-02 12:21 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28


Description mar_defy420 2009-12-02 11:35:02 UTC 
Version: 0.3

What were you doing when the application crashed?
Loging on 


Distribution: Unknown
Gnome Release: 2.28.0 2009-10-23 (Foresight Linux)
BugBuddy Version: 2.28.0

System: Linux 2.6.30.9-4-fl.smp.gcc4.1.x86_64 #1 SMP Wed Nov 4 11:21:22 UTC 2009 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10603000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: nimbus
Icon Theme: gnome-brave
GTK+ Modules: canberra-gtk-module, gnomebreakpad

Memory status: size: 148402176 vsize: 148402176 resident: 7290880 share: 5615616 rss: 7290880 rss_rlim: 18446744073709551615
CPU usage: start_time: 1259753639 rtime: 3 utime: 2 stime: 1 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/libexec/gdu-notification-daemon'

Using host libthread_db library "/lib64/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0x7fc1ab7896e0 (LWP 2680)]
0x00007fc1a9aec9c5 in waitpid () from /lib64/libpthread.so.0

+ Trace 219420

Thread 1 (Thread 0x7fc1ab7896e0 (LWP 2680))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 g_spawn_sync
    from /lib64/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /lib64/libglib-2.0.so.0
  • #3 ??
    from /usr/lib64/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 gdu_pool_get_devices
    from /usr/lib64/libgdu.so.0
  • #6 update_all
    at notification-main.c line 262
  • #7 main
    at notification-main.c line 574
  • #0 waitpid
    from /lib64/libpthread.so.0 


---- 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 ---------------------
(gdu-notification-daemon:2680): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
beagled will run in the background.
Use beagle-status to check progress of beagled.
For log files check /home/Quigui/.beagle/Log/current-Beagle.
[35;01mwarning: No hp: or hpfax: devices found in any installed CUPS queue. Exiting.[0m
[01mHP Linux Imaging and Printing System (ver. 3.9.8)[0m
[01mSystem Tray Status Service ver. 2.0[0m
Copyright (c) 2001-9 Hewlett-Packard Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.
--------------------------------------------------
Comment 1 Akhil Laddha 2009-12-02 12:21:21 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?

*** This bug has been marked as a duplicate of bug 602697 ***