Description of problem: ConsoleKit simply stops assigning permissions to /dev/audio, /dev/sr0 and possibly other devices. Version-Release number of selected component (if applicable): ConsoleKit-0.3.0-2.fc10.x86_64 How reproducible: We have about 100 heavily used lab machines, i.e. users are logging in and out all day. After about 40 days of uptime I estimate that about 50% are affected. I cannot deliberately reproduce this but after enough log in/log out/user switches it seems to nearly always happen. Actual results: Upon logging in to an affected machine, ck-list-sessions shows nothing: dillweed:~$ ck-list-sessions dillweed:~$ Acl entries are not set on /dev/audio or /dev/sr0: dillweed:~$ getfacl -p /dev/audio # file: /dev/audio # owner: root # group: root user::rw- group::rw- mask::rw- other::--- dillweed:~$ getfacl -p /dev/sr0 # file: /dev/sr0 # owner: root # group: disk user::rw- group::rw- mask::rw- other::--- The following messages appear in /var/log/messages: Apr 15 13:15:32 dillweed gdm-simple-slave[13365]: WARNING: Unable to close session: no session open#012 Apr 15 13:15:32 dillweed gdm-session-worker[13730]: WARNING: Unable to open session: Unable to get information about the calling process#012 Apr 15 13:16:40 dillweed gnome-session[13743]: WARNING: Unable to determine session: Unable to lookup session information for process '13743' Apr 15 13:16:44 dillweed gdm-simple-slave[14173]: WARNING: Unable to open session: Unable to get information about the calling process#012 No new entries have appeared in /var/log/ConsoleKit/history for some time. The console-kit-daemon process is up and running: dillweed:~$ ps -elf | grep console-kit-daemon 5 S root 2422 1 0 80 0 - 25788 sys_po Mar03 ? 00:00:07 /usr/sbin/console-kit-daemon Expected results: On a machine which is not affected, ck-list-sessions shows users currently logged into the console: cucumber:~$ ck-list-sessions Session94: unix-user = '1179' realname = ' Elliott M Forney' seat = 'Seat1' session-type = '' active = TRUE x11-display = ':0' x11-display-device = '/dev/tty1' display-device = '' remote-host-name = '' is-local = TRUE on-since = '2009-04-15T19:09:58.645923Z' login-session-id = '1668' Acl entry is correctly added to /dev/audio and /dev/sr0: cucumber:~$ getfacl -p /dev/audio # file: /dev/audio # owner: root # group: root user::rw- user:idfah:rw- group::rw- mask::rw- other::--- cucumber:~$ getfacl -p /dev/sr0 # file: /dev/sr0 # owner: root # group: disk user::rw- user:idfah:rw- group::rw- mask::rw- other::--- Additional info: The following appears to (temporarily) fix the problem. 1. pkill -f console-kit-daemon 2. service haldaemon restart 3. Log out and back in
I experience a similar bug. In my case it appears to be associated to the usage of a external USB audio interface, an Edirol UA-25. I have yet to find out how to reproduce it consistently, but after a work session with the USB device sometimes the ck session will crash (ck-list-sessions will show nothing) and I'll have acl-related problems to access either the USB or the built-in ICH6 soundcard.
Thanks for the report. This kind of stress testing is really helpful. Can you please attach gdb to the ConsoleKit daemon when it is in this funny state and get a backtrace? Would help a lot. Thanks.
This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. 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 '10'. 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 10'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 10 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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 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.