GNOME Bugzilla – Bug 485749
crash in Deskbar: Booting machine. Previo...
Last modified: 2007-10-12 10:23:20 UTC
What were you doing when the application crashed? Booting machine. Previous boot had removed tracker and all requirements completely via synaptic. Then reinstalled tracker from command line using apt-get. 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 Wed Oct 10 06:00:47 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 (7 sec old) --------------------- [DEBUG]: File: /usr/lib/tomboy/addins/WebDavSyncService.dll [DEBUG]: AddinManager.OnAddinLoaded: Tomboy.FileSystemSyncServiceAddin [DEBUG]: Name: Local Directory Sync Service Add-in [DEBUG]: Description: Synchronize Tomboy Notes to a local file system path [DEBUG]: Namespace: Tomboy [DEBUG]: Enabled: True [DEBUG]: File: /usr/lib/tomboy/addins/FileSystemSyncService.dll [DEBUG]: Unable to locate 'gnomesu' in your PATH [DEBUG]: Using '/usr/bin/gksu' as GUI 'su' tool [DEBUG]: Successfully found system tools [DEBUG]: Unable to locate 'wdfs' in your PATH [DEBUG]: Tomboy remote control active. [DEBUG]: EnableDisable Called: enabling... True [DEBUG]: Binding key '<Alt>F12' for '/apps/tomboy/global_keybindings/show_note_menu' [DEBUG]: Binding key '<Alt>F11' for '/apps/tomboy/global_keybindings/open_start_here' -------------------------------------------------- Traceback (most recent call last):
+ Trace 169513
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 ***