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 561894 - crash in Deskbar: attemoting to change log...
crash in Deskbar: attemoting to change log...
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-11-22 06:32 UTC by kellydebique
Modified: 2008-11-22 16:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description kellydebique 2008-11-22 06:32:26 UTC 
What were you doing when the application crashed?
attemoting to change logon password


Distribution: Ubuntu 8.04 (hardy)
Gnome Release: 2.22.2 2008-06-03 (Ubuntu)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-19-lpia #1 SMP Tue Jul 29 14:02:05 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
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 ---------------------
evolution-alarm-notify-Message: Setting timeout for 62901 1227398400 1227335499
evolution-alarm-notify-Message:  Sat Nov 22 20:00:00 2008
evolution-alarm-notify-Message:  Sat Nov 22 02:31:39 2008
** (dell-launcher:5621): DEBUG: FRAMES=24 FPS=75
Initializing nautilus-share extension
seahorse nautilus module initialized
seahorse nautilus module shutdown
** (dell-launcher:5621): DEBUG: New Category: Entertainment
** (dell-launcher:5621): DEBUG: New Category: Games
** (dell-launcher:5621): DEBUG: New Category: Learn
** (dell-launcher:5621): DEBUG: New Category: Productivity
** (dell-launcher:5621): DEBUG: New Category: Web
--------------------------------------------------
Traceback (most recent call last):

+ Trace 210104

  • File "/usr/lib/deskbar-applet/deskbar-applet", line 30 in applet_factory 
    tray = DeskbarTray(applet)
  • File "/usr/lib/python2.5/site-packages/deskbar/ui/DeskbarTray.py", line 47 in __init__ 
    self.__setup_mvc()
  • File "/usr/lib/python2.5/site-packages/deskbar/ui/DeskbarTray.py", line 88 in __setup_mvc 
    self.__core.run()
  • File "/usr/lib/python2.5/site-packages/deskbar/core/CoreImpl.py", line 54 in run 
    self._setup_keybinder()
  • File "/usr/lib/python2.5/site-packages/deskbar/core/CoreImpl.py", line 75 in _setup_keybinder 
    self.set_keybinding( self.get_keybinding() )
  • File "/usr/lib/python2.5/site-packages/deskbar/core/CoreImpl.py", line 167 in set_keybinding 
    self._gconf.set_keybinding(binding)
  • File "/usr/lib/python2.5/site-packages/deskbar/core/GconfStore.py", line 178 in set_keybinding 
    self._client.set_string(self.GCONF_KEYBINDING, binding)
GError: No database available to save your configuration: Unable to store a value at key '/apps/deskbar/keybinding', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf 






Comment 1


Sebastian Pölsterl





          2008-11-22 16:49:47 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 ***