You are not logged in.
I've seen an issue the last month or so, that after a period of time (unsure how long really, my computer is rarly rebooted), a few days or more, I'm suddenly not allowed to start X applications anymore.
This includes both from the KDE start menu and from terminals. I only get this message:
When trying to start kwrite for instance:
Invalid MIT-MAGIC-COOKIE-1 key kwrite: cannot connect to X server :0
Or with sudo I've seen:
No protocol specified
kwrite: cannot connect to X server :0
This happens to all applications until I restart the X server and it's starting to get annoying to restart it every few days due to this. I checked my .Xauthority file and it is intact (I took a backup to see if it was mangled by something).
There's nothing in the kernel logs or X.org log, only messages from boot time.
I'm running testing on with the open source radeon drivers if it matters, x86_64.
Has anyone else seen something like this?
Offline
Check your hostname settings.
Offline
Nothing seems out of the ordinary there.
I have my hostname set in /etc/hostname and there's an entry in /etc/hosts for it pointing to 127.0.0.1
`hostname` returns the correct host name as well and I can ping both it and localhost with no problems.
Offline
Similar issues have been solved by taking care of hostname, which may be tricker that expected https://bbs.archlinux.org/viewtopic.php … 3#p1271493
MIT-MAGIC-COOKIE-1 issue: https://bbs.archlinux.org/viewtopic.php?id=163644 - no solution.
If you're trying to run graphical apps as root or with sudo, read https://wiki.archlinux.org/index.php/Ru … ps_as_root
Offline
It's not a sudo issue, and the hostname looks good:
[avenger@eric Series]$ hostname
eric
[avenger@eric Series]$ hostname -f
localhost.localdomainThe MIT-MAGIC-COOKIE-1 issue seems more like it, except the fact that it only happens after the system has been up a while and it's for every application.
I'm not trying to run X-apps as root (but even that works before the issue appears).
This issue is really strange...
Offline
I did some more checking out, and it does appear to be a hostname thing. I changed my hostname from to 'eric.lan' and now it works. I got the hostname from the ~/.Xauthority file (and I guess that is the hostname/domain my dhcp server wants me to take).
So it looks like the fully qualified hostname is set wrong somewere, not sure what could change it while the system is running. The issue described in your first link seems to match perfectly, too bad the issue couldn't be tracked down further.
I'm not running network manager or something like that, only dhcpcd as a systemd service.
Offline