-
Notifications
You must be signed in to change notification settings - Fork 379
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
Failed in starting with --weston-xwayland
#19
Comments
It is a bit strange as weston does not show an obvious error message. It just stops during startup. On my debian system, it starts up well in Gnome-Wayland. Does weston start if you run it alone in a terminal? Looking closer, I see weston tries to load extension I did a change to x11docker to use Xwayland backend instead of Wayland to create its window if it runs on Ubuntu. Please try out if this solves the problem: https://raw.githubusercontent.com/mviereck/x11docker/experimental/x11docker |
Thanks @mviereck! Applying the patch as specified above (v3.8.1) does allow calling
If run as current user:
...and quit without getting a weston window. If run as root:
...and a weston window will appear.
Indeed. On a potentially unrelated note, if I run
...and the
While it seems to work for now, feel free if you need any more test here as well - my dev box is an Ubuntu 17.10 (artful), upgraded from a fresh installation of 17.04 (zesty). Thanks again! |
Fine that it works now and the solution was that easy. :-) Thanks for reporting, I would not have found that issue myself. The bugfix is quite small, weston now runs as an X client instead of running as Wayland client on Ubuntu. Though, I prefer it to run as Wayland client as that adds another layer of security. Hopefully the bug will be gone in Ubuntu 18.04. Strange that weston does not crash if running as root. As user, it will most probably run on your ystem with
Thanks! Currently I don't know anything special to test. Just try out x11docker options and report if something seems to be fishy. A new option that may fail in Ubuntu is I already found that Ubuntu images do not work well with |
I have uploaded the patch / V3.8.1 yet. |
Thanks! I tried the final v3.8.1 release and ran it with There is one more thing that bothers me but may not be entirely related to this issue at all - my apologies if I should file a new issue or we should dismiss it as expected behavior. When running x11docker with Mate or Cinnamon, with flags Thanks again. Admittedly I know too little regarding the X/Wayland/compositors under the hood than I should. Would like to have your pointers here, if possible. |
It is better to open new issues ;-).
I am currently working on a major update that will set up dbus, consolekit and /tmp/.ICE-unix properly. Most probably this error message is related. Though, I do not get exactly the message you describe. Would you mind to open a new issue and show me the exact command you have used? Also it helps to store x11docker.log at https://pastebin.com/ . You find the logfile after terminating the x11docker session in
I am not sure if I understand correctly. Xwayland appears as a borderless window in wayland; mate and cinnamon should start properly in Xwayland. The Xwayland window itself can be moved around with META+LeftMouseButton. Please open a new issue for this if you experience a different behaviour. |
OK, thanks :) Will try to provide better description for each of them after gathering more information first then. Thanks again! |
# 15.12.2017 V3.9.0 /etc/shadow: disable possible root password # --dbusdaemon: new option to run dbus system daemon and consolekit in container # 14.12.2017 re-checked capabilities for init systems # --systemd: set environment globally, especially DISPLAY for deepin is needed # --systemd: set xhost+SI:localuser:$Benutzer as XAUTHORITY seems to be ignored # 12.12.2017 /tmp/.ICE-unix created in dockerrc, root owned with 1777, needed for SESSION_MANAGER # --rw: deprecated, root file system is always r/w now due to 'docker exec' in dockerrc # 10.12.2017 (V3.8.1) bugfix Ubuntu: avoid Wayland backend for Weston due to MIR issue #19 # (V3.8.1) --xorg: change Xorg to X. X is setuid wrapper for Xorg on Ubuntu 14.04 # (V3.8.1) +iglx removed from X options, not present in older versions of X, and maybe security issue. # 09.12.2017 create user in dockerrc with 'docker exec' instead of using createuser.sh # --xorg: removed +iglx from options, not supported on older X versions # 07.12.2017 --openrc: new option for init system OpenRC in container # --sharecgroup: new option to share /sys/fs/cgroup. default for --systemd. # 06.12.2017 create /var/lib/dbus in dockerrc to avoid dbus errors with init systems # show image name and display in weston windows # bugfix --runit: add SYS_BOOT even with --cap-default
Hi,
Thanks for the x11docker project! On my Ubuntu 17.10 box that is running on Wayland session, I have got errors with the flag
--weston-xwayland
.--xephyr
seems to run fine.Have run with
--verbose
and got the following as the resulting log. Do you have any ideas/pointers on what could be the culprit? Thanks.The text was updated successfully, but these errors were encountered: