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 502732 - crash in Deskbar: I was booting Ubuntu fro...
crash in Deskbar: I was booting Ubuntu fro...
Status: RESOLVED DUPLICATE of bug 502472
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-12-09 20:55 UTC by chrsorlando
Modified: 2007-12-10 15:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description chrsorlando 2007-12-09 20:55:18 UTC 
What were you doing when the application crashed?
I was booting Ubuntu from a USB flash drive, and the Deskbar crashed on startup.


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: 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 (18130 sec old) ---------------------
(nautilus:12396): libgnomevfs-WARNING **: module '/usr/lib/gnome-vfs-2.0/modules/libmapping.so' returned a NULL handle
Failed to bind master socket: Operation not permitted
mapping method init - connect2: No such file or directory
(nautilus:12396): libgnomevfs-WARNING **: module '/usr/lib/gnome-vfs-2.0/modules/libmapping.so' returned a NULL handle
Failed to bind master socket: Operation not permitted
mapping method init - connect2: No such file or directory
(nautilus:12396): libgnomevfs-WARNING **: module '/usr/lib/gnome-vfs-2.0/modules/libmapping.so' returned a NULL handle
** Message: Not starting remote desktop server
evolution-alarm-notify-Message: Setting timeout for 29285 1197244800 1197215515
evolution-alarm-notify-Message:  Mon Dec 10 00:00:00 2007
evolution-alarm-notify-Message:  Sun Dec  9 15:51:55 2007
--------------------------------------------------
Traceback (most recent call last):

+ Trace 181365

  • 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: 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


palfrey





          2007-12-10 15:49:04 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 502472 ***