On 25.02.2024 01:45, Marc Chamberlin via openSUSE Users wrote:
On 2/24/24 11:25, Andrei Borzenkov wrote:
On 24.02.2024 21:02, Marc Chamberlin via openSUSE Users wrote:
Thanks Andrei for your time and responses, I will, like you did, intersperse my replies with yours...
On 2/23/24 22:05, Andrei Borzenkov wrote:
On 24.02.2024 00:46, Marc Chamberlin via openSUSE Users wrote:
Hello -
I am trying to grok how two X authority files get created and who/what is responsible for creating them.
Normally they are created by display manager that starts X server. And that is what I expect also, but the question remains, why am I not seeing the X authority files being created at /run/user/1000 on some of my OpenSuSE 15.4 systems all running with the KDE/Plasma desktop and using the SDDM display manager?
And where is it created? Where is what created? I don't understand your question, If you are asking me where are the X Authority files are created, I presume they are created in one of the two locations I have already pointed out. It seems to depend on what version of OpenSuSE is running. If 15.3 or earlier they seem to be created in each user's home directory ~/.XAuthority If !5.4 or later I find them usually at /run/user/UUID/xauth_<random characters>
That is correct. Upstream used X authority file in the home directory, SUSE patch moved it to $XDG_RUNTIME_DIR and finally modified version of SUSE patch was merged upstream which puts X authority in /tmp. So the obvious first guess would be that some of your 15.4 systems are using older version of SDDM or may be are not using SDDM at all. That is all that can be guessed from the outside.
When the X authority files should be created is when the first user logs in, and in our case there always is a "first" user that is automatically logged in when ever the system to restarted.
All that I am asking - where X authority file is actually located for the user session. I do not know what "first" user means, but X authority you describe is created when user logs in - so you must have some user session to even start talking about X authority. If we know where these files are created, we may try to guess why they are created in the "wrong" location. ...
It is never the case that there will NOT be a user logged in on each of our remote systems. On each system we have a user we call "TheController_<some description here>" This user automatically logs in whenever there is a system reboot and then starts up applications which
If you have user session that automatically logs in - why on earth cannot you start x11vnc as part of this session startup? Why you insist that it must run as separate systemd service?