You are not logged in.
After an update made on July the 12th, LXDE is no longer able to start any application from menu or from application bar. The computer is NOT freezed: i have Lxterminal in autostart and it's running normally.
Bash commands work smoothly, But every program I try to start from Lxterminal (that in normal condition would work without problems) show the same error, here some examples:
gparted
Authorization required, but no authorization protocol specified
(gpartedbin:6702): Gtk-WARNING **: 12:55:09.244: cannot open display: :0
chromium
Authorization required, but no authorization protocol specified
[884:884:0714/125337.923424:ERROR:ozone_platform_x11.cc(244)] Missing X server or $DISPLAY
[884:884:0714/125337.923453:ERROR:env.cc(258)] The platform failed to initialize. Exiting.
firefox
Authorization required, but no authorization protocol specified
Error: cannot open display: :0
So i tried downgrade the system back to July the 5th and everything started working again.
If from this working state I run an update, the problem returns.
I tried to update with lxde in IgnoreGroup in pacman.conf with no success... so I don't know how to solve it
Last edited by ziomarco (2024-07-19 09:25:36)
Offline
after a whole day of back and forth....with the last pacman -Syu the problem is resolved by itself
Much ado about nothing
Last edited by ziomarco (2024-07-14 18:56:45)
Offline
It happens again! This make me crazy....
I found a workaround: when the problem occurs
systemctl restart lxdm
resolves the issue.
this suggest that something is starting in the wrong sequence...
Last edited by ziomarco (2024-07-18 10:18:34)
Offline
Offline
thank you seth, yuor suggest did the trick!
Offline
Your homework is gonna be to figure "why"
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
Offline
After your help I realized that Xorg and LXDE looks at hostname before starting a program. In my case /etc/hostname was not set
The new questions are: this Arch installation date from 2022, why does the problem arises only now?
why the applications started by LXDE autostart worked well and the ones started by mouse click or from console failed ?
Offline
The problem is that w/o a static hostname, your networkmanager (certainly "NetworkManager") will get you a dynamic one via dhcp.
Since X11 is a network protocol that accidentally also can color pixels, pretty much everything is FQDN sensitive, the XAUTHORITY cookie is bound to the domain name and if that changes *after* X11 started, things break because you're running X11 on the "wrong" host.
Offline