Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 559444 - net-misc/networkmanager-1.0.4-r1: invalid MIT-MAGIC-COOKIE after hostname changes
Summary: net-misc/networkmanager-1.0.4-r1: invalid MIT-MAGIC-COOKIE after hostname cha...
Status: RESOLVED TEST-REQUEST
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Unspecified (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Linux Gnome Desktop Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-02 19:02 UTC by Patrick Lauer
Modified: 2016-07-07 18:57 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick Lauer gentoo-dev 2015-09-02 19:02:24 UTC
Sep  2 20:48:35 localhost NetworkManager[2643]: <info>  (wlp3s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'WLAN16'.
Sep  2 20:48:35 localhost NetworkManager[2643]: <info>  (wlp3s0): device state change: config -> ip-config (reason 'none') [50 70 0]
Sep  2 20:48:35 localhost NetworkManager[2643]: <info>  Activation (wlp3s0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Sep  2 20:48:35 localhost NetworkManager[2643]: <info>  dhcpcd started with pid 4190
Sep  2 20:48:36 localhost NetworkManager[2643]: <info>    address 192.168.1.40
Sep  2 20:48:36 localhost NetworkManager[2643]: <info>    plen 24 (255.255.255.0)
Sep  2 20:48:36 localhost NetworkManager[2643]: <info>    gateway 192.168.1.1
Sep  2 20:48:36 localhost NetworkManager[2643]: <info>    server identifier 192.168.1.1
Sep  2 20:48:36 localhost NetworkManager[2643]: <info>    lease time 604800
Sep  2 20:48:36 localhost NetworkManager[2643]: <info>    nameserver '192.168.1.1'
Sep  2 20:48:36 localhost NetworkManager[2643]: <info>    domain name 'localdomain'
Sep  2 20:48:36 localhost NetworkManager[2643]: <info>  (wlp3s0): DHCPv4 state changed unknown -> bound
Sep  2 20:48:36 localhost NetworkManager[2643]: <info>  (wlp3s0): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
Sep  2 20:48:36 localhost NetworkManager[2643]: <info>  (wlp3s0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
Sep  2 20:48:36 localhost NetworkManager[2643]: <info>  (wlp3s0): device state change: secondaries -> activated (reason 'none') [90 100 0]
Sep  2 20:48:36 localhost NetworkManager[2643]: <info>  NetworkManager state is now CONNECTED_LOCAL
Sep  2 20:48:36 localhost NetworkManager[2643]: <info>  NetworkManager state is now CONNECTED_GLOBAL
Sep  2 20:48:36 localhost NetworkManager[2643]: <info>  Policy set 'WLAN16' (wlp3s0) as default for IPv4 routing and DNS.
Sep  2 20:48:36 localhost NetworkManager[2643]: <info>  (wlp3s0): Activation: successful, device activated.
Sep  2 20:48:36 localhost NetworkManager[2643]: <info>  Setting system hostname to 'unknown5ce0c58e77db' (from address lookup)


So hostname ends up as unknown5ce0c58e77db and X breaks because invalid magic cookie and lots of cursing happens.

Setting the config to static values avoids this hostname change and has the advantage of not breaking stuff, but that's silly.
Comment 1 Alexandre Rostovtsev (RETIRED) gentoo-dev 2015-09-02 19:22:18 UTC
What is broken about that hostname? Does it violate some rfc, or ...?
Comment 2 Patrick Lauer gentoo-dev 2015-09-03 12:20:38 UTC
I'm not sure yet how stuff breaks, but starting new X apps is impossible as they all complain "invalid MIT-MAGIC-COOKIE"

Setting a static config for this network that forces an IP and hostname avoids the issue completely. So at some point in divining or setting hostname things bo boom.
Comment 3 Pacho Ramos gentoo-dev 2015-09-04 14:03:14 UTC
This shouldn't occur as soon as /etc/X11/xinit/xinitrc.d/00-xhost is really being executed :|
Comment 4 Pacho Ramos gentoo-dev 2016-07-07 18:57:33 UTC
You can maybe retry with 1.2.2

If still happening, you will need to check if /etc/X11/xinit/xinitrc.d/00-xhost is present and is being executed with your way of launching X