GNOME Bugzilla – Bug 546611
crash in Deskbar: Using it. Sorry I don't...
Last modified: 2008-08-06 16:38:26 UTC
What were you doing when the application crashed? Using it. Sorry I don't have more details. I just start it up using a key combination and usually use it to start programs, i.e. type letters, then hit enter to start the program or open the folder. Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.1 2007-10-19 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-15-generic #1 SMP Tue Jun 10 09:21:34 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Human Icon Theme: Crashbit 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 (8576 sec old) --------------------- alarm-notify.c:337 (alarm_msgport_replied) - 0x80e9448: Replied to GUI thread alarm-queue.c:1832 (check_midnight_refresh) alarm-queue.c:1832 (check_midnight_refresh) alarm-queue.c:1832 (check_midnight_refresh) alarm-queue.c:1832 (check_midnight_refresh) alarm-queue.c:1832 (check_midnight_refresh) alarm-queue.c:1832 (check_midnight_refresh) alarm-queue.c:1832 (check_midnight_refresh) alarm-queue.c:1832 (check_midnight_refresh) alarm-queue.c:1832 (check_midnight_refresh) alarm-queue.c:1832 (check_midnight_refresh) alarm-queue.c:1832 (check_midnight_refresh) alarm-queue.c:1832 (check_midnight_refresh) alarm-queue.c:1832 (check_midnight_refresh) alarm-queue.c:1832 (check_midnight_refresh) alarm-queue.c:1832 (check_m -------------------------------------------------- Traceback (most recent call last):
+ Trace 204725
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 ***