Closed sxiii closed 4 years ago
It seems that this error has something to do with my DISPLAY=""
variable. When I set it up like export DISPLAY=""
then it works. When I do export $Xenv
after running a session it's getting filled with data from docker, and later I can't start it until I make DISPLAY empty again.
I am not sure what is going on. Can you please provide me ~/.cache/x11docker/x11docker.log
or the --verbose
output?
Here's the file: error.log
Doing export DISPLAY=""
helps to get rid of this problem. But if the DISPLAY has something in it; then there's error of not being able to access the XServer, even tho it's not launched.
Maybe I already found the issue in your command:
'/usr/bin/x11docker' '--verbose' '--name=ff' '--gpu' '--xorg' '--size=1920x1080' '--display' '11' '--showenv' '--hostipc' '--hostdisplay' '--user=RETAIN' '--wm=x11docker/fvwm' '-m' '--' 'ff'
You specify --xorg --hostdisplay
. Those are two different X server options, the second one (--hostdisplay
) takes effect.
If you previously ran export $Xenv
there will be some confusion.
--xorg
runs a new X server.
--hostdisplay
uses an already running X server, e.g. one with a regular desktop environment.
Try either with --xorg
(or --xorg --wm
) only,
or provide a regular X enviroment that already provides a window manager to use --hostdisplay
(without --wm
).
Aha. Now I got the idea. Second one is more important; --xorg -> for new X; --hostdisplay for "reusing existing". That wasn't clear! I am trying to get rid of the flags I don't really need. So thanks!
Does --wm
now work as expected, or are still issues left?
@mviereck yeah I managed to pick the right sets of flags. I think WM works as expected so closing the issue :) Thanks.
Latest issue (maybe bug!) I found with using both
--wm=openbox
andwm=x11docker/openbox
:I was already running openbox earlier. The only thing is that I've changed Dockerfile a little bit. Here you can see that I have the image: