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 496704 - crash in Deskbar: immer noch das Gleiche
crash in Deskbar: immer noch das Gleiche
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: 2007-11-14 11:06 UTC by W.Schumann
Modified: 2007-11-14 14:52 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description W.Schumann 2007-11-14 11:06:44 UTC 
What were you doing when the application crashed?
immer noch das Gleiche


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: default.kde

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-
(evolution-alarm-notify:6670): evolution-alarm-notify-WARNING **: Fabrik für Alarmbenachrichtigungsdienst konnte nicht erstellt werden, gegebenenfalls läuft diese bereits.
alarm-notify.c:368 (alarm_notify_new) - Alarm Notify New 
 alarm-notify.c:304 (alarm_channel_setup) - Channel Setup
 alarm-notify.c:243 (alarm_notify_init) - Initing Alarm Notify
alarm-queue.c:1870 (alarm_queue_init)
alarm-queue.c:200 (queue_midnight_refresh) - Refresh at Thu Nov 15 00:00:00 2007
 
alarm-notify.c:220 (load_calendars) - Loading Calendar file:///home/willi/.evolution/tasks/local/system 
alarm-notify.c:462 (alarm_notify_add_calendar) file:///home/willi/.evolution/tasks/local/system - Calendar Open Async... 0x80c6370
alarm-notify.c:220 (load_calendars) - Loading Calendar file:///home/willi/.evolution/memos/local/system 
alarm-notify.c:462 (alarm_notify_add_calendar) file:///home/willi/.evolution/memos/local/system - Calendar Open Async... 0x80e4f40
(gnome-panel:6660): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -1 and height 26
  PID TTY          TIME CMD
--------------------------------------------------
Traceback (most recent call last):

+ Trace 177631

  • 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: Der bestehende, schreibgeschützte Wert konnte nicht überschrieben werden: Der bestehende, schreibgeschützte Wert konnte nicht überschrieben werden: Der Wert für »/apps/deskbar/keybinding« wird in einer nur lesbaren Quelle am Anfang Ihres Konfigurationspfades zugewiesen. 






Comment 1


Sebastian Pölsterl





          2007-11-14 14:52:42 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 ***