New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Invalid argument for -config when using --xpra or --xorg #9
Comments
Thanks for your feedback!
Does xpra work on its own?
And xpra started this way?
I'm not sure how to solve this, as I want to avoid creating files in |
Option |
My current OS is Ubuntu 16.04, which seems to be the problem. 16.04 handles Xorg in a very strange and roundabout way, which forces all Xorg instances to be setuid. This in-turn precludes the use of either --config or --logfile. |
https://xpra.org/trac/ticket/1220 is the upstream issue. |
# 25.04.2017 V3.1.7 --xpra and --xdummy now use Xvfb if installed. Compare #9, Xdummy cannot be used on Ubuntu 16.04 due to xorg.conf location # set $Windowmanager in auto choosing X server if switching to desktop windows
Thanks! For use of option |
Unfortunately xvfb still triggers the -config issue in 16.04. Seems |
Do you use the latest version of x11docker? Xvfb is independent from Xorg and is called without any -config option. Can you check your x11docker version ( |
Command run: x11docker --xpra --sudo --verbose -- ' ' firefox /usr/bin/firefox
Docker file: firefox.txt
x11docker log file: x11docker.txt
I've tried multiple config options, but if I use --xpra or --xorg, I get this error. Seems Xorg is not happy with -config being an absolute location.
The text was updated successfully, but these errors were encountered: