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 613505 - crash in Disk Notifications: Starting session
crash in Disk Notifications: Starting session
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-03-21 15:43 UTC by wodano
Modified: 2010-03-21 22:23 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28



Description wodano 2010-03-21 15:43:32 UTC
Version: 2.28.1

What were you doing when the application crashed?
Starting session


Distribution: Gentoo Base System release 2.0.1
Gnome Release: 2.28.2 2010-03-11 (Gentoo)
BugBuddy Version: 2.28.0

System: Linux 2.6.33-walhall-39 #1 SMP PREEMPT Sat Mar 6 18:44:25 WET 2010 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10799901
Selinux: No
Accessibility: Disabled
GTK+ Theme: Crux
Icon Theme: Crux
GTK+ Modules: canberra-gtk-module, gnomebreakpad

Memory status: size: 277733376 vsize: 277733376 resident: 8417280 share: 6610944 rss: 8417280 rss_rlim: 18446744073709551615
CPU usage: start_time: 1269186060 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'

[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.4-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
0x00007fd18935abae in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 0x7fd18c752700 (LWP 2867))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 bugbuddy_segv_handle(int)
    from /usr/lib64/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 gdu_pool_get_devices
    from /usr/lib/libgdu.so.0
  • #6 update_all
  • #7 main
A debugging session is active.

	Inferior 1 [process 2867] 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 ---------------------
Tracker-Message: Loading database... '/home/jac/.cache/tracker/fulltext.db' (unknown)
Tracker-Message: Opened sqlite3 database:'/home/jac/.cache/tracker/fulltext.db'
Tracker-Message: Initialized tracker fts extension
Tracker-Message:   Setting cache size to 512
Tracker-Message:   Adding functions (FormatDate, etc)
Tracker-Message: Opened sqlite3 database:'/home/jac/.cache/tracker/meta.db'
Tracker-Message: Initialized tracker fts extension
Tracker-Message:   Setting cache size to 2000
Tracker-Message:   Adding functions (FormatDate, etc)
(tracker-store:2868): Tracker-CRITICAL **: Unable to prepare query 'SELECT (SELECT Uri FROM Resource WHERE ID = "tracker:Ontology".ID), "nao:lastModified" FROM "tracker:Ontology"': no such table: trac
(tracker-store:2868): Tracker-CRITICAL **: tracker_db_statement_start_cursor: assertion `TRACKER_IS_DB_STATEMENT (stmt)' failed
(tracker-store:2868): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
--------------------------------------------------
Comment 1 Fabio Durán Verdugo 2010-03-21 22:23:04 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 ***