Bug#357540: gconf2: Failed to get lock

Ross Boylan ross at biostat.ucsf.edu
Fri Mar 17 23:46:23 UTC 2006


Package: gconf2
Version: 2.12.1-12
Severity: normal

I'm seeing this periodically in my logs:
Mar 17 14:51:46 iron gconfd (ross-3055): Failed to get lock for daemon, exiting: Failed to lock '/tmp/gconfd-ross/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable)

That message came a couple of minutes after a reboot.  I think the
others may also be shortly after boots.

I'm not sure what the signficance of the error message is, e.g., if
there really is another process so I still have the service.  I'm
running KDE.

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (50, 'unstable'), (40, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.4.27adnvcd
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages gconf2 depends on:
ii  gconf2-common            2.12.1-12       GNOME configuration database syste
ii  libc6                    2.3.5-13        GNU C Library: Shared libraries an
ii  libgconf2-4              2.12.1-12       GNOME configuration database syste
ii  libglib2.0-0             2.8.6-1         The GLib library of C routines
ii  libpopt0                 1.7-5           lib for parsing cmdline parameters
ii  libxml2                  2.6.23.dfsg.2-2 GNOME XML library
ii  psmisc                   22.1-1          Utilities that use the proc filesy
ii  python                   2.3.5-5         An interactive high-level object-o

Versions of packages gconf2 recommends:
ii  libgtk2.0-0                   2.8.13-1   The GTK+ graphical user interface 

-- no debconf information





More information about the Pkg-gnome-maintainers mailing list