GNOME Bugzilla – Bug 478905
crash in Deskbar: switching windows on tas...
Last modified: 2007-09-22 09:04:24 UTC
What were you doing when the application crashed? switching windows on task bar Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.0 2007-09-17 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-11-generic #1 SMP Mon Sep 17 03:18:44 GMT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70000000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Mist 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 --------------------- ** (gnome-control-center:1619): WARNING **: error raised: [load_xbel_store: couldn't load bookmark file [NULL] ] (/usr/local/libexec/gnome-screensaver-gl-helper:1804): Gdk-CRITICAL **: gdk_x11_visual_get_xvisual: assertion `visual != NULL' failed (/usr/local/libexec/gnome-screensaver-gl-helper:1813): Gdk-CRITICAL **: gdk_x11_visual_get_xvisual: assertion `visual != NULL' failed LoadPlugin: failed to initialize shared library /home/mandar/.mozilla/plugins/libflashplayer.so [/home/mandar/.mozilla/plugins/libflashplayer.so: wrong ELF class: ELFCLASS32] LoadPlugin: failed to initialize shared library /usr/lib/firefox/plugins/libflashplayer.so [/usr/lib/firefox/plugins/libflashplayer.so: wrong ELF class: ELFCLASS32] LoadPlugin: failed to initialize shared library /home/mandar/.mozilla/plugins/libflashplayer.so [/home/mandar/.mozilla/plugins/libflashplayer.so: wrong ELF class: ELFCLASS32] (gnome-terminal:6535): Vte-WARNING **: No handler for control sequence `device-control-string' defined. Loading Spamassasin as the default junk plugin -------------------------------------------------- Traceback (most recent call last):
+ Trace 164362
self._history.load()
saved_history = cPickle.load(file(HISTORY_FILE)) EOFError
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 470985 ***