You are not logged in.
I have been searching for a solution for the past two days and I am not winning.
I recently installed Arch Linux with Plasma 5 on an HP ProBook and everything works fine when I am connected to the office network where I work. However, as soon as I get home where I have two connections - a mobile connection using a Huawei B618 router and a Fibre connection using a Huawei HG659 - I am only able to open applications within 5 minutes from login. After that, no applications opens. It will show on the task bar for a second or two then disappear.
Surprisingly, when I am at work, I am not asked for a password to connect to the Wi-Fi network there while a password to the two Wi-Fi networks at home is required every time I start a new session.
Below is how my /etc/hosts files looks like.
127.0.0.1 localhost
127.0.0.1 localhost.localdomain localhost
I am not sure whether or not this is related to the /etc/hosts file or /etc/hostname with the following content.
localhost
Your help would be greatly appreciated.
Last edited by theoissilent (2018-07-21 09:10:54)
Offline
Offline
I have seen that section of the Wiki. Perhaps I should have added this. Before Arch Linux, I was running Fedora 25 where my hostname was set as "localhost" and there was no problem. I thought it would not be a problem on Arch Linux too.
Does Arch Linux not allow "localhost" as the host name? If so, how come it works perfectly fine when connected to the office network and not my home network?
Offline
Try opening apps from a terminal, that should give some error output.
https://superuser.com/questions/671614/ … -confusion
Arch is home!
https://github.com/Docbroke
Offline
If you don't set a valid hostname, you will see exactly this sort of behaviour. Fedora is not Arch. And no, localhost is not a valid hostname. That is why it is explicitly mentioned in the Installation Guide.
Offline
Try opening apps from a terminal, that should give some error output.
https://superuser.com/questions/671614/ … -confusion
When I try opening Chromium, I get the following error:
[goodies@localhost ~]$ chromium
Invalid MIT-MAGIC-COOKIE-1 key
(chromium:4487): Gtk-WARNING **: 10:25:57.655: cannot open display: :0
Surprisingly, I get a different error message I try to open Firefox or Thunderbird:
[goodies@localhost ~]$ firefox
Invalid MIT-MAGIC-COOKIE-1 keyUnable to init server: Could not connect: Connection refused
Error: cannot open display: :0
Offline
What happens after changing hostname to something unique ?
EDIT: MIT-MAGIC-COOKIE-1 should match hostname, otherwise x will not authorise program to open display.
Test with "xauth list"
Last edited by Docbroke (2018-07-21 08:46:51)
Arch is home!
https://github.com/Docbroke
Offline
Thank you very much, gentleman. It seems the issue was indeed the hostname. I have changed it to something unique and all is well.
I find it strange though that this only happens on my home networks and not at the office - unless the firewall used is the reason it does not happen there.
Once again, thank you so much.
Offline
Please mark as [SOLVED] by editing the title in your first post.
Offline
Surprisingly, I get a different error message I try to open Firefox or Thunderbird:
Do you really expect developers of different programs to use the exact same wording for their error messages? They do both include the same error message produced by X about the cookie.
About the difference between the two networks: hostname can be supplied via DHCP. Maybe one of your home routers does this and your DHCP client changes the hostname only if the system doesn't currently have a valid hostname. The cookie would be generated when X starts and use the old, invalid hostname.
Last edited by Raynman (2018-07-21 09:17:29)
Offline
Do you really expect developers of different programs to use the exact same wording for their error messages? They do both include the same error message produced by X about the cookie.
My message was based on my prior assumptions. I had earlier thought it was a system error, hence I expected the error messages to be the same without considering they were application specific error messages.
Offline