On 2023-03-23 04:43, Bob Rogers wrote:
From: "Carlos E. R." <> Date: Thu, 23 Mar 2023 02:27:10 +0100
. . .
Have you tried "su -" instead of "su"?
No; I wasn't aware of this option. But I'm not sure what this does for me in terms of XAUTHORITY. It does give me less noise from QStandardPaths when I start yast2. Here's plain "su":
Noise in itself is not important :-)
root@orion> yast2 & [1] 5857 root@orion> QStandardPaths: runtime directory '/run/user/500' is not owned by UID 0, but a directory permissions 0700 owned by UID 500 GID 500 QStandardPaths: runtime directory '/run/user/500' is not owned by UID 0, but a directory permissions 0700 owned by UID 500 GID 500 QStandardPaths: runtime directory '/run/user/500' is not owned by UID 0, but a directory permissions 0700 owned by UID 500 GID 500 root@orion> [1]+ Done yast2 root@orion>
And here's "su -":
root@orion> yast2 & [1] 1715 root@orion> QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
root@orion> [1]+ Done yast2 root@orion>
So program configuration software certainly seems to consider this an improvement.
I know :-) The common language difference is that with "su -" you get the environment of the target user. And the home. cer@Telcontar:~> pwd /home/cer cer@Telcontar:~> su - Password: Telcontar:~ # pwd /root Telcontar:~ #
Can't say I'm tempted to try with the old XAUTHORITY though . . .
-- Bob
-- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)