[Bug 148454]

[Lennart-poettering]

I have now reverted the patch and reopened this bug. VT_WAITEVENT is
inherently racy, since events that happen between the time we return
from a VT_WAITEVENT and go back into VT_WAITEVENT are completely lost.
That has the effect that when coming back from a suspend sometimes VT
switches are not noticed and ACLs incorrectly set up.

Kay has now proposed a new kernel interface that helps us to fix this
properly. This is currently in discussion on LKML.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to consolekit in Ubuntu.
https://bugs.launchpad.net/bugs/148454

Title:
  console-kit-daemon spawns too many threads

Status in ConsoleKit:
  Confirmed
Status in “consolekit” package in Ubuntu:
  Opinion
Status in “consolekit” package in Fedora:
  Invalid

Bug description:
  since upgrading to gutsy beta htop shows about fifty processes like
  the following

  pid user pri ni virt res shr s cpu% mem% time+ command
  7582 root 23 0 7456 2016 1336 s 0.0 0.2 0:00.00 /usr/sbin/console-kit-deamon

  It maybe the case that console-kit-daemon starts a thread for each
  console that can theoretically exist. On Linux
  (/usr/include/linux/vt.h) MAX_NR_CONSOLE is defined to be 63.

  Note that those processes do not show up in DEFAULT top or ps output
  --BUT-- if you run either of those tools with the -H parameter, so as
  to display all the threads of a process, then they do show up.

To manage notifications about this bug go to:
https://bugs.launchpad.net/consolekit/+bug/148454/+subscriptions