https://bugs.kde.org/show_bug.cgi?id=370608
kolAflash <kolafl...@kolahilft.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|INVALID |---
--- Comment #2 from kolAflash <kolafl...@kolahilft.de> ---
New fact (tested on openSUSE):
The variable XAUTHORITY is already set directly after login to the value
"/tmp/xauth-1000-_0", which it still has when the bug start appearing (usually
some hours after logging in).
But XAUTHORITY is only set if using SDDM as display manager. If using KDM as
display manager, XAUTHORITY doesn't get set.
So "unset XAUTHORITY" and "XAUTHORITY=~/.Xauthority" only seem to be
workarounds.
And the actual bug is probably something else. My current guess is, that the
file "/tmp/xauth-1000-_0" becomes broken somehow. But I'll have to wait for the
bug to appear again to verify.
Both systems I'm experiencing the bug on had been updated from KDE 4 (openSUSE
13.1) to KDE/Plasma 5 (openSUSE 42.1). I'm not experiencing the bug on any
systems which had been set up from scratch using KDE 5.
But XAUTHORITY is also set to /tmp/xauth-1000-_0 on those newly set up systems.
So that variable should probably really have that value.
And please keep in mind: The bug appears on Arch Linux and openSUSE, so there's
some chance it's by KDE.
(yes, it could also be an systemd bug - I'm keeping that in mind)
--
You are receiving this mail because:
You are watching all bug changes.
