GNOME Bugzilla – Bug 492091
crash in Deskbar: I removed tracker packag...
Last modified: 2007-10-31 20:50:52 UTC
What were you doing when the application crashed? I removed tracker package by synaptics and restarted system. System booted up without any alert and I was able to log in the system. Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.1 2007-10-19 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Glider Icon Theme: gnome 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 ----------- .xsession-errors (9 sec old) --------------------- alarm-queue.c:2052 (alarm_queue_add_client) - Posting a task alarm-queue.c:547 (load_alarms) - Setting Call backs alarm-notify.c:349 (alarm_msg_received) - 0x80e2760: Received at thread b43ffb90 alarm-queue.c:2003 (alarm_queue_add_async) - 0x80e2eb0 alarm-notify.c:337 (alarm_msgport_replied) - 0x80e3e98: Replied to GUI thread alarm-queue.c:581 (load_alarms_for_today) - From Wed Oct 31 22:28:44 2007 to Wed Oct 31 22:28:44 2007 alarm-queue.c:518 (load_alarms) alarm-queue.c:547 (load_alarms) - Setting Call backs alarm-notify.c:349 (alarm_msg_received) - 0x80e8cd0: Received at thread b43ffb90 alarm-queue.c:2003 (alarm_queue_add_async) - 0x80e2e70 ala PID TTY TIME CMD /usr/share/themes/Glider/gtk-2.0/gtkrc:107: Invalid symbolic color 'tooltip_bg_color' /usr/share/themes/Glider/gtk-2.0/gtkrc:107: error: invalid identifier `tooltip_bg_color', expected valid identifier -------------------------------------------------- Traceback (most recent call last):
+ Trace 174169
self._history.load()
saved_history = cPickle.load(file(HISTORY_FILE))
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 474179 ***