GNOME Bugzilla – Bug 494165
crash in Deskbar: starting the computer al...
Last modified: 2007-11-08 19:08:12 UTC
What were you doing when the application crashed? starting the computer also I just removed all the tracker stuff. It was eating 1.4 gb of ram! 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 --------------------- Version: 1.0 Info: A clone of the Mac OSX-Dashboard clock UPDATING SHAPE OK - Clock has been initialized. Restored instances from session 'default' ... CachingBackend: Saving <#Clock1> :) ... kbuildsycoca running... kio (KMimeType): WARNING: KServiceType::offers : servicetype ThumbCreator not found kio (KMimeType): WARNING: KServiceType::offers : servicetype ThumbCreator not found kio (KMimeType): WARNING: KServiceType::offers : servicetype ThumbCreator not found kio (KMimeType): WARNING: KServiceType::offers : servicetype ThumbCreator not found kio (KMimeType): WARNING: KServiceType::offers : servicetype ThumbCreator not found kio (KMimeType): WARNING: KServiceType::offers : servicetype ThumbCreator not found kio (KMimeType): WARNING: KServiceType::offers : servicetype ThumbCreator not found kio (KMimeType): WARNING: KServiceType::offers : servicetype ThumbCreator not found -------------------------------------------------- Traceback (most recent call last):
+ Trace 175731
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 ***