Red Hat Bugzilla – Bug 440349
console-kit-daemon segfaults from time to time
Last modified: 2015-01-14 18:20:48 EST
Description of problem:
I found that in / I collected a few core files. The last one from
2008-04-01 and the other with time stamps 2008-03-29, 2008-03-01
and 2008-02-26. All of these from the same version of
console-kit-daemon. gdb reports:
Core was generated by `/usr/sbin/console-kit-daemon'.
Program terminated with signal 11, Segmentation fault.
#0 0x0000000000eeb330 in g_str_hash () from /lib64/libglib-2.0.so.0
A full trace, after ConsoleKit-debuginfo was installed, has 125
threads and is attached.
Version-Release number of selected component (if applicable):
as you see from quoted dates it happens infrequently but consistently;
I am afraid that I do not know in what circumstances.
Created attachment 300153 [details]
gdb backtrace from a core produced by console-kit-daemon
Created attachment 300154 [details]
trace with glib2-debuginfo loaded.
Hm, maybe this trace where glib2-debuginfo is installed too will be
a bit more telling?
Hmm, that's really strange since we don't use a g_str_hash in the vt-monitor
code at all. We use a g_direct_hash.
> that's really strange ...
Maybe g_str_hash is hidden behind some macros or something inlined?
A stack trace for Thread 1 seems to imply g_hash_table_remove_internal()
but also indirectly.
That, for a change is from some F8 i686 machine - not mine. I was asked
for a help because its owner had troubles with mounting removable media.
All attempts were silently failing. Eventually running 'gnome-mount'
with '-v -t' revealed the following:
org.freedesktop.hal.storage.mount-removable no <-- (action, result)
A prolonged head scratching traced that back to a dead console-kit-daemon
with following "pearls" digged out from logs:
console-kit-dae: segfault at 0000000d eip 00133360 esp b7f33304 error 4
console-kit-dae: segfault at 0000000c eip 05d64cee esp b7eed310 error 4
Both entries are for ConsoleKit-0.2.3-3.fc8.1 installed on March 1st.
"2096" is apparently coincidental.
This does not happens very often (maybe because once console-kit-daemon
is dead it stays dead) and it appears to be related to some turbulencies
on dbus. Try to kill or restart messagebus service and maybe you can catch
See also bug #444546 (currently charged to dbus).
This is from yet another F8-i386 installation. A trawl through
logs brought the following which happened on Apr 12th:
console-kit-daemon: GLib-CRITICAL: g_async_queue_push: assertion
`g_atomic_int_get (&queue->ref_count) > 0' failed
console-kit-dae: segfault at 6374653b eip 002aa360 esp bfac1594 error 4
That one looks a bit different, though.
Should have look closer; 6374653b "address" above decodes to ";etc".
Should be fixed in:
> Should be fixed ...
Only that talks about F9 packages while samples quoted in comment #5
and comment #6 are from F8 installations. Should I open another bug
or this is not necessary?
Ah, well then it's a different bug. Sorry about that.
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '9'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 9's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 9 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.