xf86-video-dummy".
LD_SO_PRELOAD tricks to
fool the X11 server process) and therefore not suitable for deployment in many environments.
RandR extension. For many display bugs (ie: #1, #2)
this is the only workable solution: it allows Xpra to resize the virtual display to match the client's resolution so as to prevent windows and
menus from overflowing beyond the edge of the screen.
suid Xorg binary,
Xpra should have installed the xpra_Xdummy wrapper script and configured xpra.conf to use it instead
of the regular Xorg binary.
Xorg binary to a non-suid executable before running it.
Xorg executable world-readable so that the wrapper can make the non-suid copy when needed:
sudo chmod +r /usr/bin/Xorg
Xorg -noreset +extension GLX +extension RANDR +extension RENDER -logfile ./10.log -config ./xorg.conf :10
(It contains many of the most common resolutions you are likely to need,
including those found on phones and tablets.
However if your client uses unusual resolutions, for instance multiple screens of differing sizes,
you may need to add new Modelines
to match your specific resolution)
--xvfb switch:
xpra --xvfb="Xorg -dpi 96 -noreset -nolisten tcp \
+extension GLX +extension RANDR +extension RENDER \
-logfile ${HOME}/.xpra/Xvfb-10.log -config ${HOME}/xorg.conf" \
start :10xvfb option in your /etc/xpra/xpra.conf:
xvfb=Xorg -dpi 96 -noreset -nolisten tcp \
+extension GLX +extension RANDR +extension RENDER \
-logfile ${HOME}/.xpra/Xvfb-10.log -config ${HOME}/xorg.conf(the -noreset option is only needed if the window manager is not
the first application started on the display, for example if you use the --start-child= option,
or if you want the display to survive once the window manager exits
- generally, this is a good idea since xpra could crash and when it exits cleanly via "xpra stop" it takes care
of shutting down the X11 server anyway)