Hi,
the networkmanager 1.14.7dev+3+g353743b99-1 set the hostname from DHCP in a way that break X11 authentication.
Symptom: "
Error: Can't open display: :0"
Diagnose: hostname and cat /etc/hostname are different
Hot Fix: revert hostname change:
sudo hostname -F /etc/hostname
or extend X11 authentication for new hostname
hostname
xhost +{YOUR NEW DHCP HOSTNAME}
cat /etc/NetworkManager/NetworkManager.conf
# Configuration file for NetworkManager.
# See "man 5 NetworkManager.conf" for details.
[main]
plugins=keyfile
[keyfile]
hostname-mode=none
may work too (not tested).
No issues here with all latest updates....Plasma w/runit init.
Best regards.
I also met similar issue few year ago, when NM was setting hostname based on actual network I was connected to and I was unable to login to X or so...
I solved it the same way as you, I created /etc/hostname file and it works ever since.
The problem came up when I created a fixed WiFi IP in my router.
The WiFi router had then set some DHCP tags that motivated NetworkManager to change the hostname according to the DHCP tag.
And bang, X11 broken.
I think NetworkManager can do weird things with the generic network configs like overwrite/ignore certain values.
Never liked NM, TBH: too complicated and bound to break from time to time. I've always used wicd for wifi, static or dhclient/dhcpcd for dynamic ethernet.
Also be prepared for NM 1.16, by default (or so it was in testing few days ago) I had to type my password to work with wifi, what a pain.