Description of problem:
I'm getting frequent crashes in console-kit-daemon. It happens when someone
tries to login via gdm. I'm not sure this problem is limited to ConsoleKit only.
I managed to catch the crash twice using gdb. Backtraces attached.

Version-Release number of selected component (if applicable):
ConsoleKit-0.2.3-1.fc8

How reproducible:
Frequently

Steps to Reproduce:
1. Configure user authentication via LDAP/TLS
2. Start gdm
3. Try to login
  
Actual results:
Dec 19 16:37:28 ws-ljw console-kit-daemon[3111]: GLib-CRITICAL:
g_async_queue_push: assertion `g_atomic_int_get (&queue->ref_count) > 0' failed
Dec 19 16:37:28 ws-ljw console-kit-daemon[3111]: GLib-CRITICAL:
g_async_queue_lock: assertion `g_atomic_int_get (&queue->ref_count) > 0' failed
Dec 19 16:37:28 ws-ljw console-kit-daemon[3111]: GLib-CRITICAL:
g_async_queue_length_unlocked: assertion `g_atomic_int_get (&queue->ref_count) >
0' failed
Dec 19 16:37:28 ws-ljw console-kit-daemon[3111]: GLib-CRITICAL:
g_async_queue_unlock: assertion `g_atomic_int_get (&queue->ref_count) > 0' failed
Dec 19 16:37:55 ws-ljw console-kit-daemon[3299]: GLib-CRITICAL:
g_async_queue_push: assertion `g_atomic_int_get (&queue->ref_count) > 0' failed
Dec 19 16:37:55 ws-ljw console-kit-daemon[3299]: GLib-CRITICAL:
g_async_queue_lock: assertion `g_atomic_int_get (&queue->ref_count) > 0' failed
Dec 19 16:37:55 ws-ljw console-kit-daemon[3299]: GLib-CRITICAL:
g_async_queue_length_unlocked: assertion `g_atomic_int_get (&queue->ref_count) >
0' failed
Dec 19 16:37:55 ws-ljw console-kit-daemon[3299]: GLib-CRITICAL:
g_async_queue_unlock: assertion `g_atomic_int_get (&queue->ref_count) > 0' failed
Dec 19 16:38:43 ws-ljw kernel: console-kit-dae[3300]: segfault at 0000000c eip
00d5dc4e esp b7fea310 error 4
...
Dec 19 16:46:56 ws-ljw console-kit-daemon[4255]: GLib-CRITICAL:
g_async_queue_push: assertion `g_atomic_int_get (&queue->ref_count) > 0' failed
Dec 19 16:46:56 ws-ljw console-kit-daemon[4255]: GLib-CRITICAL:
g_async_queue_lock: assertion `g_atomic_int_get (&queue->ref_count) > 0' failed
Dec 19 16:46:56 ws-ljw console-kit-daemon[4255]: GLib-CRITICAL:
g_async_queue_length_unlocked: assertion `g_atomic_int_get (&queue->ref_count) >
0' failed
Dec 19 16:47:14 ws-ljw console-kit-daemon[4255]: GLib-CRITICAL:
g_async_queue_push: assertion `g_atomic_int_get (&queue->ref_count) > 0' failed
Dec 19 16:47:16 ws-ljw console-kit-daemon[4255]:last message repeated 4 times
Dec 19 16:47:20 ws-ljw console-kit-daemon[4255]: GLib-CRITICAL:
g_async_queue_push: assertion `g_atomic_int_get (&queue->ref_count) > 0' failed
Dec 19 16:53:00 ws-ljw console-kit-daemon[4255]: WARNING: Error waiting for
native console 25 activation: Bad file descr
iptor
...
Dec 19 17:13:09 ws-ljw console-kit-daemon[5408]: GLib-CRITICAL:
g_async_queue_push: assertion `g_atomic_int_get (&queue->ref_count) > 0' failed
Dec 19 17:13:09 ws-ljw kernel: console-kit-dae[5408]: segfault at 0000000c eip
00cf7360 esp bf997d14 error 4

Additional info:
User authentication is done via LDAP over TLS and I get errors like
Dec 19 16:48:24 ws-ljw gdmgreeter[4577]: nss_ldap: failed to bind to LDAP server
ldaps://fs.icm.edu.pl/: Can't contact LDAP server
Dec 19 16:48:24 ws-ljw gdmgreeter[4577]: nss_ldap: failed to bind to LDAP server
ldaps://burza.icm.edu.pl/: Can't contact LDAP server
Dec 19 16:48:24 ws-ljw gdmgreeter[4577]: nss_ldap: could not search LDAP server
- Server is unavailable

even though I can get user information via `id' or ldapsearch without any problems.

If I start nscd, then it, too, starts complaining about not being able to bind
to LDAP server.

gdm-2.20.2-2.fc8
nscd-2.7-2
nss_ldap-257-4.fc8