GNOME Bugzilla – Bug 570013
crash in Deskbar: clicked twice on deskbar...
Last modified: 2009-02-01 20:28:25 UTC
What were you doing when the application crashed? clicked twice on deskbar search applet Distribution: Ubuntu 8.10 (intrepid) Gnome Release: 2.24.1 2008-10-24 (Ubuntu) BugBuddy Version: 2.24.1 System: Linux 2.6.27-11-generic #1 SMP Thu Jan 22 17:22:40 UTC 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10502000 Selinux: No Accessibility: Disabled GTK+ Theme: Human Icon Theme: Human 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 (117 sec old) --------------------- Unknown message: An invalid char is given at scim_bridge_string_to_uint (): - Unknown message: Invalid message: Close the connection. Failed to receive messages at scim_bridge_client_read_and_dispatch () An IOException at scim_bridge_client_handle_key_event () An IOException at filter_key_event () An IOException at key_snooper () An IOException occurred at scim_bridge_client_imcontext_set_cursor_location () An IOException occurred at scim_bridge_client_imcontext_set_cursor_location () An IOException occurred at scim_bridge_client_imcontext_set_cursor_location () An IOException occurred at scim_bridge_client_imcontext_set_cursor_location () An IOException occurred at scim_bridge_client_imcontext_set_cursor_location () An IOException occurred at scim_bridge_client_imcontext_set_cursor_location () An IOException occurred at scim_bridge_client_imcontext_set_cursor_location () ...Too much output, ignoring rest... -------------------------------------------------- Traceback (most recent call last):
+ Trace 212073
run_old(*args, **kwargs)
self.__target(*self.__args, **self.__kwargs)
function(*args, **kwargs)
if tomboy().FindNote(case) == '':
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 524456 ***