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 520935 - crash in Deskbar: Iniciando o Sistema...
crash in Deskbar: Iniciando o Sistema...
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-03-07 09:16 UTC by joseailtonfreitas
Modified: 2008-03-07 10:08 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description joseailtonfreitas 2008-03-07 09:16:40 UTC 
What were you doing when the application crashed?
Iniciando o Sistema...


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: OkayishChicken
Icon Theme: JiniYellowishGreen

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 (7 sec old) ---------------------
alarm-queue.c:547 (load_alarms) - Setting Call backs 
alarm-notify.c:337 (alarm_msgport_replied) - 0x80eb540: 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) - 0x80e9238: Received at thread b4db2b90
alarm-queue.c:2003 (alarm_queue_add_async) - 0x80e4b30
alarm-queue.c:581 (load_alarms_for_today) - From Sat Mar  8 00:00:00 2008
 to Sat Mar  8 00:00:00 2008
alarm-queue.c:518 (load_alarms) 
alarm-queue.c:547 (load_alarms) - Setting Call backs 
alarm-notify.c:337 (alarm_msgport_replied) - 0x80e9238: Replied to GUI thread
alarm-notify.c:393 (cal_opened_cb) file:///home/silverwolf/.evolution/memos/local/system - Calendar Status 0
alarm-queue.c:2052 (alarm_queue_add_client) - Posting a task
alarm-n
Conectando ao servidor [  ###        ]
Conectando ao servidor [ ###         ]
Conectando ao servidor [###          ]
Conectando ao servidor [ ###         ]
Conectando ao servidor [  ###       

Conectando ao servidor [   ###       ]
Conectando ao servidor [  ###        ]
Conectando ao servidor [ ###         ]
Conectando ao servidor [###          ]
Conectando ao servidor [ ###         ]
Cone
--------------------------------------------------
Traceback (most recent call last):

+ Trace 191603

  • 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 48 in run 
    self._setup_keybinder()
  • File "/usr/lib/python2.5/site-packages/deskbar/core/CoreImpl.py", line 69 in _setup_keybinder 
    self.set_keybinding( self.get_keybinding() )
  • File "/usr/lib/python2.5/site-packages/deskbar/core/CoreImpl.py", line 158 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: Não é possível sobreescrever valor somente leitura já existente: Não é possível sobreescrever valor somente leitura já existente: O valor para '/apps/deskbar/keybinding' atribuído em fonte somente leitura no início do seu caminho de configuração 






Comment 1


Sebastian Pölsterl





          2008-03-07 10:08:26 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 ***