Custom Query (2683 matches)
Results (31 - 33 of 2683)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#351 | fixed | --use-display seems to be broken | ||
Description |
Using --use-display produces the following error message: Traceback (most recent call last): File "./scripts/xpra", line 6, in <module> sys.exit(xpra.scripts.main.main(__file__, sys.argv)) File "/mnt/data/src/xpra/src/build/lib.linux-x86_64-2.7/xpra/scripts/main.py", line 433, in main return run_server(parser, options, mode, script_file, args) File "/mnt/data/src/xpra/src/build/lib.linux-x86_64-2.7/xpra/scripts/server.py", line 459, in run_server xvfb_pid = get_pid() File "/mnt/data/src/xpra/src/build/lib.linux-x86_64-2.7/xpra/scripts/server.py", line 96, in get_pid from xpra.x11.gtk_x11.prop import prop_get File "/mnt/data/src/xpra/src/build/lib.linux-x86_64-2.7/xpra/x11/gtk_x11/prop.py", line 27, in <module> X11Window = X11WindowBindings() File "core_bindings.pyx", line 60, in xpra.x11.bindings.core_bindings.X11CoreBindings.__cinit__ (xpra/x11/bindings/core_bindings.c:791) AssertionError: display is not set! |
|||
#1859 | fixed | --use-display: XAUTHORITY is not honoured | ||
Description |
System: debian 9, winswitch repository Since xpra v2.3-r19246 xpra does not use/regard XAUTHORITY to access a display with --use-display if the specified display uses cookie authentication. It fails with 'no protocol specified'. Code to reproduce: /usr/bin/Xvfb :40 -screen 0 1920x1080x24 \ -nolisten tcp -dpms -s off -retro \ +extension Composite +extension RANDR +extension RENDER +extension GLX\ +extension XTEST \ -auth /tmp/cookie \ & sleep 2 xauth -f /tmp/cookie add :40 . $(mcookie) # env DISPLAY=:40 XAUTHORITY=/tmp/cookie xterm #no error message env DISPLAY=:40 XAUTHORITY=/tmp/cookie xpra start :40 --use-display --start-via-proxy=no --daemon=no |
|||
#908 | wontfix | --with-Xdummy --with-Xdummy_wrapper options not honored across invocations of setup.py | ||
Description |
It used to be the case that you could specify
Currently, unless
Logically, I expect xpra.conf to be created during build, and whatever is present during install is just installed if we're using |