initial xterm is started ignoring Xresources customization

[muwlgr]

Describe the bug on one of my remote hosts, I customized Xresources/Xdefaults/xrdb to run xterm with black background and white (or other color) text. however, when I start initial xterm session using xpra start ssh://hostname xterm , it gets started with white bg and black text. subsequent xterms, started using xterm & from the initial xterm, are started with black bg and white text, which I would expect from the initial xterm as well. xrdb -query shows identical printout from white-bg window as well as from black-bg. ssh -X hostname xterm opens black-bg xterm with white text what could I be doing wrong ?

To Reproduce Steps to reproduce the behavior:

1. server command just installed xpra in the server side, did not change its configuration
2. client command xpra start ssh://hostname xterm
3. specific action to trigger the bug just observe the initial xterm with white bg, the subsequent xterms with black bg

System Information (please complete the following information):

• Server OS: [e.g. RHEL 8.x]

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Debian
  Description:    Debian GNU/Linux 12 (bookworm)
  Release:        12
  Codename:       bookworm

• Client OS: [e.g. Windows 10]

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Debian
  Description:    Debian GNU/Linux 12 (bookworm)
  Release:        12
  Codename:       bookworm

• Xpra Server Version [e.g. 4.2.3] xpra 6.2.0-r2-1
• Xpra Client Version [e.g. 4.3] xpra 6.2.0-r2-1

Additional context

$ grep . /etc/apt/sources.list.d/xpra.sources 
Types: deb
URIs: https://xpra.org
Suites: bookworm
Components: main
Architectures: amd64 

[totaam]

My guess is that the first xterm is starting before the xsettings have been applied or synchronized. Try with --xsettings=no Or start your xterm with --start-after-connect=xterm.

[muwlgr]

xpra start ssh://hostname --xsettings=no xterm starts white-bg xterm (with subsequent xterms spawned from it having black-bg)

xpra start ssh://hostname --start-after-connect=xterm does not start anything, only hangs the session on the client side until I press Ctrl+C

[totaam]

Sorry, no idea - and no time to spend on this.

[muwlgr]

ssh -X hostname xterm opens black-bg xterm with white text (which is expected) what could I be doing wrong ?

[totaam]

Wild guess: something should load xrdb into the session before launching the xterm?

[muwlgr]

I don't have ~/.xsession in my home. I don't have xrdb calls in my ~/.bash* scripts (only some lines recorded in .bash_history or .xsession-errors) but still, ssh -X hostname xterm shows black bg (expected) xpra start ssh://hostname xterm shows white bg (wrong, how to fix?)

[muwlgr]

I remember it working as expected with previous versions of xpra. I have a different host on which xpra start ssh://hostname xterm starts a black-bg xterm same as ssh -X hostname xterm does

[muwlgr]

sorry, I don't have this 'healthy' host anymore. probably because I did not start xpra server part on it for too long after the update. It only had LANG=uk_UA.UTF-8 startkde command in its ~/.xsession but removing and restoring this line did not have much impact. black-bg on first login, white-bg on subsequent logins after first logout (and black-bg for any subsequently-started xterms).

[muwlgr]

further observations: any xterm started with xpra start ssh://hostname ... , starts with white-bg. any child xterm started from white-bg xterm with xterm & starts with black-bg any xterm started with ssh -X hostname ... starts with black-bg