Bug 482647 – crash in Deskbar loading history file: cPickle.load(file(HISTORY_FILE))

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 482647 - crash in Deskbar loading history file: cPickle.load(file(HISTORY_FILE))


Summary:	crash in Deskbar loading history file: cPickle.load(file(HISTORY_FILE))


Status:	RESOLVED DUPLICATE of bug 474179

Product:	deskbar-applet
Classification:	Deprecated
Component:	general
Version:	2.20.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Deskbar Applet Maintainer(s)
QA Contact:	Deskbar Applet Maintainer(s)

URL:
Whiteboard:

Duplicates:	482689 482721 483081 483098 (view as bug list)
Depends on:
Blocks:

Reported:	2007-10-02 16:23 UTC by blackmetal123
Modified:	2007-10-05 09:34 UTC

See Also:
GNOME target:	---
GNOME version:	2.19/2.20

Description blackmetal123 2007-10-02 16:23:55 UTC

What were you doing when the application crashed?
Just starting Ubuntu


Distribution: Ubuntu 7.10 (gutsy)
Gnome Release: 2.20.0 2007-09-17 (Ubuntu)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30 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 (6 sec old) ---------------------
/bin/sh: /usr/bin/esd: not found
** (x-session-manager:5116): WARNING **: Could not start esd: Failed to execute child process "/usr/bin/esd" (No such file or directory)
** (x-session-manager:5116): WARNING **: Failed to start sound.
Window manager warning: Failed to read saved session file /home/daan/.metacity/sessions/default0.ms: Failed to open file '/home/daan/.metacity/sessions/default0.ms': No such file or directory
** Message: Not starting remote desktop server
/bin/sh: /usr/bin/esd: not found
Initializing gnome-mount extension
(gnome-panel:5186): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -3 and height 24
/bin/sh: /usr/bin/esd: not found
/bin/sh: /usr/bin/esd: not found
--------------------------------------------------
Traceback (most recent call last):

+ Trace 167172

File "/usr/lib/python2.5/site-packages/deskbar/core/CoreImpl.py", line 314 in on_module_initialized
```
self._history.load()
```
File "/usr/lib/python2.5/site-packages/deskbar/core/DeskbarHistory.py", line 113 in load
```
saved_history = cPickle.load(file(HISTORY_FILE))
```

ImportError: No module named tracker-module

Comment 1 Diego Escalante Urrelo (not reading bugmail) 2007-10-03 07:03:16 UTC

*** Bug 482689 has been marked as a duplicate of this bug. ***

Comment 2 Diego Escalante Urrelo (not reading bugmail) 2007-10-03 07:04:03 UTC

Should this be considered a deskbar bug or a distributor bug (removing tracker causes this, see the dupe)?

Comment 3 Diego Escalante Urrelo (not reading bugmail) 2007-10-04 03:17:28 UTC

*** Bug 483081 has been marked as a duplicate of this bug. ***

Comment 4 Diego Escalante Urrelo (not reading bugmail) 2007-10-04 03:17:38 UTC

*** Bug 483098 has been marked as a duplicate of this bug. ***

Comment 5 Diego Escalante Urrelo (not reading bugmail) 2007-10-04 03:18:39 UTC

*** Bug 482721 has been marked as a duplicate of this bug. ***

Comment 6 Diego Escalante Urrelo (not reading bugmail) 2007-10-04 03:20:32 UTC

Confirming due to dupes, renaming.

Comment 7 Sebastian Pölsterl 2007-10-05 09:34:54 UTC

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 ***