Summary: | console-kit-daemon holds tty | ||
---|---|---|---|
Product: | ConsoleKit | Reporter: | Leo Borealis <lionmv> |
Component: | Daemon | Assignee: | william.jon.mccann |
Status: | NEW --- | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | egorov_egor, lionmv, radzio.cool, rob, vincent-fdt, vovik-wfa, xiaqqaix |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Leo Borealis
2010-08-31 17:32:07 UTC
This bug appears in Debian and ArchLinux both, may be in other distros. confirming. Archlinux, consolekit 0.4.1 when console-kit-daemon launches, it grabs currently active vt. ck-launch-session does not work on vt grabbed by console-kit-daemon. This bug breaks qingy experience: can not launch session twice on same tty, it hangs. If using other DM's, tty7 gets blocked after first use. workaround: add this line to rc.local to force console-kit-daemon launch on distant tty: openvt -c 63 -f -- console-kit-daemon --no-daemon & may not work with some graphical login managers, as they may launch it sooner. Anything running console-kit-daemon is affected. Another workaround is to run console-kit-daemon w/o "--no-daemon" before starting any X server. Otherwise, tty7 gets blocked every time. when running it without "--no-daemon", it grabs currently foreground vt, no matter what vt it was launched from. With "--no-daemon" you can pin it to desired vt in background. So it can stay on tty1 this way. It does not cause any problems there. I added it to rc.local I have slackware 13.1 64bit and kde 4.4.3 and i have the same problem. However i did what you suggested, with the rc.local, and it's ok now. I am worried about no progress. Surely, there is a workaround I've found but a workaround shouldn't be considered as a fix. I vote for a fix. Google "tty7 tty8" and you'll see everyone is complaining about the bug... It doesn't really matter (to me), but that's clearly no good behavior. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.