GNOME Bugzilla – Bug 491798
crash in Deskbar: Error raises after login...
Last modified: 2007-10-31 01:05:15 UTC
What were you doing when the application crashed? Error raises after login into gdm. I think that reason is that I removed "tracker". Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.0 2007-09-17 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks 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 (6 sec old) --------------------- http://www.gtk.org/setuid.html Refusing to initialize GTK+. /etc/gdm/Xsession: Beginning session setup... Setting IM through im-switch for locale=ru_RU. Start IM through /etc/X11/xinit/xinput.d/all_ALL linked to /etc/X11/xinit/xinput.d/default. SESSION_MANAGER=local/leonidv-ubuntu:/tmp/.ICE-unix/5676 ** (gnome-session:5676): WARNING **: Host name lookup failure on localhost. Предупреждение менеджера окон: Значение "" из базы данных конфигурации является недопустимым значением для к Предупреждение менеджера окон: Произошёл сбой при чтении сохранённого файла сеанса "/home/leonidv/.metacity/sessions/default0.ms ** Message: Не запускается сервер удаленного рабочего стола Initializing gnome-mount extension PID TTY TIME CMD Не удалось открыть файл «file:///usr/share/applications/gnome-cups-manager.desktop» для кнопки запуска панели: No such file or directory -------------------------------------------------- Traceback (most recent call last):
+ Trace 173973
self._history.load()
saved_history = cPickle.load(file(HISTORY_FILE))
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 474179 ***