Yes, knowing why the console FD is wrong would be very nice... Then upstream
could fix the bug in a more appropriate fashion.
But in the meantime it will at least make Ubuntu usable for some of us.
Also, the original sources had this "FIXME" warning where you added the
retry loop, showing that something had to be done there. So even if the
root of the problem is fixed upstream, keeping the retry loop in the
code would still be a plus, IMHO.
Just out of curiosity, I will also try with a shorter sleep time to
determine the "race time" more accurately.
** Changed in: consolekit (Ubuntu Lucid)
Status: Triaged => In Progress
--
Active VT tracking can fail at startup
https://bugs.launchpad.net/bugs/544139
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
