http://bugzilla.opensuse.org/show_bug.cgi?id=1023588 Bug ID: 1023588 Summary: NetworkManager Causes Xauthority Conflicts Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: openSUSE 42.2 Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening@forge.provo.novell.com Reporter: bugs@tmarques.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- After stock install, /etc/hostname is set to "linux.suse", as I didn't touch this. This is the host name that is set on boot. After NetworkManager comes up, this changes to another hostname, which is what DNSMasq on my server sends. The result: Lightdm cannot start X session as it gives me an invalid MIT-MAGIC-COOKIE. I have to restart Lightdm shortly after boot to be able to login. Just now found the issue because I booted without network and logged in to the desktop. Then I connected the network and could not open apps anymore. xsession-errors revealed: Invalid MIT-MAGIC-COOKIE-1 keyThunar: Cannot open display: Invalid MIT-MAGIC-COOKIE-1 keyUnable to init server: Could not connect: Connection refused Upon adding the cookie of the previous hostname with the new one, everything works fine. I think this was what was causing me segfaults on coming out of suspend, 1/3 times or so, but will have to see how it plays out. YAST complained about configuration conflicts on the network settings until I disabled "set hostname by DHCP" function. NetworkManager problem persists after rebooting the service. I looked at dhclient settings but the problem itself is not obvious and dhclient files also offer no suggestion about how to turn the hostname change off. -- You are receiving this mail because: You are on the CC list for the bug.