On Sat, 1/30/16, Haines Brown <hai...@histomat.net> wrote:
Subject: [DNG] systemd is haunting me
To: dng@lists.dyne.org
Date: Saturday, January 30, 2016, 6:26 PM
I have been running Debian Sid on a laptop with a purged systemd for
quite a few months. Maybe when I now ran # aptitude update or
safe-upgrade for the first time after several months since the Sid
installation systemd-udevd seems to have switched my wireless interface
from wlan0 to wlp3s0.
Changing the entry in /etc/network/interfaces fixed that problem. So now
I could do a wireless aptitude update and safe-upgrade.
Even though in /etc/apt/preferences.d/systemd I have:
Package: "systemd"
Pin: origin ""
Pin-Priority: -1
Systemd was re-installed. Why didn't this systemd file prevent it?
Then I found that while root can run starx with no problem, when user
does it the desktop comes up frozen along with mouse and keyboard
input. I found this:
$ cat /var/log/Xorg.0.log | grep EE
(EE) systemd-logind: failed to gete session: The name \
org.freedesktop.login1 was not provided by any .service \
files.
Systemd is not on the system, so where did systemd-logind come from? How
can I block it and recover a usable virtual desktop for user?
Haines Brown
--------------------------------------------
I'm suffering this curse also. I am just now upgrading Jessie and something
wants to pull in libsystemd0. I have no idea what. Needless to say, I am NOT
going to install it. Unfortunately, Devuan's version of whack-a-mole is only
going to accelerate. We're going to be overrun if we don't get more hands on
deck . . .
golinux
_______________________________________________
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
