On Mon, Sep 17, 2012 at 10:45 AM, Stefan G. Weichinger <li...@xunil.at> wrote: > Am 16.09.2012 20:45, schrieb Canek Peláez Valdés: > >> This workaround also works in my systemd-only overlay. So, if you have >> the systemd flag in any of those four packages, disable it and >> everything should work. Just to be explicit, the versions are: >> >> gnome-base/gdm-3.4.1-r1 >> gnome-base/gnome-session-3.4.2.1 >> gnome-base/gnome-shell-3.4.2 >> sys-auth/polkit-0.107:0 > > confirming this. I have exactly your mentioned versions with > USE="-systemd" and suspend/hibernate option returns, I could mount/use a > DVD right now ... yes!
OK; now I can put this whole thing behind me. You can read the bug again: https://bugs.freedesktop.org/show_bug.cgi?id=53905 but the short answer is that you cannot let both systemd and consolekit to manage sessions. The problem (in my case) was that I was using accountsservice 0.6.22, which depends on consolekit. I upgraded to accountsservice 0.6.24 (which can depend on systemd), I removed all consolekit USE-flags (except for bluez: bluez uses consolekit to pull either consolekit or systemd; I reported a bug[1]), and after an emerge -uDNv world, I removed consolekit (I didn't had any other package depending on it). Now everything works as it should, in both my overlay and in the vanilla Gentoo tree. Be aware: it works *with systemd*; maybe it works without it, but I don't know (nor care). All the GNOME session management is moving to systemd, and I think it's a great idea. Support for consolekit (which is no longer maintained) is still there, but I don't know for how long. If you want to keep using (the unmaintained) consolekit, be sure to set "-systemd" in your USE flags. Do not mix systemd and consolekit, or this bug will hit you. Regards. [1] https://bugs.gentoo.org/show_bug.cgi?id=436180 -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
