Hello,
since i've updated my workstation and the remote worstation to fedora 31 with the newest xpra version (both - xpra v4.0.1-r26379) im getting a "running on linux unknown unknown unknown" in the xpra startup log.
2020-06-04 11:54:38,879 Authentication (publickey) successful! 2020-06-04 11:54:39,205 keyboard settings: rules=evdev, model=pc105, layout=de 2020-06-04 11:54:39,208 desktop size is 5360x1440 with 1 screen: 2020-06-04 11:54:39,209 :0.0 (1418x381 mm - DPI: 96x96) workarea: 5360x1053 at 0x387 2020-06-04 11:54:39,209 AUO eDP-1 1920x1080 at 0x360 (293x165 mm - DPI: 166x166) 2020-06-04 11:54:39,209 ACR DP-1 3440x1440 at 1920x0 (795x334 mm - DPI: 109x109) 2020-06-04 11:54:42,251 enabled remote logging 2020-06-04 11:54:42,252 Xpra GTK3 X11 server version 4.0.1-r26379 64-bit 2020-06-04 11:54:42,253 running on Linux unknown unknown unknown 2020-06-04 11:54:42,376 server does not support xi input devices 2020-06-04 11:54:42,376 server uses: xtest
Im also not able to start any child processes. For instance: Im starting a tool, which starts evince, libreoffice... by pressing a button. That worked with the last version, but not with this one. Maybe the "unknown unknwn unknown" problem is connected with this?
Ask if you need any further information.
Thanks in advance
running on Linux unknown unknown unknown
That's odd, I'm not seeing this here on F31 or F32 with the official packages. How did you install xpra?
Im starting a tool, which starts evince, libreoffice... by pressing a button
What tool can I use to reproduce the problem.
Is the tool started with --start=
?
Does it work if you do the same thing from an xterm
running through xpra? (it does for me)
Perhaps you're not using --start
and therefore not using the correct environment.
In that case, the application may start but somewhere else.. like maybe on a wayland display.
xpra was installed through dnf install...
[
root@ws ~]# dnf list installed | grep xpra ffmpeg-xpra.x86_64 4.2.2-2.fc31 python3-xpra.x86_64 4.0.1-10.r26379.fc31 python3-xpra-audio.x86_64 4.0.1-10.r26379.fc31 python3-xpra-client.x86_64 4.0.1-10.r26379.fc31 python3-xpra-server.x86_64 4.0.1-10.r26379.fc31 x264-xpra.x86_64 20190929-1.fc31 xorg-x11-drv-dummy.x86_64 0.3.8-1.xpra2.fc31 xpra.x86_64 4.0.1-10.r26379.fc31 xpra-common.noarch 4.0.1-10.r26379.fc31 xpra-common-client.noarch 4.0.1-10.r26379.fc31 xpra-common-server.noarch 4.0.1-10.r26379.fc31 xpra-html5.noarch 4.0.1-10.r26379.fc31
Our tool is a selfmade crm tool. Its complicated so i do not have any other tools which works the same. Im starting xpra this way (so im always starting with xterm):
setsid xpra start ssh:ws:231 --bell=no --border=blue,3 --cursor=no --pulseaudio=no --speaker=disabled --microphone=disabled --quality=0 --system-tray=no --printing=no --file-transfer=no --mdns=no --html=off --dbus-proxy=no --no-notifications --notification=no --video-encoders=x264,vpx '--env=PATH=$PATH:/share/bin' --start-child=xterm -e $TOOL '--title=@title@ at @client-machine@' --exit-with-children
--file-transfer=on
By setting this im able to get a popup where i want this file to open. When i select "open on server" i can see the file. But this is new and i dont want this popup...
It seems like this switch is toggleing this "linux unknown unknown unknown" too. Maybe the "off, no" Option of this switch is broken?
Our tool is a selfmade crm tool
Then maybe it's stripping something from the environment that xpra provided.
Try running evince
from an xterm started with --start=xterm
: evince
should start and show up in the xpra session.
But if you do DISPLAY=:VALUE xterm
to start your xterm instead (with VALUE
set to your xpra display) and then try to run evince
from that xterm, it doesn't show up in the session, it shows up my wayland desktop..
So, basically, that part is not an xpra bug for sure. They must have changed the default in Fedora 31 to use wayland instead of x11.
The "unknown" values problem, I will try to replicate later (but this is much less critical).
By setting this im able to get a popup where i want this file to open. When i select "open on server" i can see the file. But this is new and i dont want this popup...
See #1726 and the forward-xdg-open
option.
It seems like this switch is toggleing this "linux unknown unknown unknown" too.
I will check this.
yes, wayland is now the default. forward-xdg-open
fixes my problem. Thanks!
It seems like this switch is toggleing this "linux unknown unknown unknown" too. Maybe the "off, no" Option of this switch is broken?
Can you please clarify which exact command lines will allow me to reproduce this problem?
I've tried combinations of --file-transfer=yes
and --file-transfer=no
on both client and server, to no avail.
Can you please clarify which exact command lines will allow me to reproduce this problem?
Bump!
setsid xpra start ssh:ws:231 --bell=no --border=blue,3 --cursor=no --pulseaudio=no --speaker=disabled --microphone=disabled --quality=0 --system-tray=no --printing=no --file-transfer=no --mdns=no --file-transfer=on --html=off --dbus-proxy=no --no-notifications --notification=no --video-encoders=x264,vpx '--env=PATH=$PATH:/share/bin' --start-child=xterm -e gedit '--title=@title@ at @client-machine@' --exit-with-children
Thanks for the command line.
.. -file-transfer=no --mdns=no --file-transfer=on
You are setting it to no
, and then to on
. (the latter will override the former)
For good measure, I have tested with both values.
.. --no-notifications --notification=no
You can delete one of these two, they do exactly the same thing. (the second form is the preferred form)
I have run your exact command line, only changing the host, and the problem does not occur here.
So I am closing as needinfo
, there must be something else causing this problem on your system.
Perhaps something from this list wiki/ReportingBugs?
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/2797