GNOME Bugzilla – Bug 625342
crash in Deskbar:
Last modified: 2010-07-27 10:07:51 UTC
What were you doing when the application crashed? Distribution: Ubuntu 10.04 (lucid) Gnome Release: 2.30.2 2010-06-25 (Ubuntu) BugBuddy Version: 2.28.0 System: Linux 2.6.32-24-generic #38-Ubuntu SMP Mon Jul 5 09:22:14 UTC 2010 i686 X Vendor: The X.Org Foundation X Vendor Release: 10706000 Selinux: No Accessibility: Disabled GTK+ Theme: Ambiance Icon Theme: ubuntu-mono-dark GTK+ Modules: canberra-gtk-module Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0 CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 Traceback (most recent call last):
+ Trace 222996
from deskbar.ui.DeskbarApplet import DeskbarApplet
from deskbar.ui.AbstractCuemiacDeskbarIcon import AbstractCuemiacDeskbarIcon
from deskbar.ui.CuemiacWindowController import CuemiacWindowController
from deskbar.ui.preferences.DeskbarPreferences import DeskbarPreferences
from deskbar.ui.preferences.AccelEntry import AccelEntry
----------- .xsession-errors --------------------- Starting log: File:'/home/jiff/.local/share/tracker/trackerd.log' (polkit-gnome-authentication-agent-1:1541): GLib-GObject-WARNING **: cannot register existing type `_PolkitError' (polkit-gnome-authentication-agent-1:1541): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed 18 Unable to find a synaptics device. (gnome-power-manager:1530): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.24.1/gobject/gsignal.c:2273: signal `proxy-status' is invalid for instance `0x9c0c2f8' Impossible d'ouvrir le fichier de bureau evolution-mail.desktop pour le lanceur du tableau de bord Initializing nautilus-gdu extension (trackerd:1537): Tracker-CRITICAL **: tracker_processor_mount_point_added: assertion `TRACKER_IS_PROCESSOR (processor)' failed Échec : Échec lors de l'initialisation du module --------------------------------------------------
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 617299 ***