I think this may be the route to success, because I can do successfully the following (starting in the terminal of the root user)
manj-laptop ~]# su - manolo
05:58:22 me@manj-laptop ~ → export DISPLAY=':0.0'
05:58:59 me@manj-laptop ~ → echo $DISPLAY
05:59:09 me@manj-laptop ~ → firefox &
05:59:16 me@manj-laptop ~ → ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
this starts firefox as the personal user. So I guess I need to find out how to set this value for DISPLAY constantly. I guess it is not adding export DISPLAY=':0.0' to /etc/profile which I will try as a temporary solution maybe anyway.
Did you install today’s Stable Update? If so, then you should have paid attention to this…
You probably need to set a new password in order for yescrypt to be able to work on your old login, because your old login was still using sha512, and with the new encryption algorithm in place, logind can probably not recognize the sha512-encrypted password for your account in /etc/shadow.
My 2 cents – If your data is disposable; you could simply start over while this new information is fresh in your mind. There will probably be some blowback; some shock and horror, from the community at large for even hinting at this … but … often, it just saves time and complication. That is all. Cheers.
hm. I started this on Oct 4th, and certainly ran a pacman -Syu after things went sour. So I am pretty so, I guess I should have that update installed.
The things you have listed to pay attention to boil down to “This should not require any manual intervention.” So I wouldn’t really know which action to take away from this.
What I don’t get is what yescript actually is. I can find it neither via pacman -Ss yescript, pacman -Sl | grep yescript, nor in pamac. A .tar downloads exist at https://www.openwall.com/yescrypt/ though. Can someone shed some light on this?
From a naive point of view a package should exists in order to use it, or do I understand something fundamentally wrong here?
tried that once again just now … the new password is still not accepted as login in lightdm.