GNOME Bugzilla – Bug 524754
crash in Deskbar:
Last modified: 2008-04-04 07:05:24 UTC
What were you doing when the application crashed? 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: 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 (40 sec old) --------------------- (evolution:6428): camel-WARNING **: Could not find key entry for word 'traducción': No existe el fichero ó directorio (evolution:6428): camel-WARNING **: Could not find key entry for word 'hola': No existe el fichero ó directorio (evolution:6428): camel-WARNING **: Could not find key entry for word 'módulo': No existe el fichero ó directorio ** (nm-applet:6159): WARNING **: <WARN> nmi_save_network_info(): Error saving secret for wireless network 'acasil' in keyring: 1 JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] -------------------------------------------------- Traceback (most recent call last):
+ Trace 193509
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 471355 ***
(made a little mistake) 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 ***