>> I simply wanted to point out that when running logind under >> systemd-shim, you'll get the error messages as shown in the attached >> screenshots. I'm pretty sure, some of our users will be concerned about >> this. > > Hello, I am a concerned user! ;-)
Same here. Expect to see more of these bug reports soon; between lightdm and the 'init' metapackage, there are a lot of dependencies on systemd trickling down in testing/unstable. For example, I'm still running sysvinit-core until more of the scripts get ported over by maintainers, but after today's upgrade I'm seeing these errors. # aptitude why systemd-shim i lightdm Depends consolekit | libpam-systemd i A libpam-systemd Depends systemd-sysv | systemd-shim (>= 6-4) # aptitude why libpam-systemd i lightdm Depends consolekit | libpam-systemd consolekit was already (and still is) installed, but libpam-systemd got installed anyhow, which then pulled in everything else. (The actual init management hasn't switched over, as systemd-sysv is not installed, but bits and pieces of systemd are taking effect anyhow.) Why the lightdm/etc stuff is effecting simple console logins, I have no idea, but there it is. I would love to have systemd present as it means I can start porting over our own local scripts, but my understanding was that it wouldn't actually "activate" until and unless we replaced the /sbin/init binary (via file swap or kernel parameter). I'm sure I don't understand all the details. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
