| Summary: | sys-apps/qingy - request for live ebuild | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | JMW <jessemichaelwilson> |
| Component: | New packages | Assignee: | Gentoo's Team for Core System packages <base-system> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | enhancement | Keywords: | EBUILD |
| Priority: | Low | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | Ebuild for qingy-9999. | ||
|
Description
JMW
2013-03-24 19:05:07 UTC
Created attachment 343128 [details]
Ebuild for qingy-9999.
SVN version of qingy which now has support for consolekit.
If you want to make a snapshot, fine. But getting a live ebuild for qingy seems to me like a huge waste of time and nothing else. (In reply to comment #2) > If you want to make a snapshot, fine. But getting a live ebuild for qingy > seems to me like a huge waste of time and nothing else. snapshot would be useful as qingy is the only 'getty in Portage with problems using ConsoleKit, with some of it's valid configurations the one in Portage relies on pambase[consolekit] and the pam_ck_connector.so module as it lacks internal support which is only in svn however the reason I haven't made a snapshot for it, is the lack of verification if autologin + ConsoleKit combination works there yet or not last I checked it was still having issues, and it wasn't possible to autologin and get 'active = TRUE' session (in ck-list-sessions output) :-/ reporter, has that improved in svn? if so, I can be convinced of creating a snapshot Ok, quite frankly, I DON'T know what autologin actually does. I have it set for all of my qingy tty's, but it has NEVER logged me in automatically, and the "autologins" in the settings file could only be there as a hack to prevent some unwanted behavior. Nevertheless, they ARE present in the settings file, and when I was running the old qingy, I wouldn't get "active = TRUE" when on a second active X-session on another account run from qingy (yes, both accounts run from qingy). The last time I checked with the SVN qingy, I DID get "active = TRUE" in ck-list-sessions (again, with autologin in the settings file, but no idea what it's doing). I can't do anything else to test whether consolekit is functioning properly 100% of the time with the new qingy until I compile a new kernel so that I can actually login to another functional xserver, since I did an emerge -avDNut world and I have binary version mismatch between the Xorg nvidia driver and the kernel nvidia driver. I am attempting to get a working pulseaudio multiuser with fast user switching setup with qingy, and this requires functional consolekit, so yes, I am definitely the person to test the new qingy and report details about how the new qingy works with consolekit, and I will definitely give any further details you need, just as soon as I get my system back in a consistent state. I definitely think a snapshot is a good idea, and anyone who wants to test the very latest qingy can always grab the ebuild from this bug report, so if you feel comfortable writing the snapshot ebuild now, I think some users will benefit. I want to be able to provide useful bug reports to Michele Noberasco, so I will continue running the live version, and updating frequently, but having a snapshot version that I can fall back on if the live version fails will help me greatly. Ok. I'm off to compile my new kernel. I'll check back here when I'm done. Clarification: "can actually login to another functional X server" should be "can't actually login to another functional X server", and I have taken off the "nox11" from the end of "sesson optional pam_ck_connector.so" in /etc/pam.d/system-login. I don't know if this is still necessary in the latest SVN, but those were the instructions given along with the patch submitted at http://sourceforge.net/tracker/?func=detail&aid=3314721&group_id=82854&atid=567419. Just letting you know so you'll be able to test this functionality. |
