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 558441 - crash in Deskbar: ни чего не делал. при за...
crash in Deskbar: ни чего не делал. при за...
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-10-29 19:41 UTC by timo
Modified: 2008-11-01 12:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description timo 2008-10-29 19:41:47 UTC 
What were you doing when the application crashed?
ни чего не делал. при загрузке системы появляется ошибка "файл пользователя $home/.dmrs имеет не корректные права доступа и игнарируется". позже стала появлятся ошибка "диспетчер сеансов GNOME не смог заблокировать файл /home/timo/.ICEEauthority". опять же ни чего не делал и система загрузилась. теперь боюсь выключать. помогите. спасибо.


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: 70000000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
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 (8 sec old) ---------------------
 to Wed Oct 29 22:36:16 2008
alarm-queue.c:518 (load_alarms) 
alarm-queue.c:547 (load_alarms) - Setting Call backs 
alarm-notify.c:337 (alarm_msgport_replied) - 0x80dec00: Replied to GUI thread
alarm-notify.c:349 (alarm_msg_received) - 0x81b85c8: Received at thread 2b455b90
alarm-queue.c:2003 (alarm_queue_add_async) - 0x812cd00
alarm-queue.c:581 (load_alarms_for_today) - From Wed Oct 29 22:36:16 2008
 to Wed Oct 29 22:36:16 2008
alarm-queue.c:518 (load_alarms) 
alarm-queue.c:547 (load_alarms) - Setting Call backs 
alarm-notify.c:337 (alarm_msgport_replied) - 0x81b85c8: 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) - 0x80edbd8: Received
--------------------------------------------------
Traceback (most recent call last):

+ Trace 208890

  • 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: Невозможно перезаписать существующее значение, предназначенное только для чтения: Невозможно перезаписать существующее значение, предназначенное только для чтения: Значение для "/apps/deskbar/keybinding" установлено в источнике только-для-чтения в начале пути конфигурации 






Comment 1


Susana





          2008-11-01 12:22:48 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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