search

mviereck / dockerfile-x11docker-xwayland

Xwayland X server in docker image
MIT License
14 stars 1 forks source link

Example fails with segmentation fault #1

Closed D4Delta closed 5 years ago

D4Delta commented 5 years ago

When I run x11docker --wayland --gpu x11docker/xwayland (one of the example in README) It fails with the following output:

x11docker note: Using X server option --hostwayland

x11docker WARNING: Command 'xauth' not found.
  Please install 'xauth' to allow X cookie authentication.
  Securing X access with cookie authentication is not possible.
  Fallback: Disabling X authentication protocol. (option --no-auth)
  You can look for the package name of this command at: 
 https://github.com/mviereck/x11docker/wiki/dependencies#table-of-all-packages

x11docker WARNING: Option --gpu degrades container isolation.
  Container gains access to GPU hardware.
  This allows reading host window content (palinopsia leak)
  and GPU rootkits (compare proof of concept: jellyfish).

x11docker note: You are running a pure Wayland environment.
  X applications without Wayland support will fail.

x11docker WARNING: Option --no-auth: SECURITY RISK!
  Allowing access to new X server for everyone.

x11docker WARNING: Sharing device file: /dev/dri

x11docker WARNING: Sharing device file: /dev/vga_arbiter

x11docker x11docker/xwayland :
Please type in your password to run docker on display 
Password (su): Mot de passe : 
xauth:  file /fakehome/delta/.Xauthority does not exist

glamor: EGL version 1.4 (DRI2):
(EE) 
(EE) Backtrace:
(EE) 0: /usr/bin/Xwayland (xorg_backtrace+0x4a) [0x561f0b485d7a]
(EE) 1: /usr/bin/Xwayland (0x561f0b2e0000+0x1a9b09) [0x561f0b489b09]
(EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fe33d7fc000+0x110e0) [0x7fe33d80d0e0]
(EE) 3: /usr/lib/x86_64-linux-gnu/libwayland-client.so.0 (wl_proxy_marshal_constructor+0x96) [0x7fe33f7fb236]
(EE) 4: /usr/bin/Xwayland (0x561f0b2e0000+0x3b60c) [0x561f0b31b60c]
(EE) 5: /usr/bin/Xwayland (0x561f0b2e0000+0x15b306) [0x561f0b43b306]
(EE) 6: /usr/bin/Xwayland (MapWindow+0x1f9) [0x561f0b47f389]
(EE) 7: /usr/bin/Xwayland (0x561f0b2e0000+0x1730e1) [0x561f0b4530e1]
(EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf1) [0x7fe33d47d2e1]
(EE) 9: /usr/bin/Xwayland (_start+0x2a) [0x561f0b31a5ca]
(EE) 
(EE) Segmentation fault at address 0x0
(EE) 
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
(EE)

I'm running sway 1.1.1-3, without xwayland.

(Thank you for x11docker btw, I'm writing this issue on a pure wayland dockerized firefox, it works flawlessly)

mviereck commented 5 years ago

Thank you for reporting this!

I wonder if that might be related to Sway. AFAIK it uses a customized version of Xwayland. Maybe the communication between Sway and the "official" Xwayland is disturbed somehow.

Do you have weston installed on your system, too? Please try:

x11docker --wayland --weston --gpu x11docker/xwayland

Another attempt: The image x11docker/xwayland has been based on Debian 9/stretch. I have updated it to Debian 10/buster yet. Pull a fresh image with docker pull x11docker/xwayland and try again. Maybe this more recent version of Xwayland works.

Another check: Try to run Xwayland :10 directly on Sway.

D4Delta commented 5 years ago

Xwayland :10 fails with the same segmentation fault, so it's not a bug related to x11docker-xwayland, closing this (sorry about that, I should have tried Xwayland without docker first).

mviereck commented 5 years ago

No problem! Good to know this. Maybe you want to open a ticket at https://github.com/swaywm? It would be of interest for me, too.

The check with x11docker --wayland --weston --gpu x11docker/xwayland would be of interest, too.

mviereck commented 5 years ago

I have opened a ticket at sway: https://github.com/swaywm/sway/issues/4327