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 604213 - crash in Disk Notifications: Tried to mount a DVD, bu...
crash in Disk Notifications: Tried to mount a DVD, bu...
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-09 22:00 UTC by marcus
Modified: 2009-12-10 04:15 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28



Description marcus 2009-12-09 22:00:29 UTC
Version: 0.3

What were you doing when the application crashed?
Tried to mount a DVD, but it had too many scratches. Then i tried to eject the DVD, without success and then the sceen went crazy and i coudn't use ctrl,alt,F1. Rebooted by using the power button. 	


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

System: Linux 2.6.30.6-2-fl.smp.gcc4.1.x86_64 #1 SMP Mon Sep 14 22:19:36 UTC 2009 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10603000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Foresight
Icon Theme: Tango
GTK+ Modules: canberra-gtk-module, gnomebreakpad

Memory status: size: 148594688 vsize: 148594688 resident: 7311360 share: 5623808 rss: 7311360 rss_rlim: 18446744073709551615
CPU usage: start_time: 1260395331 rtime: 7 utime: 5 stime: 2 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 0x7f6f6e6086e0 (LWP 2672)]
0x00007f6f6c9689c5 in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 0x7f6f6e6086e0 (LWP 2672))

  • #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 ---------------------
** (gnome-panel:2622): CRITICAL **: panel_multiscreen_y: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed
** (gnome-panel:2622): CRITICAL **: panel_multiscreen_width: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed
** (gnome-panel:2622): CRITICAL **: panel_multiscreen_height: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed
** (gnome-panel:2622): CRITICAL **: panel_multiscreen_x: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed
** (gnome-panel:2622): CRITICAL **: panel_multiscreen_y: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed
** (gnome-panel:2622): CRITICAL **: panel_multiscreen_width: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed
** (gnome-panel:2622): CRITICAL **: panel_multiscreen_height: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed
evolution-shell-Message: Killing old version of evolution-data-server...
--------------------------------------------------
Comment 1 Akhil Laddha 2009-12-10 04:15:25 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 ***