qingy is supposed to support consolekit since 1.0.0, which means you can use it to login into kde and use its mounter, reboot/halt menu options, etc. Just like you'd do with kdm or gdm. The problem is that it won't work out of the box. By default, qingy is configured to start X in the same tty that it's working, that's fine, because ttys are reused and all that. But there's a problem: when you use the DirectFB backend for qingy (most users surely want this) the consolekit session is not in "active" status, which prevents all the nice features of your desktop from working. Like this: # ck-list-sessions Session1: unix-user = '1000' realname = '(null)' seat = 'Seat1' session-type = '' active = FALSE x11-display = '' x11-display-device = '' display-device = '/dev/tty3' remote-host-name = '' is-local = TRUE on-since = '2011-06-23T09:24:02.220531Z' login-session-id = '1' idle-since-hint = '2011-06-23T09:24:32.421184Z' By applying a simple change to the configuration this can be circumvented, and then everything works. It's as simple as changing this line in /etc/qingy/settings x_server_tty = qingy_tty By this one: x_server_tty = unused_tty I propose two different ways to "fix" the problem: A) use this as the default, maybe add a comment in the config file using epatch B) put an ewarn or something in the ebuild, letting the user know that if s/he wants to use consolekit support s/he needs to do that change in the config file So, what do you think? Reproducible: Always
I'd second this - it took me ages to work out why my XFCE session was working nicely with consolekit when I started it from a terminal but not when starting it directly from qingy.
IMHO, to fix this issue by using special setting or ewarn is not enough. There are different problems for each different situation, listed below. Using with DirectFB GUI frontend: (a) To get an active CK session, x_server_tty=unused_tty is needed. (b) Logging-in to text console, CK session will be inactive always. Using with text-based frontend: x_server_tty=qingy_tty is needed. Using an autologin feature: Never get an active CK session. I wrote a workaround patch and submitted it to upstream. https://sourceforge.net/tracker/?func=detail&aid=3314721&group_id=82854&atid=567419
Created attachment 279333 [details, diff] Updated patch for qingy with ConsoleKit. Patch update. /etc/X11/Sessions/{Gnome, KDE-4} did not work correctly with old patch. Now fixed. Note: To use Qingy with this patch, you need to remove "nox11" option for pam_ck_connector.so in /etc/pam.d/system-login.
Hi, ConsoleKit support in Qingy should be fixed upstream now (svn only). Still missing proper checks in configure.ac and autologin support. Hope to release a new version soon.
Fixed in qingy-1.0.0-r1 by applying the patch qingy-1.0.0-consolekit-pam.patch obtained from upstream subversion. qingy-1.0.0: fix bug #359637 Updating sys-apps/qingy-1.0.0 autotools files: thanks to Justin for reporting, hal and axs for testing, Justin and s4t4n for fixing. Fix bug #462634 - sys-apps/qingy-1.0.0 build error: Thanks to Ole Langbehn for reporting, Rafal Muzylo, Ellison Marks, needle and Stephan Litterst for help. qingy-1.0.0-r1: Fix bug #372675 - sys-apps/qingy fails to keep ConsoleKit PAM session open with default setting (using DirectFB: Thanks to guboj for reporting, Richard Kenney for testing, Tomoh K. and s4t4n for fixing. Patches are from qingy upstream subversion. (Portage version: 2.2.8-r1/cvs/Linux x86_64, signed Manifest commit with key 618E971F)
