GNOME Bugzilla – Bug 490999
crash in Deskbar: I removed tracker (deskt...
Last modified: 2007-10-28 11:26:08 UTC
What were you doing when the application crashed? I removed tracker (desktop search engine and frontend). Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.0 2007-09-17 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-14-generic #1 SMP Sun Oct 14 21:45:15 GMT 2007 x86_64 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 (6 sec old) --------------------- alarm-queue.c:518 (load_alarms) alarm-queue.c:547 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x6d8c60: Replied to GUI thread alarm-notify.c:349 (alarm_msg_received) - 0x6d9120: Received at thread 42044950 alarm-queue.c:2003 (alarm_queue_add_async) - 0x2aaaac001fa0 alarm-queue.c:581 (load_alarms_for_today) - From Sun Oct 28 20:50:14 2007 to Sun Oct 28 20:50:14 2007 alarm-queue.c:518 (load_alarms) alarm-queue.c:547 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x6d9120: Replied to GUI thread alarm-notify.c:393 (cal_opened_cb) contacts:/// - Calendar Status 0 alarm-queue.c:2052 (alarm_queue_add_client) - Posting a task alarm-notify.c:349 (alarm_msg_received) - 0x6db5c0: Received at thread /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 173386
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 ***