Description of problem:
At some point (e.g. login from text console) console-kit-daemon executes everything from /usr/lib/ConsoleKit/run-seat.d including udev-acl from udev package. This program should be called with udev-acl --action=some_action parameter, but console-kit-daemon executes udev-acl some_action. This causes 15s delay when you try to login from console (this is probably another bug of console-kit-daemon, it probably wait for timeout when process started from /usr/lib/ConsoleKit/run-seat.d fails)
Version-Release number of selected component (if applicable):
Try to login from text console
I realize, that /usr/lib/ConsoleKit/run-seat.d/udev-acl.ck supports only three actions (add, change, remove). So even with --action=some_action parameter ConsoleKit calls this program with arguments (seat_added, seat_active_session_changed) that make no sense.
At this point /usr/lib/ConsoleKit/run-seat.d/udev-acl.ck doesn't do anything useful and causes 15s login delays. To workaround this problem you can simple remove /usr/lib/ConsoleKit/run-seat.d/udev-acl.ck and for future updates it would be nice to remove this useless file from udev package.
From looking at the source, udev-acl DOES understand the "seat_active_session_changed" parameter. What exactly makes you think it does not?
And it's not useless, it applies the ACLs to devices marked with ACL_MANAGE=1 by udev (sound cards, for example).
I'm not seeing the delay you describe. More investigation of your problem is needed. Perhaps the delay is really in udev-acl, but it's not clear why it is occuring. Could you perhaps strace it?
Is this command quiet?: rpm -V udev ConsoleKit
`rpm -V udev ConsoleKit` is quiet
I was a bit confused how these *Kits works, but now I found what causing udev-acl.ck delay and this message in log files
console-kit-daemon: WARNING: The program /usr/lib/ConsoleKit/run-seat.d/udev-acl.ck didn't exit within 15 seconds; killing it
At some point udev-acl.ck tries to read data from /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/PNP0C0A:00/power_supply/BAT0/uevent, but this read call almost always take more than 15s to complete.
[user@host ~]$ date; cat /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/PNP0C0A:00/power_supply/BAT0/uevent; date
Wed Aug 4 14:43:38 CDT 2010
Wed Aug 4 14:44:01 CDT 2010
btw: the battery is few years dead
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13. 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 '13'.
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 13'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 13 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 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.