xpra icon
Bug tracker and wiki

This bug tracker and wiki are being discontinued
please use https://github.com/Xpra-org/xpra instead.

Custom Query (2683 matches)


Show under each result:

Results (46 - 48 of 2683)

Ticket Resolution Summary Owner Reporter
#2926 fixed fedora 33 rpm dependencies problems Antoine Martin Antoine Martin

Somehow Fedora 33 does not see that x264-xpra and ffmpeg-xpra provide the libraries it thinks are missing... which means that the python3-xpra package can't be installed.

#2925 fixed lack of XDG_RUNTIME_DIR causes problems Antoine Martin Antoine Martin

Switching to another user account via su - otheruser may not create XDG_RUNTIME_DIR. On some distros, logging in via ssh does not create it either.

Then when we try to create the sockets, /run/user/$UID does not exist and we end up not creating any local sockets... then xpra list shows nothing, and connecting via ssh also fails to locate the server.

#2924 fixed ssh suddenly ignored in config file? Lukas Haase Lukas Haase

I have *.xpra config files for my Windows system. Some of them contain ssh= lines that always used to work (they prevent querying my agent and supply dedicated key files directly).

Recently I upgraded to 4.0.3 and it seems this option is ignored now.

Example in config:

ssh=c:\\Program Files\\Xpra\\plink.exe -noagent -T -i o:\\key.ppk

This will query the agent and then ask me for a password (I think via pamiko frontend). Also if I add random things like -DoesNotExist ... the pamiko thing will be used.

However, starting from command line works:

"c:\Program Files\Xpra\Xpra_cmd.exe" attach --ssh="c:\\Program Files\\Xpra\\plink.exe -noagent -T -i o:\\key.ppk" --username=lukas ssh://lukas@


Note: See TracQuery for help on using queries.