Opened 2 years ago
Last modified 16 months ago
#2797 closed defect
running on linux unknown — at Version 1
Reported by: | nsauter | Owned by: | nsauter |
---|---|---|---|
Priority: | major | Milestone: | 4.1 |
Component: | client | Version: | 4.0.x |
Keywords: | Cc: |
Description (last modified by )
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
Change History (1)
comment:1 Changed 2 years ago by
Description: | modified (diff) |
---|---|
Owner: | changed from Antoine Martin to nsauter |
Note: See
TracTickets for help on using
tickets.
That's odd, I'm not seeing this here on F31 or F32 with the official packages.
How did you install xpra?
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.