Larry Finger composed on 2017-09-29 12:18 (UTC-0500):

Dominique Leuenberger / DimStar wrote:

...

On Fri, 2017-09-29 at 11:24 -0500, Larry Finger wrote:

...

...

valid MIT-MAGIC-COOKIE-1 keyQXcbConnection: Could not connect to display :0

...

Is your DHCP server sending you a hostname? Generally, this error appears when the hostname 'changes' while the session is already up (which is for example the default with user-manager networks as managed by NetworkManager)

...

OTOH, I don't see anything in 0928 that should impact that. did you upgrade from 0927 or something older? Does the error persist across reboots?

The hostname changes were the problem. I used the ncurses version of YaST to set and lock the hostname, and now all is well.

Anyone know the mechanism YaST uses to "lock the hostname"? Making hostname immutable causes netcfg updates to fail. -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Andreas Schwab composed on 2017-10-02 10:47 (UTC+0200):

Felix Miata wrote:

...

Anyone know the mechanism YaST uses to "lock the hostname"?

Set the "Set Hostname via DHCP" option to "no" I didn't ask how to make YaST lock the hostname. By "mechanism" I mean how does YaST cause a lock to occur when setting hostname option via DHCP to no. IOW, what/where does YaST write to disk when setting/unsetting the lock? -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation)

Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Hi, looks like new version of NetworkManager/dnsclient silently ignores this settings and sets hostname .. On 2 October 2017 at 11:27, Andreas Schwab wrote:

On Okt 02 2017, Felix Miata wrote:

...

I didn't ask how to make YaST lock the hostname. By "mechanism" I mean how does YaST cause a lock to occur when setting hostname option via DHCP to no. IOW, what/where does YaST write to disk when setting/unsetting the lock?

See /etc/sysconfig/network/dhcp (DHCLIENT_SET_HOSTNAME).

Andreas.

-- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

El 29-09-2017 a las 13:38, Dominique Leuenberger / DimStar escribió: Generally, this error

appears when the hostname 'changes'

Wow.. there is some very low hanging fruit right there.. I hope wayland does not carry this insanity forward to the future. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

looks like NetworkManager/dhclient ignore DHCLIENT_SET_HOSTNAME="no". workaroud is remove 'set-hostname' from `/etc/dhclient.conf` On 2 October 2017 at 14:33, Cristian Rodríguez wrote:

El 29-09-2017 a las 13:38, Dominique Leuenberger / DimStar escribió: Generally, this error

...

appears when the hostname 'changes'

Wow.. there is some very low hanging fruit right there.. I hope wayland does not carry this insanity forward to the future. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org