GNOME Bugzilla – Bug 483401
crash in Deskbar: typed text then tab
Last modified: 2007-10-05 09:26:21 UTC
What were you doing when the application crashed? typed text then tab Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.0 2007-09-17 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 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 (809 sec old) --------------------- /etc/gdm/Xsession: Beginning session setup... /etc/profile: 20: [[: not found /etc/X11/Xsession.d/40guidance-displayconfig_restore: 11: /usr/bin/displayconfig-restore: not found Setting IM through im-switch for locale=es_AR. Start IM through /etc/X11/xinit/xinput.d/all_ALL linked to /etc/X11/xinit/xinput.d/default. SESSION_MANAGER=local/gandalf-desktop:/tmp/.ICE-unix/5165 ** (gnome-session:5165): WARNING **: Failed to start sound. Advertencia del gestor de ventanas: Ocurrió un error al leer el archivo de sesión guardado /home/gandalf/.metacity/sessions/default0.ms: Ha ocurrido un error al abrir el archivo «/home/gandalf/.met ** Message: No iniciando el servidor de escritorio remoto Initializing gnome-mount extension Initializing nautilus-image-converter extension PID TTY TIME CMD checking for valid crashreport now -------------------------------------------------- Traceback (most recent call last):
+ Trace 167733
reply_handler(*message.get_args_list(**get_args_opts))
reply_handler = lambda hits: self.recieve_hits(qstring, hits, max),
matches.append(TrackerLiveSearchMatch (output))
self.add_all_actions (get_actions_for_uri(result['uri']))
mime = gnomevfs.get_mime_type(uri)
looks like tracker is causing deskbar to segfault... again
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 474131 ***