gconfd crashes...

[Mike Harding]

I have had gconfd-2 crashing lately, which freezes up evolution.  Blah.

Anyway - has this happened to anyone else?

Also, could this be caused by having a tinderbox building away on my
desktop machine (Marcus)?

I did see this in /var/log/messages...

Jul 27 14:59:04 bsd kernel: pid 55827 (gconfd-2), uid 1001: exited on signal 6
Jul 27 15:18:52 bsd gconfd (mvh-25589): gmem.c:172: failed to allocate 134217728 bytes
Jul 27 15:18:52 bsd kernel: pid 25589 (gconfd-2), uid 1001: exited on signal 6
Jul 27 15:44:20 bsd gconfd (mvh-5149): gmem.c:172: failed to allocate 134217728 bytes
Jul 27 15:44:20 bsd kernel: pid 5149 (gconfd-2), uid 1001: exited on signal 6
Jul 27 15:44:22 bsd gconfd (mvh-77369): Failed to get lock for daemon, exiting: Failed to lock '/var/tmp/gconfd-mvh/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable)
Jul 27 15:46:56 bsd gconfd (mvh-77367): gmem.c:172: failed to allocate 8388608 bytes
Jul 27 15:46:56 bsd kernel: pid 77367 (gconfd-2), uid 1001: exited on signal 6
Jul 27 15:47:50 bsd <Jul 27 15:47:50gconfd (mvh-80875): gmem.c:135: failed to allocate 670 bytes
Jul 27 15:47:50 bsd kernel: pid 80875 (gconfd-2), uid 1001: exited on signal 6
Jul 27 15:48:17 bsd <Jul 27 15:48:17gconfd (mvh-81150): gmem.c:135: failed to allocate 670 bytes
Jul 27 15:48:17 bsd kernel: pid 81150 (gconfd-2), uid 1001: exited on signal 6
Jul 27 15:48:58 bsd <Jul 27 15:48:58gconfd (mvh-81425): gmem.c:135: failed to allocate 670 bytes
Jul 27 15:48:59 bsd kernel: pid 81425 (gconfd-2), uid 1001: exited on signal 6
Jul 27 15:49:41 bsd <Jul 27 15:49:41gconfd (mvh-81567): gmem.c:135: failed to allocate 670 bytes
Jul 27 15:49:41 bsd kernel: pid 81567 (gconfd-2), uid 1001: exited on signal 6
Jul 27 15:52:16 bsd <Jul 27 15:52:16gconfd (mvh-82195): gmem.c:135: failed to allocate 670 bytes
Jul 27 15:52:16 bsd kernel: pid 82195 (gconfd-2), uid 1001: exited on signal 6
Jul 27 15:52:18 bsd gconfd (mvh-84451): Failed to get lock for daemon, exiting: Failed to lock '/var/tmp/gconfd-mvh/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable)
Jul 27 16:07:22 bsd kernel: pid 84452 (gconfd-2), uid 1001: exited on signal 6
Jul 27 16:07:22 bsd gconfd (mvh-84452): Received signal 11, dumping core. Please report a GConf bug.
Jul 27 16:16:46 bsd kernel: pid 46225 (gconfd-2), uid 1001: exited o
Jul 27 16:16:46 bsd kernel: n signal 6
Jul 27 16:16:46 bsd gconfd (mvh-46225): Received signal 11, dumping core. Please report a GConf bug.

- Mike H.