“…maybe that debug output is new in 5.10.0…”
My previous comment was addressing that speculation.
I just did a zypper dup
and the warning remains – as you probably expected.
“…maybe that debug output is new in 5.10.0…”
My previous comment was addressing that speculation.
I just did a zypper dup
and the warning remains – as you probably expected.
Sure.
Btw, it doesn’t actually seem to be a change in Qt anyway. This check/warning is in there unchanged since 2012 at least (haven’t looked further back).
I just did a
zypper dup
and the warning remains – as you probably expected.
Yes.
Btw, here on 42.3 I get a different warning when running “su -” and then YaST:
wolfi@amiga:~/> su -
Passwort:
amiga:~ # yast2
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
The wrong ownership warning seems to be caused by using “su” to switch to root instead of “su -”… (probably because su does not fully change the environment to root’s, so XDG_RUNTIME_DIR is still set to the user’s runtime dir which is owned by the user, not root, of course)
wolfi@amiga:~/> su
Passwort:
amiga:/home/wolfi/ # yast2
QStandardPaths: wrong ownership on runtime directory /run/user/500, 500 instead of 0
So in the end, it’s caused by xdg-su using “su” to switch to root (but that hasn’t changed either, since openSUSE 13.2 at least).
I am pretty sure that I didn’t see this message in the (not so distant) past, so maybe there was a change (bug?) to su at some point.
PS:
In theory this could lead to root owned files in the user’s XDG_RUNTIME_DIR, if you run applications as root via xdg-su (or “su”).
Not with YaST though, as Qt doesn’t use it because of the wrong ownership and prints this warning instead.
But that should not cause any real problems in any case I think, as XDG_RUNTIME_DIR is on a tmpfs anyway that gets “lost” on reboots.