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 506964 - crash in Deskbar: Booting Ubuntu from USB ...
crash in Deskbar: Booting Ubuntu from USB ...
Status: RESOLVED DUPLICATE of bug 486549
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-01-03 01:54 UTC by james
Modified: 2008-01-06 12:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description james 2008-01-03 01:54:03 UTC 
What were you doing when the application crashed?
Booting Ubuntu from USB stick.


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 ---------------------
alarm-queue.c:518 (load_alarms) 
alarm-queue.c:547 (load_alarms) - Setting Call backs 
alarm-notify.c:337 (alarm_msgport_replied) - 0x80dc6a0: 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) - 0x80e16e8: Received at thread b3ddab90
alarm-queue.c:2003 (alarm_queue_add_async) - 0x80d7a70
alarm-queue.c:581 (load_alarms_for_today) - From Wed Jan  2 18:53:18 2008
 to Wed Jan  2 18:53:18 2008
alarm-queue.c:518 (load_alarms) 
alarm-queue.c:547 (load_alarms) - Setting Call backs 
alarm-notify.c:337 (alarm_msgport_replied) - 0x80e16e8: Replied to GUI thread
alarm-notify.c:393 (cal_opened_cb) file:///home/ubuntu/.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) - 0
--------------------------------------------------
Traceback (most recent call last):

+ Trace 183866

  • File "/usr/lib/deskbar-applet/deskbar-applet", line 27 in applet_factory 
    dapplet = DeskbarApplet(applet)
  • File "/usr/lib/python2.5/site-packages/deskbar/ui/DeskbarApplet.py", line 91 in __init__ 
    self.__setup_mvc()
  • File "/usr/lib/python2.5/site-packages/deskbar/ui/DeskbarApplet.py", line 101 in __setup_mvc 
    self.__core.run()
  • File "/usr/lib/python2.5/site-packages/deskbar/core/CoreImpl.py", line 47 in run 
    self._setup_keybinder()
  • File "/usr/lib/python2.5/site-packages/deskbar/core/CoreImpl.py", line 67 in _setup_keybinder 
    self.set_keybinding( self.get_keybinding() )
  • File "/usr/lib/python2.5/site-packages/deskbar/core/CoreImpl.py", line 156 in set_keybinding 
    self._gconf.set_keybinding(binding)
  • File "/usr/lib/python2.5/site-packages/deskbar/core/GconfStore.py", line 157 in set_keybinding 
    self._client.set_string(self.GCONF_KEYBINDING, binding)
GError: Can't overwrite existing read-only value: Can't overwrite existing read-only value: Value for `/apps/deskbar/keybinding' set in a read-only source at the front of your configuration path 






Comment 1


Sebastian Pölsterl





          2008-01-06 12:49:05 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 486549 ***