GNOME Bugzilla – Bug 489980
crash in Deskbar: using tracker search too...
Last modified: 2007-10-25 10:21:24 UTC
What were you doing when the application crashed? using tracker search tool. it stopped working shortly after doing an online upgrade from fiesty to gusty. 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: 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 (349566 sec old) --------------------- [00000358] main private debug: removing module "s16tofloat32" [00000359] main private debug: removing module "bandlimited_resampler" [00000330] main audio output debug: thread 2831133584 joined (alsa.c:714) [00000330] main audio output debug: removing module "alsa" [00000331] main private debug: removing module "float32tos16" [00000330] main audio output debug: removing module "trivial_mixer" [00000326] ffmpeg decoder debug: ffmpeg codec (Windows Media Video 2) stopped [00000326] main decoder debug: removing module "ffmpeg" [00000326] main decoder debug: thread 2847918992 joined (input/decoder.c:191) [00000326] main decoder debug: killing decoder fourcc `WMV2', 0 PES in FIFO [00000326] main decoder debug: cannot find playlist, destroying vout [00000327] main video output debug: removing module "xvideo" [00000327] main video output debug: thread 2839526288 joined (video_output/video_output.c:461) ...Too much output, ignoring rest... -------------------------------------------------- Traceback (most recent call last):
+ Trace 172656
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 ***