GNOME Bugzilla – Bug 527248
crash in Deskbar: Just trying to type a co...
Last modified: 2008-04-10 08:52:19 UTC
What were you doing when the application crashed? Just trying to type a command. Seems if I hit "enter" while it's trying to load auto-completion info it crashes a lot. Any way I can replace deskbar applet with something that just lets me type commands? I already have aliases for anything I want to type there anyway. 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 Tue Feb 12 07:42:25 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Human 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 (6143 sec old) --------------------- 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_midnight_reKilled -------------------------------------------------- Traceback (most recent call last):
+ Trace 194785
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 ***