After migrating to systemd (in order to use gnome 3.8), I noticed that the first time I login to my system via ssh right after a reboot is very slow, it takes about 90 seconds. I experimented a lot and it seems that the problem is with sys-auth/pambase-20120417-r2. If I disable the consolekit use flag (which is enabled by the desktop profile) and leave the systemd flag enabled (which I enabled in make.conf during the systemd migration), login now is as fast as before. Reproducible: Always
More generally, should there be a dedicated profile for gnome 3.8 that enables the systemd use flag and disables consolekit? Until that happens, should the wiki page about systemd migration recommend disabling the consolekit flag in make.conf?
Would be better to try to know why are they conflicting now for pambase
*vaguely points towards pambase + systemd flag* This is enabling session-tracking. If you hack the build to disable the systemd dependency on pambase, it goes away even with consolekit flag on gdm and such. Though I noticed more than just slow initial logins (hung shutdowns, slow vt switching, sometimes my testing computer would begin to weep uncontrollably, etc).
Sounds like you're hitting a time-out. Is your network configuration correct (DNS, hostname and so on)?
(In reply to Jeroen Roovers from comment #4) > Sounds like you're hitting a time-out. Is your network configuration correct > (DNS, hostname and so on)? Yes. Besides, I have disabled the UseDNS in my sshd_config. I can reproduce this with a virtual machine. I start the virtual machine and when systemd has finished booting in it, I try following (in the host): time ssh root@192.168.5.2 true and it always takes about 90 seconds to complete.
@systemd, please advice, as far as I remember (I can be wrong though), consolekit and systemd can not be enabled the same time, otherwise it gonna be lots of "fun".
(In reply to Mikle Kolyada from comment #6) The systemd profiles have consolekit in use.mask. This bug is several years old, so I wonder if people still run into it. If there is still a problem, a REQUIRED_USE constraint might suffice. REQUIRED_USE="?? ( consolekit elogind systemd )"
(In reply to Mike Gilbert from comment #7) > (In reply to Mikle Kolyada from comment #6) > > The systemd profiles have consolekit in use.mask. > > This bug is several years old, so I wonder if people still run into it. If > there is still a problem, a REQUIRED_USE constraint might suffice. > > REQUIRED_USE="?? ( consolekit elogind systemd )" I had the same idea in mind, will implement soon
should be fixed in the tree
