X resource database is not maintained between connections

[matthewpersico]

Describe the bug
The X resource database is not maintained between connections.

To Reproduce
Steps to reproduce the behavior:

1. server command

 STARTED       ELAPSED          UID      PID     PPID TT       COMMAND
  Dec 23  16d21h52m40s        17245   270277        1 ?        /usr/lib/systemd/systemd --user
  Dec 23  16d21h52m40s        17245   270279   270277 ?         \_ (sd-pam)
  Jan 06   2d22h53m54s        17245  2941946   270277 ?         \_ /usr/bin/python3.11 /usr/bin/xpra start --attach=no --daemon=no --terminate-children=yes --exit-with-windows=yes
  Jan 06   2d22h53m53s        17245  2942028  2941946 ?         |   \_ /usr/libexec/Xorg-for-Xpra-S2941946 -noreset -novtswitch -nolisten tcp +extension GLX +extension RANDR +extension RENDER -auth /home/mpersico5/.Xauthority -logfile /run/user/17245/xpra/S2941946/Xorg.log -configdir /run/user/17245/xpra/S2941946/xorg.conf.d/2941946 -config /etc/xpra/xorg.conf -depth 24 -displayfd 4

2. client command

Start-Process -NoNewWindow -FilePath "C:\Program Files\Xpra\Xpra_cmd.exe" -ArgumentList "attach", "ssh://$using:hostname", "--ssh", "C:\Windows\System32\OpenSSH\ssh.exe"

3. specific action to trigger the bug
   a) Add the following to .Xdefaults: Xdefaults*loaded: true
   b) Load .Xdefaults: xrdb -merge ~/.Xdefaults
   c) Show that is the load succeeded: xrdb -query | grep Xdefaults*loaded
   d) Disconnect the xpra client on the local machine.
   e) Reconnect the xpra client on the local machine.
   f) Check the X resource database: xrdb -query | grep Xdefaults*loaded

The result of f) should be Xdefaults*loaded: true as there should be no reason to re-init the X resource database if the server is still running. All of the windows come back when I reconnect, so I know the server is still running. Is it the disconnection or reconnection process that clears the X resource database? Either way, I contend that should not be happening. It forces you to xrdb -merge ~/.Xdefaults every time you reconnect. Not fatal but definitely inconvenient.

System Information (please complete the following information):

• Server OS: Red Hat Enterprise Linux release 8.10 (Ootpa)
• Client OS: Windows 10 Enterprise, 22H2
• Xpra Server Version 6.1-r0
• Xpra Client Version 6.1.2 - Python 3.11, 64bit - commit gb0ed8cfd44 from v6.1.x branch with 0 local changes

[totaam]

The xsettings are managed by the server to try to ensure that client properties like DPI and such are applied to the server session.
I assume that you are talking about a seamless session, in which case the xrdb calls you make can be modified to be (re-)applied after the client has connected using the --start-after-connect.

[matthewpersico]

Yes. That is what I am referring to. So this is "working as designed"?

[matthewpersico]

Ah! You're suggesting that we add --start-after-connect xrdb -merge ~/.Xdefaults to our client connect start line?

[totaam]

add --start-after-connect xrdb -merge ~/.Xdefaults to our client connect start line?

Yes. I would add it to my server start command line, but the client one should also work.