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 528472 - crash in Deskbar: nichts; nach dieser Fehl...
crash in Deskbar: nichts; nach dieser Fehl...
Status: RESOLVED DUPLICATE of bug 478337
Product: deskbar-applet
Classification: Deprecated
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Deskbar Applet Maintainer(s)
Deskbar Applet Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2008-04-16 20:47 UTC by oparichard
Modified: 2008-04-16 23:32 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description oparichard 2008-04-16 20:47:55 UTC 
What were you doing when the application crashed?
nichts; nach dieser Fehlermeldung lief alles OK. Natürlich nervt die Fehlermeldung bei jedem logon.


Distribution: Ubuntu 7.10 (gutsy)
Gnome Release: 2.20.1 2007-10-19 (Ubuntu)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-14-generic #1 SMP Tue Feb 12 07:42:25 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: OSX-theme
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 (9 sec old) ---------------------
alarm-queue.c:518 (load_alarms) 
alarm-queue.c:547 (load_alarms) - Setting Call backs 
alarm-notify.c:337 (alarm_msgport_replied) - 0x80f0ad0: Replied to GUI thread
alarm-notify.c:349 (alarm_msg_received) - 0x80f3848: Received at thread b359bb90
alarm-queue.c:2003 (alarm_queue_add_async) - 0x80f0d70
alarm-queue.c:581 (load_alarms_for_today) - From Wed Apr 16 22:45:16 2008
 to Wed Apr 16 22:45:16 2008
alarm-queue.c:518 (load_alarms) 
alarm-queue.c:547 (load_alarms) - Setting Call backs 
alarm-notify.c:337 (alarm_msgport_replied) - 0x80f3848: Replied to GUI thread
alarm-notify.c:393 (cal_opened_cb) file:///home/richard/.evolution/memos/local/system - Calendar Status 0
alarm-queue.c:2052 (alarm_queue_add_client) - Posting a task
alarm-notify.c:349 (alarm_msg_received) - 0x80f6e28: Received at thread b359bb90
alarm-queue.c:2003 (alarm_queue_add_async) - 0x80f0c00
alarm-queue.c:581 (load
--------------------------------------------------
Traceback (most recent call last):

+ Trace 195408

  • File "/usr/lib/deskbar-applet/deskbar-applet", line 50 in <module> 
    from deskbar.ui.DeskbarApplet import DeskbarApplet
  • File "/usr/lib/python2.5/site-packages/deskbar/ui/DeskbarApplet.py", line 7 in <module> 
    from deskbar.core.CoreImpl import CoreImpl
  • File "/usr/lib/python2.5/site-packages/deskbar/core/CoreImpl.py", line 7 in <module> 
    from deskbar.core.ModuleInstaller import ModuleInstaller
  • File "/usr/lib/python2.5/site-packages/deskbar/core/ModuleInstaller.py", line 2 in <module> 
    import urllib
ValueError: bad marshal data 






Comment 1


Gianluca Borello





          2008-04-16 23:32:13 UTC
        



Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 478337 ***