GNOME Bugzilla – Bug 503958
crash in Deskbar: I just want to use the D...
Last modified: 2007-12-17 10:28:21 UTC
What were you doing when the application crashed? I just want to use the Deskbar Applet -- but really a bigger bug is that I can't get it to show a text field in the panel anymore; so I keep fiddleing with settings trying to get that feature back. . 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: Clearlooks 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 (4454 sec old) --------------------- alarm-queue.c:215 (add_client_alarms_cb) - Adding (nil) alarm-queue.c:581 (load_alarms_for_today) - From Sun Dec 16 16:00:01 2007 to Sun Dec 16 16:00:01 2007 alarm-queue.c:518 (load_alarms) alarm-queue.c:537 (load_alarms) - Disconnecting old queries alarm-queue.c:547 (load_alarms) - Setting Call backs alarm-queue.c:215 (add_client_alarms_cb) - Adding (nil) alarm-queue.c:581 (load_alarms_for_today) - From Sun Dec 16 16:00:01 2007 to Sunevolution-alarm-notify-Message: alarm.c:246: Requested removal of nonexistent alarm! evolution-alarm-notify-Message: Setting timeout for 86400 1197936000 1197849600 evolution-alarm-notify-Message: Mon Dec 17 16:00:00 2007 evolution-alarm-notify-Message: Sun Dec 16 16:00:00 2007 -------------------------------------------------- Traceback (most recent call last):
+ Trace 182075
run_old(*args, **kwargs)
self.__target(*self.__args, **self.__kwargs)
function(*args, **kwargs)
if text.startswith(query):
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 475351 ***