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 499767 - crash in Deskbar: Gnucash stoping
crash in Deskbar: Gnucash stoping
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: 2007-11-26 16:16 UTC by amrivo73
Modified: 2007-11-26 16:54 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description amrivo73 2007-11-26 16:16:18 UTC
What were you doing when the application crashed?
Gnucash stoping


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 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 ---------------------
alarm-queue.c:518 (load_alarms) 
alarm-queue.c:547 (load_alarms) - Setting Call backs 
alarm-notify.c:337 (alarm_msgport_replied) - 0x80e9c20: Replied to GUI thread
alarm-notify.c:393 (cal_opened_cb) file:///home/ar/.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) - 0x80e0310: Received at thread b45c6b90
alarm-queue.c:2003 (alarm_queue_add_async) - 0x80e8d40
alarm-queue.c:581 (load_alarms_for_today) - From Mon Nov 26 17:14:47 2007
 to Mon Nov 26 17:14:47 2007
alarm-queue.c:518 (load_alarms) 
alarm-queue.c:547 (load_alarms) - Setting Call backs 
alarm-notify.c:337 (alarm_msgport_replied) - 0x80e0310: Replied to GUI thread
alarm-notify.c:393 (cal_opened_cb) contacts:/// - Calendar Status 0
alarm-queue.c:2052 (alarm_queue_add_client) - Posting a task
alarm-notify.c:349 (alarm_msg_received) - 0x80e90f0: Received at thread b45c6b9
--------------------------------------------------
Traceback (most recent call last):
  • 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.ModuleLoader import ModuleLoader
  • File "/usr/lib/python2.5/site-packages/deskbar/core/ModuleLoader.py", line 1 in <module>
    import os, pydoc
  • File "pydoc.py", line 55 in <module>
    import sys, imp, os, re, types, inspect, __builtin__, pkgutil
ValueError: bad marshal data

Comment 1 Sebastian Pölsterl 2007-11-26 16:54: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 ***