Wayland on Arch Linux?

stozi · 2013-08-08 07:21:25

weston-launch gives me "failed to initialize egl"

I'm in the video group and using gma500_gfx. "lsmod | grep gma" outputs as it should according to the poulsbo wiki, with drm_kms_helper.

D4ve · 2013-08-13 23:55:28

Is someone here who got xwayland into a working state? No matter what i try, every application that requires the xserver fails to start.

Relevant things:
- I'm on a wayland only archlinux installation, so no X except xwayland
- xwayland-git from AUR is installed
- xf86-video-ati-xwayland-git from AUR is installed
- I'm in the weston-launch group (as proposed here)
- xwayland.so is successfully loaded: [01:27:57.905] Loading module '/usr/lib/weston/xwayland.so'
- a DISPLAY-variable is created: DISPLAY=:0

If i try to start an application that requires X, this happens (Even if i pass GDK_BACKEND=x11 as argument):

$ gnome-terminal
** (gnome-terminal:3355): WARNING **: Could not open X display 
Failed to parse arguments: Cannot open display:

I really don't know why it doesn't work. The xserver with wayland-support is included in xwayland-git, right?!

Last edited by D4ve (2013-08-15 01:44:10)

Cdh · 2013-08-14 08:48:22

Not sure if it's still the case but you can recompile weston with

--enable-xwayland --with-xserver-path=/opt/xwayland/bin/Xorg

(or wherever xwaland-git installs the x server)

Cdh · 2013-08-14 19:20:42

Does anyone know what's up with qtwayland? I tried to compile the dev git branch for extra/qt5-base 5.1.0-1

And with qmake-qt5 I get

Checking for wayland... yes
Checking for xkbcommon... yes
Checking for wayland_cursor... yes
Checking for wayland_scanner... yes
Checking for wayland_egl... no
Checking for egl... no
Checking for brcm_egl... no
Checking for glx... yes
Checking for xcomposite... yes
Project MESSAGE: no wayland-egl support detected, cross-toolkit compatibility disabled

With google I only found http://qt-project.org/forums/viewthread/30362

But there is wayland-egl:

$ pkg-config --modversion wayland-egl
9.3.0-devel

I thought qt 5.1 was supported?

Last edited by Cdh (2013-08-14 19:21:02)

D4ve · 2013-08-15 01:40:40

Cdh wrote:

Not sure if it's still the case but you can recompile weston [...]

Thanks, things look a little bit better now:

[03:22:50.649] Loading module '/usr/lib/weston/xwayland.so'
[03:22:50.658] xserver listening on display :0
[...]
[03:22:59.454] forked X server, pid 589
[03:22:59.719] xserver crashing too fast: 256

I think the last line is the best: crashing too fast - I mean, is it really expected that the xserver crashes? And if yes, how fast/slow should it crash? I'm confused...

EDIT: Damn, compiling weston with the two options changed nothing, just checked the old logfile, there's even the same error message in it. grrr...

EDIT: Made a new thread describing my problem. I don't think this really belongs in this thread. If anyone wants to join, click here

Last edited by D4ve (2013-08-15 14:05:31)

Cdh · 2013-09-01 13:48:42

Cdh wrote:

Checking for wayland_egl... no

Ok, so in qt 5.1 opengl es2 needs to be enabled.
In the qt5 pkbuild, add

-egl -opengl es2

to the configure parameters and rebuild.

Then in qtwayland qmake-qt5 shows "Checking for wayland_egl... yes"

The dev and the stable branch fail to compile with

/usr/lib/gcc/x86_64-unknown-linux-gnu/4.8.1/../../../../lib/libQt5PlatformSupport.a(qeventdispatcher_glib.o): In function `QPAEventDispatcherGlib::~QPAEventDispatcherGlib()':
(.text+0x83): undefined reference to `g_source_destroy'

I think it is trying to statically link against glib (and later fontconfig) and glib doesn't have static libraries on archlinux.

And the master branch just fails with some errors like wayland-output-extension-client-protocol.h missing or so.

stozi · 2013-09-18 16:35:43

I've bought a new computer and gotten weston running. I want to use qupzilla, so I installed it and hawaii-meta-git from the maui project. hawaii gives me a blank screen and a broken system after I crtl-alt-bkspc out. What surprises me is that in weston without hawaii qupzilla-qt5-git won't load as root or userx despite having qtwayland etc.

Fatal: QXcbConnection: Could not connect to display (qxcbconnection.cpp290, QXcbConnection::QXcbConnection
(QxcbNativeInterface*, bool, const char*))
Aborted (core dumped)

Scimmia · 2013-09-19 05:21:29

Anyone ever seen anything like this? I took a photo because the screenshot shows everything correctly, so it's obviously a display issue not a rendering issue. The bottom part of the screen is what shows up when I launch the terminal emulator by clicking in the upper left. Launching it within X works fine, too, this only happens when I try to launch weston alone.

And the log:

Date: 2013-09-18 CDT
[23:57:26.127] weston 1.2.90
               [url]http://wayland.freedesktop.org/[/url]
               Bug reports to: [url]https://bugs.freedesktop.org/enter_bug.cgi?product=Wayland&component=weston&version=1.2.90[/url]
               Build: 1.2.0-192-g4a4704a-dirty Minor improvement of weston-terminal resizing (2013-09-13 15:42:28 -0700)
[23:57:26.127] OS: Linux, 3.11.1-2-ck, #1 SMP PREEMPT Mon Sep 16 05:09:21 EDT 2013, x86_64
[23:57:26.127] Loading module '/usr/lib/weston/drm-backend.so'
[23:57:26.128] initializing drm backend
[23:57:26.128] using /dev/dri/card0
[23:57:26.243] Chosen EGL config details:
               RGBA bits: 8 8 8 0
               swap interval range: 0 - 0
[23:57:26.254] EGL version: 1.4 (DRI2)
[23:57:26.254] EGL vendor: Mesa Project
[23:57:26.254] EGL client APIs: OpenGL OpenGL_ES OpenGL_ES2 
[23:57:26.254] EGL extensions: EGL_MESA_drm_image EGL_WL_bind_wayland_display
               EGL_KHR_image_base EGL_KHR_gl_renderbuffer_image
               EGL_KHR_surfaceless_context EGL_KHR_create_context
               EGL_EXT_buffer_age
[23:57:26.254] GL version: OpenGL ES 2.0 Mesa 9.2.0
[23:57:26.254] GLSL version: OpenGL ES GLSL ES 1.0.16
[23:57:26.254] GL vendor: X.Org R300 Project
[23:57:26.254] GL renderer: Gallium 0.4 on ATI RV515
[23:57:26.254] GL extensions: GL_EXT_blend_minmax GL_EXT_multi_draw_arrays
               GL_EXT_texture_filter_anisotropic
               GL_EXT_texture_compression_dxt1 GL_EXT_texture_format_BGRA8888
               GL_OES_depth24 GL_OES_element_index_uint
               GL_OES_fbo_render_mipmap GL_OES_mapbuffer GL_OES_rgb8_rgba8
               GL_OES_standard_derivatives GL_OES_stencil8 GL_OES_texture_3D
               GL_OES_texture_npot GL_OES_EGL_image GL_OES_depth_texture
               GL_OES_packed_depth_stencil GL_EXT_texture_type_2_10_10_10_REV
               GL_OES_get_program_binary GL_APPLE_texture_max_level
               GL_EXT_discard_framebuffer GL_EXT_read_format_bgra
               GL_NV_fbo_color_attachments GL_OES_EGL_image_external
               GL_OES_vertex_array_object GL_ANGLE_texture_compression_dxt3
               GL_ANGLE_texture_compression_dxt5 GL_EXT_texture_rg
               GL_EXT_unpack_subimage GL_NV_draw_buffers GL_NV_read_buffer
               GL_EXT_map_buffer_range
[23:57:26.254] GL ES 2 renderer features:
               read-back format: BGRA
               wl_shm sub-image to texture: yes
               EGL Wayland extension: yes
[23:57:26.255] Initialized backlight, device /sys/class/backlight/acpi_video0
[23:57:26.255] EDID data 'SEC', '', ''
[23:57:26.256] Output LVDS1, (connector 16, crtc 10)
  mode 1680x1050@60.0, preferred, current
  mode 1400x1050@60.0
  mode 1280x1024@59.9
  mode 1440x900@59.9
  mode 1280x960@59.9
  mode 1280x854@59.9
  mode 1280x800@59.8
  mode 1280x720@59.9
  mode 1152x768@59.8
  mode 1024x768@59.9
  mode 800x600@59.9
  mode 848x480@59.7
  mode 720x480@59.7
  mode 640x480@59.4
[23:57:26.329] launching '/usr/lib/weston/weston-keyboard'
[23:57:26.340] input device Video Bus, /dev/input/event3 is a keyboard
[23:57:26.341] input device Power Button, /dev/input/event5 is a keyboard
[23:57:26.341] input device Sleep Button, /dev/input/event6 is a keyboard
[23:57:26.342] input device Broadcom Corp, /dev/input/event1 is a keyboard
[23:57:26.342] input device Broadcom Corp, /dev/input/event2 is a pointer caps = relative-motion button
[23:57:26.342] input device AT Translated Set 2 keyboard, /dev/input/event0 is a keyboard
[23:57:26.342] input device SynPS/2 Synaptics TouchPad, /dev/input/event11 is a touchpad
[23:57:26.342] input device SynPS/2 Synaptics TouchPad, /dev/input/event11 is a pointer caps = absolute-motion button
[23:57:26.342] input device SynPS/2 Synaptics TouchPad, /dev/input/event11 is a touch device
[23:57:26.343] input device Dell WMI hotkeys, /dev/input/event10 is a keyboard
[23:57:26.343] Loading module '/usr/lib/weston/desktop-shell.so'
[23:57:26.343] Loading module '/usr/lib/weston/xwayland.so'
[23:57:26.347] xserver listening on display :0
[23:57:26.347] Compositor capabilities:
               arbitrary surface rotation: yes
               screen capture uses y-flip: yes
[23:57:26.347] libwayland: using socket /run/user/1000/wayland-0
[23:57:26.350] launching '/usr/lib/weston/weston-desktop-shell'
proxy already has listener
proxy already has listener
[23:57:29.213] leaving VT
[23:57:38.328] caught signal 15
[23:57:38.328] libwayland: disconnect from client 0x21dad20
[23:57:38.328] libwayland: disconnect from client 0x21f99b0
[23:57:38.337] failed to drop master: Permission denied

haagch · 2013-09-24 16:22:21

In case people didn't see it: The current xwayland can run as normal X too. So there's no need to install xwayland somewhere else from your system X or decide between the two.

xwayland-git didn't install everything needed (xorg macros etc.) and xorg-server-xwayland didn't compile I think so I just modified xorg-server-git from AUR minimally, changed source to xserver::git+git://anongit.freedesktop.org/xorg/xserver#branch=xwayland and added --enable-wayland to the autogen parameters. It works fine with xf86-video-intel-xwayland-git (after removing the dependency on xwayland-git) both as xwayland in weston and as normal X.

But with qt5 I didn't have luck either. qtbase-git doesn't compile and with qt5 with -opengl es it fails linking. Does anyone have it working in any way?

D4ve · 2013-09-24 18:29:03

haagch wrote:

In case people didn't see it: The current xwayland can run as normal X too.

Could you explain that a little bit further? I don't really get it.

Or do you mean I can completely uninstall X and just go with xwayland without the need of a running wayland in the background?

haagch · 2013-09-24 19:52:24

I mean that you can uninstall the xorg-server from the repositories and install xwayland instead. And you can still use xwayland packages like the "normal" X without wayland.

Scimmia · 2013-09-24 23:31:57

I'm running that way now, although I modified the xorg-server package in [extra] instead of starting with the one in the AUR. They're very similar, so same effect.

D4ve, simply put, xwayland is xorg-server, just with some extra stuff in it. It runs exactly the same as xorg-server does, just with the added ability to run rootless under wayland.

D4ve · 2013-09-25 04:52:21

Ah, ok. Thanks for your answers, I always thought xwayland can't run standalone.

Scimmia · 2013-09-25 05:36:05

I was just watching some video from XDC (X.Org Developer Conference), it sounds like they want to get xwayland merged into master before 1.15, which is now scheduled to be released on Christmas. This means no more building from the AUR, xwayland will be there and ready to go on installations from the official repos.

reference: https://www.youtube.com/watch?v=jdd0zFQCU_I

I'm waiting for "Chris Halse Rogers - Nested Xservers, Mir & Wayland", which was earlier today be no video yet, and "Kristian Høgsberg, Daniel Stone - Wayland update" which is tomorrow.

blackout23 · 2013-10-01 14:50:02

Well but will xwayland support be enabled in the DDX drivers, too? The wayland website has instructions on how to compile xf86-video-nouveau with xwayland (isn't on the AUR) but I had no luck.

http://www.phoronix.com/scan.php?page=n … px=MTQ3MzQ

This would save the day maybe. Bascially it just replaces xf86-video-{intel,ati,nouveau} and has xwayland inside it.

Scimmia · 2013-10-01 16:24:58

I don't believe either the ati or nouveau DDXs work with the updated 1.14 xorg-server/xwayland. Not sure about intel.

The brand new xf86-video-wlglamor is working for me on an ATI card, though. I saw a discussion on IRC about this, it seems to be their answer instead of adding support in each DDX. Haven't figured out a good way to switch back and forth, but haven't spent much time on it.

Last edited by Scimmia (2013-10-02 03:50:41)

Scimmia · 2013-10-17 06:52:49

Since the last thing I said was that I haven't figured out a good way to switch back and forth, I thought I would update this.

xwayland has been updated to use wlglamor as a fallback now, so no more xorg.conf.d file needed. If it doesn't find another DDX that will work, it will try to use wlglamor automatically if it finds it.

onny · 2013-10-18 14:16:29

I further added some notes on keyboard shortcuts, configuration files, Xwayland and Gnome3 support into the Wayland wiki page

Scimmia · 2013-11-01 16:17:34

Scimmia wrote:

I was just watching some video from XDC (X.Org Developer Conference), it sounds like they want to get xwayland merged into master before 1.15, which is now scheduled to be released on Christmas. This means no more building from the AUR, xwayland will be there and ready to go on installations from the official repos.
reference: https://www.youtube.com/watch?v=jdd0zFQCU_I

Quoting myself to update, 1.15 merge window is now closed and xwayland is not there. I guess we'll hope for 1.16.

onny · 2013-11-01 17:34:38

Thank you Scimmia for the info!

HalosGhost · 2013-11-01 20:23:56

Scimmia wrote:

Quoting myself to update, 1.15 merge window is now closed and xwayland is not there. I guess we'll hope for 1.16.

Bummer. I would really like to see XWayland get some ᴛʟᴄ.

All the best,

-HG

TheCycoONE · 2013-12-17 17:47:28

@Scimmia: I have the same problem, but I'm using pretty similar hardware (an X1400)

Could be a problem with the r300 drivers?

Scimmia · 2013-12-17 17:58:36

I've found that it only happens with hardware rendering/EGL, so I think it is a driver issue. Enlightenment has support for wayland clients within their X compositor, so I'm testing from there. weston-simple-egl gives me the same problem, weston-simple-shm runs fine. I haven't looked into getting weston running on software only.

Scimmia · 2013-12-27 17:00:59

TheCycoONE, I went ahead and filed a bug report against wayland/weston. I'm on an X1400 as well, so if they just say it's the driver and not their problem, I'll file one against mesa.

https://bugs.freedesktop.org/show_bug.cgi?id=73076

ammen99 · 2014-01-03 09:38:52

Hi
I'm having problems with mouse.
I can start weston-launch and it loads, mouse is moving but i cannot click.What should i do?

Arch Linux

#226 2013-08-08 07:21:25

Re: Wayland on Arch Linux?

#227 2013-08-13 23:55:28

Re: Wayland on Arch Linux?

#228 2013-08-14 08:48:22

Re: Wayland on Arch Linux?

#229 2013-08-14 19:20:42

Re: Wayland on Arch Linux?

#230 2013-08-15 01:40:40

Re: Wayland on Arch Linux?

#231 2013-09-01 13:48:42

Re: Wayland on Arch Linux?

#232 2013-09-18 16:35:43

Re: Wayland on Arch Linux?

#233 2013-09-19 05:21:29

Re: Wayland on Arch Linux?

#234 2013-09-24 16:22:21

Re: Wayland on Arch Linux?

#235 2013-09-24 18:29:03

Re: Wayland on Arch Linux?

#236 2013-09-24 19:52:24

Re: Wayland on Arch Linux?

#237 2013-09-24 23:31:57

Re: Wayland on Arch Linux?

#238 2013-09-25 04:52:21

Re: Wayland on Arch Linux?

#239 2013-09-25 05:36:05

Re: Wayland on Arch Linux?

#240 2013-10-01 14:50:02

Re: Wayland on Arch Linux?

#241 2013-10-01 16:24:58

Re: Wayland on Arch Linux?

#242 2013-10-17 06:52:49

Re: Wayland on Arch Linux?

#243 2013-10-18 14:16:29

Re: Wayland on Arch Linux?

#244 2013-11-01 16:17:34

Re: Wayland on Arch Linux?

#245 2013-11-01 17:34:38

Re: Wayland on Arch Linux?

#246 2013-11-01 20:23:56

Re: Wayland on Arch Linux?

#247 2013-12-17 17:47:28

Re: Wayland on Arch Linux?

#248 2013-12-17 17:58:36

Re: Wayland on Arch Linux?

#249 2013-12-27 17:00:59

Re: Wayland on Arch Linux?

#250 2014-01-03 09:38:52

Re: Wayland on Arch Linux?

Board footer