Why is gconfd starting twice?

[Adam Funk]

On my recent Ubuntu installation I keep seeing this error

  gconfd (adam-2543): Failed to get lock for daemon, exiting: Failed
  to lock '/tmp/gconfd-adam/lock/ior': probably another process has
  the lock, or your operating system has NFS file locking
  misconfigured (Resource temporarily unavailable)

in my logcheck output from every X login and figured out that for some
reason gconfd is trying to start twice every time I log in:

Aug 15 08:53:45 bunsen gconfd (adam-13861): starting (version 2.14.0), pid 13861 user 'adam'
Aug 15 08:53:46 bunsen gconfd (adam-13859): starting (version 2.14.0), pid 13859 user 'adam'
Aug 15 08:53:46 bunsen gconfd (adam-13859): Failed to get lock for daemon, exiting: Failed to lock '/tmp/gconfd-adam/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable)
Aug 15 08:53:46 bunsen gconfd (adam-13861): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0
Aug 15 08:53:46 bunsen gconfd (adam-13861): Resolved address "xml:readwrite:/home/adam/.gconf" to a writable configuration source at position 1
Aug 15 08:53:46 bunsen gconfd (adam-13861): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2
Aug 15 08:53:46 bunsen gconfd (adam-13861): Resolved address "xml:readonly:/var/lib/gconf/debian.defaults" to a read-only configuration source at position 3
Aug 15 08:53:46 bunsen gconfd (adam-13861): Resolved address "xml:readonly:/var/lib/gconf/defaults" to a read-only configuration source at position 4
Aug 15 09:32:46 bunsen gconfd (adam-13861): GConf server is not in use, shutting down.
Aug 15 09:32:46 bunsen gconfd (adam-13861): Exiting

Any suggestions on debugging it?  

Or should I just ignore it?

-- 
Thanks,
Adam