opps a fatal error occured

Bug #1320781 reported by dark_sarin on 2014-05-19
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu Tweak

Bug Description

Distribution: Ubuntu 10.04 lucid
Application: Ubuntu Tweak 0.5.14
Desktop: gnome

Traceback (most recent call last):
  File "/usr/bin/ubuntu-tweak", line 110, in <module>
    launcher = TweakLauncher(session_bus, MainWindow())
  File "/usr/lib/python2.6/dist-packages/ubuntutweak/mainwindow.py", line 276, in __init__
  File "/usr/lib/python2.6/dist-packages/ubuntutweak/mainwindow.py", line 351, in get_gui_state
  File "/usr/lib/python2.6/dist-packages/ubuntutweak/common/config.py", line 147, in get_window_size
    width = cls.config.get_value_from_key(cls.window_width, default=900)
  File "/usr/lib/python2.6/dist-packages/ubuntutweak/common/config.py", line 35, in get_value_from_key
    return self.get_value()
  File "/usr/lib/python2.6/dist-packages/ubuntutweak/conf/gconfsetting.py", line 103, in get_value
  File "/usr/lib/python2.6/dist-packages/ubuntutweak/conf/gconfsetting.py", line 112, in set_value
    self.__client.set_value(self.__key, value)
GError: No database available to save your configuration: Unable to store a value at key '/apps/ubuntu-tweak/window_width', 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

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers