Xpra icon changes

[michael]

Icon of Xpra in taskbar (Win7) sometimes changes during use to the symbol of other applications (Outlook, Firefox, ...) - confusing

Xpra 2.3.1 64 Bit Client (2.3.1 revision 19531) + Server (2.3.1-r19533-1)
Win7 (VDI) -> Ubuntu 16.04 (virtual)
independent of Desktop Environment (simple terminator and lxde-desktop, too)
LAN (no limit)
e.g. C:\Program Files\Xpra\Xpra.exe" start --start-child=terminator ssh:user@fqdn:1000 --encoding=png −−pulseaudio=no −−speaker=no −−microphone=no --keyboard-layout=de
Same problem with 0.16 which i used before.
More users have the problem - others use it too rarely.

[Antoine Martin]

This sounds like it could be #1707, which would mean that this working as intended.
Are you talking about the taskbar or the systray?
It is meant to allow us to distinguish xpra forwarded windows from local ones. (ie: firefox local vs remote)

changes during use to the symbol of other applications (Outlook, Firefox, ...)

I doubt the icon shows the outlook icon unless you somehow managed to run outlook via xpra.

Same problem with 0.16 which i used before.

0.16 did not have this feature at all. So maybe this is / was a different problem?

Xpra 2.3.1 64 Bit Client (2.3.1 revision 19531)

Make sure you're running 2.3.2, which included a fix for this feature: r19719.

You can also disable it completely with XPRA_DYNAMIC_TRAY_ICON=0.

[michael]

taskbar!:

[Antoine Martin]

How odd! The icon in the taskbar should be the one from the window when there is only one window.
I have no idea how we could ever get the icon for outlook or from where!

Can you reproduce this with "-d tray,icon" added to the client command line?
Does the problem go away if you run with XPRA_DYNAMIC_TRAY_ICON=0?

[michael]

I have no idea how we could ever get the icon for outlook or from where!

Me, too :-)

Can you reproduce this with "-d tray,icon" added to the client command line?

Yes - Xpra.log appended.
Yesterday it changed to an empty icon. Today it changed to Notepad++ icon.

Does the problem go away if you run with XPRA_DYNAMIC_TRAY_ICON=0?

I will try today.

[Antoine Martin]

Well, the icon part looks OK but there are a number of errors in that log file, some of which give the wrong geometry for the monitors and therefore for the system tray too.
I guess that us using the wrong dimensions for the tray icon could somehow cause MS Windows to trip over itself?

• r19924 fixes the AssertionError in _focus_change - likely unrelated and harmless
• r19925 fixes the OverflowError: long int too long to convert in GetMonitorInfo (+r19929 fixup)
• r19928 improves the debug logging

Please try the latest 2.4 beta build to see if that resolves those issues (only known limitation of this build is the lack of webcam forwarding): https://xpra.org/beta/windows/.

[michael]

Beta 2.4 (2018-07-11) does not work here - screenshot attached.

Text:

xpra main error
Traceback (most recent call last):
  File "./xpra/scripts/main.py", line 75, in main
  File "./xpra/scripts/main.py", line 286, in run_mode
  File "./xpra/scripts/ma in.py", line 1605, in run_remote_server
TypeError: init() takes exactly 2 arguments (3 given)

[Antoine Martin]

Beta 2.4 (2018-07-11) does not work here - screenshot attached.

Try starting the server first from an SSH session, then connect to it with:

xpra_cmd attach ssh://user@host:SSHPORT/

(FYI: this is the recommended way of debugging things, the all-in-one remote start command can hide some details - esp wrt ssh)

[michael]

Excuse me for asking:

Until now i start my session during start and the debugging parameters are passed throug. If i split start and attach:
Must i activate the debug statements at start of the server process and/or at client attach?
Which logfile is relevant for you? Server (Linux) or client (Windows)?

[Antoine Martin]

Must i activate the debug statements at start of the server process and/or at client attach?

When in doubt, best to do both. Some will only be relevant to one end, which is fine.

Which logfile is relevant for you? Server (Linux) or client (Windows)?

By default remote-logging=yes so the server log should include the client log output.
But in this case, I strongly suspect that this a client-only problem (where would the server get an outlook icon?!), so the client log would be enough.

[michael]

Beta 2.4 (2018-07-11) with attach and -d tray,icon creates the problem (Word icon) - Xpra2.log attached.