Wayland on Arch Linux?

89c51 · 2014-01-16 12:46:31

Since Enlightenment 19 hit git it is possible -in theory at least- to run it on pure wayland. Has anyone managed to get it to run this way? Is there anything special needed in mesa or any other lib??

I removed X dependencies from Scimmias PKGBUILDs but could someone check them for possible mistakes?? I am pretty sure i missed stuff.

elementary-git
http://pastebin.com/4pyFUa2u

enlightenment-git
http://pastebin.com/V4Q5HpAF

efl-git
http://pastebin.com/QHGE9Sf8

stozi · 2014-01-30 17:17:18

so midori-gtk3 works out of the box. But I'm surprised Qt5-wayland is taking so long to hit repositories, or even be buildable from AUR. What does it mean that it's in branch stable? this is the closest thing I've come to being able to follow its progress - https://qt.gitorious.org/qt/qtwayland/s … 95490627:#
Though I'm not sure there's much to interpret from that

Nektarios · 2014-02-22 08:15:48

I am trying to start weston with my second monitor at 120hz instead of 60hz at it's default resolution of 1680x1050. I used the output section in my ~/.config/weston.ini file, setting the appropriate modeline but it doesn't work. here is the relevant part of the ini:

[output]
name=DVI2
mode=1680x1050@120.0
modeline=313.75  1680 1816 2000 2320  1050 1053 1059 1128 -hsync +vsync

[output]
name=DVI1
#mode=1280x800

Notice that I tried several mode and none of them work:
mode=1680x1050
mode=1680x1050@120
mode=1680x1050@120.0

And here's the weston-launch log:

Date: 2014-02-22 EET
[09:50:23.740] weston 1.4.0
               http://wayland.freedesktop.org/
               Bug reports to: https://bugs.freedesktop.org/enter_bug.cgi?product=Wayland&component=weston&version=1.4.0
               Build: 1.4.0-45-g49fcd00 build: Pass pkg-config CFLAGS as target_CFLAGS, not CPPFLAGS (2014-02-03 11:21:41 -0800)
[09:50:23.740] OS: Linux, 3.12.9-2-ARCH, #1 SMP PREEMPT Fri Jan 31 10:22:54 CET 2014, x86_64
[09:50:23.740] Using config file '/home/nektarios/.config/weston.ini'
[09:50:23.740] Loading module '/usr/lib/weston/drm-backend.so'
[09:50:23.741] initializing drm backend
[09:50:23.742] using /dev/dri/card0
[09:50:23.742] Loading module '/usr/lib/weston/gl-renderer.so'
[09:50:23.801] Chosen EGL config details:
               RGBA bits: 8 8 8 0
               swap interval range: 0 - 0
[09:50:23.802] EGL version: 1.4 (DRI2)
[09:50:23.803] EGL vendor: Mesa Project
[09:50:23.803] EGL client APIs: OpenGL OpenGL_ES OpenGL_ES2 OpenGL_ES3 
[09:50:23.803] 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
[09:50:23.803] GL version: OpenGL ES 3.0 Mesa 10.0.2 (git-b6ccc2b)
[09:50:23.803] GLSL version: OpenGL ES GLSL ES 3.0
[09:50:23.803] GL vendor: X.Org
[09:50:23.803] GL renderer: Gallium 0.4 on AMD CYPRESS
[09:50:23.803] 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 GL_OES_depth_texture_cube_map
               GL_OES_surfaceless_context GL_EXT_color_buffer_float
[09:50:23.803] GL ES 2 renderer features:
               read-back format: BGRA
               wl_shm sub-image to texture: yes
               EGL Wayland extension: yes
[09:50:23.803] Failed to initialize backlight
[09:50:23.803] EDID data 'SAM', 'SyncMaster', 'H1AK500000'
[09:50:23.803] Output DVI1, (connector 22, crtc 11)
               mode 2560x1600@59.9, current
               mode 1280x800@59.9
[09:50:23.861] Failed to initialize backlight
[09:50:23.861] EDID data 'SAM', 'SyncMaster', 'HVMZ501956'
[09:50:23.861] Output DVI2, (connector 25, crtc 12)
               mode 1680x1050@59.9, preferred, current
               mode 1680x1050@120.0
               mode 1680x1050@110.0
               mode 1680x1050@100.0
[09:50:23.861] launching '/usr/libexec/weston-keyboard'
[09:50:23.861] compositor: executing '/usr/libexec/weston-keyboard' failed: No such file or directory
[09:50:23.865] input device Power Button, /dev/input/event5 is a keyboard
[09:50:23.865] input device Power Button, /dev/input/event4 is a keyboard
[09:50:23.865] not using input device '/dev/input/event16'.
[09:50:23.866] not using input device '/dev/input/event7'.
[09:50:23.866] not using input device '/dev/input/event15'.
[09:50:23.866] not using input device '/dev/input/event14'.
[09:50:23.866] not using input device '/dev/input/event13'.
[09:50:23.866] not using input device '/dev/input/event12'.
[09:50:23.866] not using input device '/dev/input/event11'.
[09:50:23.866] not using input device '/dev/input/event10'.
[09:50:23.866] not using input device '/dev/input/event9'.
[09:50:23.866] not using input device '/dev/input/event8'.
[09:50:23.866] input device USB Keyboard, /dev/input/event0 is a keyboard
[09:50:23.867] input device USB Keyboard, /dev/input/event1 is a keyboard
[09:50:23.867] input device Microsoft Microsoft 5-Button Mouse with IntelliEye(TM), /dev/input/event2 is a pointer caps = relative-motion button
[09:50:23.867] input device Razer Razer DeathAdder, /dev/input/event3 is a pointer caps = relative-motion button
[09:50:23.867] not using input device '/dev/input/event6'.
[09:50:23.867] Loading module '/usr/lib/weston/desktop-shell.so'
[09:50:23.867] Module '/usr/lib/weston/desktop-shell.so' already loaded
[09:50:23.867] Loading module '/usr/lib/weston/xwayland.so'
[09:50:23.869] xserver listening on display :2
[09:50:23.869] Compositor capabilities:
               arbitrary surface rotation: yes
               screen capture uses y-flip: yes
[09:50:23.869] libwayland: using socket /run/user/1002/wayland-0
[09:50:23.874] launching '/usr/lib/weston/weston-desktop-shell'
[09:50:23.874] libwayland: disconnect from client 0x9bb780
[09:50:23.874] input_method died, respawning...
[09:50:23.874] launching '/usr/libexec/weston-keyboard'
[09:50:23.874] compositor: executing '/usr/libexec/weston-keyboard' failed: No such file or directory
[09:50:23.875] libwayland: disconnect from client 0x9bb780
[09:50:23.875] input_method died, respawning...
[09:50:23.875] launching '/usr/libexec/weston-keyboard'
[09:50:23.875] compositor: executing '/usr/libexec/weston-keyboard' failed: No such file or directory
[09:50:23.876] libwayland: disconnect from client 0x9bb780
[09:50:23.876] input_method died, respawning...
[09:50:23.876] launching '/usr/libexec/weston-keyboard'
[09:50:23.876] compositor: executing '/usr/libexec/weston-keyboard' failed: No such file or directory
[09:50:23.877] libwayland: disconnect from client 0x9aea40
[09:50:23.877] input_method died, respawning...
[09:50:23.877] launching '/usr/libexec/weston-keyboard'
[09:50:23.877] compositor: executing '/usr/libexec/weston-keyboard' failed: No such file or directory
[09:50:23.877] libwayland: disconnect from client 0x9aea40
[09:50:23.877] input_method died, respawning...
[09:50:23.877] launching '/usr/libexec/weston-keyboard'
[09:50:23.878] compositor: executing '/usr/libexec/weston-keyboard' failed: No such file or directory
[09:50:23.878] libwayland: disconnect from client 0x9aea40
[09:50:23.878] input_method died, giving up.
ERROR loading icon from file '/usr/share/icons/hicolor/24x24/apps/google-chrome.png', error: 'file not found'
ERROR loading icon from file '/usr/share/icons/hicolor/24x24/apps/google-chrome.png', error: 'file not found'
[09:50:27.021] already in the native mode
[09:50:27.021] already in the native mode
[09:50:29.941] forked X server, pid 4516

X.Org X Server 1.15.0
Release Date: 2013-12-27
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.12.9-2-ARCH x86_64 
Current Operating System: Linux nekhomeworkstation 3.12.9-2-ARCH #1 SMP PREEMPT Fri Jan 31 10:22:54 CET 2014 x86_64
Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=6fba374c-edcc-4c19-8c30-d0d563961123 rw quiet usbhid.mousepoll=2
Build Date: 07 February 2014  07:06:32AM
 
Current version of pixman: 0.32.4
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.2.log", Time: Sat Feb 22 09:50:29 2014
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
setversion 1.4 failed: Permission denied
Initializing built-in extension Generic Event Extension
Initializing built-in extension SHAPE
Initializing built-in extension MIT-SHM
Initializing built-in extension XInputExtension
Initializing built-in extension XTEST
Initializing built-in extension BIG-REQUESTS
Initializing built-in extension SYNC
Initializing built-in extension XKEYBOARD
Initializing built-in extension XC-MISC
Initializing built-in extension SECURITY
Initializing built-in extension XINERAMA
Initializing built-in extension XFIXES
Initializing built-in extension RENDER
Initializing built-in extension RANDR
Initializing built-in extension COMPOSITE
Initializing built-in extension DAMAGE
Initializing built-in extension MIT-SCREEN-SAVER
Initializing built-in extension DOUBLE-BUFFER
Initializing built-in extension RECORD
Initializing built-in extension DPMS
Initializing built-in extension Present
Initializing built-in extension DRI3
Initializing built-in extension X-Resource
Initializing built-in extension XVideo
Initializing built-in extension XVideo-MotionCompensation
Initializing built-in extension XFree86-VidModeExtension
Initializing built-in extension XFree86-DGA
Initializing built-in extension XFree86-DRI
Initializing built-in extension DRI2
Loading extension GLX
[09:50:29.956] deactivating session
(EE) 
Fatal server error:
(EE) no screens found(EE) 
(EE) 
Please consult the The X.Org Foundation support 
         at http://wiki.x.org
 for help. 
(EE) Please also check the log file at "/var/log/Xorg.2.log" for additional information.
(EE) 
(EE) Server terminated with error (1). Closing log file.
[09:50:30.714] activating session
[09:50:30.715] input device Power Button, /dev/input/event5 is a keyboard
[09:50:30.716] input device Power Button, /dev/input/event4 is a keyboard
[09:50:30.716] not using input device '/dev/input/event16'.
[09:50:30.716] not using input device '/dev/input/event7'.
[09:50:30.716] not using input device '/dev/input/event15'.
[09:50:30.716] not using input device '/dev/input/event14'.
[09:50:30.717] not using input device '/dev/input/event13'.
[09:50:30.717] not using input device '/dev/input/event12'.
[09:50:30.717] not using input device '/dev/input/event11'.
[09:50:30.717] not using input device '/dev/input/event10'.
[09:50:30.717] not using input device '/dev/input/event9'.
[09:50:30.717] not using input device '/dev/input/event8'.
[09:50:30.717] input device USB Keyboard, /dev/input/event0 is a keyboard
[09:50:30.717] input device USB Keyboard, /dev/input/event1 is a keyboard
[09:50:30.717] input device Microsoft Microsoft 5-Button Mouse with IntelliEye(TM), /dev/input/event2 is a pointer caps = relative-motion button
[09:50:30.718] input device Razer Razer DeathAdder, /dev/input/event3 is a pointer caps = relative-motion button
[09:50:30.718] not using input device '/dev/input/event6'.
[09:50:30.718] libwayland: disconnect from client 0xcf3210
[09:50:30.718] xserver crashing too fast: 256
[09:50:32.851] libwayland: disconnect from client 0xcbc740

As you can see, there's no info at all about even trying to change the mode, it just lists the 60hz mode as the prefered and current.

Also I see some serious issues with weston/wayland, one is that it is not entirely smooth, as the movement of windows is jerky and skips frames. The other issue is that the mouse cursor feels slow, which means that probably there's significant input lag. And another issue is that while moving windows with the mouse, the window lags behind the mouse cursor.

All of which, are issues that wayland and weston were supposed to be designed in the first place to eliminate once and for all. Well, encountering all of them again, is very disappointing to say the least.

What is the problem and weston/wayland can't deliver what was promised?

Last edited by Nektarios (2014-02-22 08:20:36)

blackout23 · 2014-02-23 23:16:48

Can't say that wayland/weston feels laggy or stuttery. I only encountered this when using the nvidia driver from [extra] and starting weston on X11 with the x11-backend.so. It will fallback to llvmpipe and everything basically runs on the CPU. After installing the NVIDIA beta driver which now comes with EGL and GLES2 weston is super fast. It actually uses the proprietary drivers EGL implemenation.

Date: 2014-02-24 CET
[00:13:09.114] weston 1.4.0
               http://wayland.freedesktop.org/
               Bug reports to: https://bugs.freedesktop.org/enter_bug.cgi?product=Wayland&component=weston&version=1.4.0
               Build:  
[00:13:09.114] OS: Linux, 3.13.4-1-ARCH, #1 SMP PREEMPT Thu Feb 20 23:54:52 CET 2014, x86_64
[00:13:09.114] Starting with no config file.
[00:13:09.115] Loading module '/usr/lib/weston/x11-backend.so'
[00:13:09.134] initializing x11 backend
[00:13:09.136] Loading module '/usr/lib/weston/gl-renderer.so'
[00:13:09.139] Using gl renderer
[00:13:09.139] launching '/usr/lib/weston/weston-keyboard'
[00:13:09.218] Chosen EGL config details:
               RGBA bits: 8 8 8 8
               swap interval range: 0 - 200
[00:13:09.314] EGL version: 1.4
[00:13:09.314] EGL vendor: NVIDIA
[00:13:09.314] EGL client APIs: OpenGL_ES
[00:13:09.314] EGL extensions: EGL_NV_system_time EGL_KHR_surfaceless_context
               EGL_KHR_image EGL_KHR_image_base EGL_KHR_image_pixmap
               EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image
               EGL_KHR_gl_renderbuffer_image EGL_KHR_config_attribs
               EGL_KHR_fence_sync EGL_NV_sync EGL_KHR_reusable_sync
               EGL_KHR_create_context EGL_EXT_create_context_robustness
               EGL_KHR_stream EGL_KHR_stream_fifo
               EGL_KHR_stream_producer_eglsurface
               EGL_KHR_stream_consumer_gltexture EGL_NV_stream_sync
               EGL_KHR_get_all_proc_addresses
[00:13:09.314] GL version: OpenGL ES 2.0 334.16
[00:13:09.314] GLSL version: OpenGL ES GLSL ES 1.00
[00:13:09.314] GL vendor: NVIDIA Corporation
[00:13:09.314] GL renderer: GeForce GTX 580/PCIe/SSE2
[00:13:09.314] GL extensions: GL_EXT_blend_minmax GL_EXT_color_buffer_float
               GL_EXT_color_buffer_half_float GL_EXT_debug_label
               GL_EXT_frag_depth GL_EXT_map_buffer_range
               GL_EXT_occlusion_query_boolean GL_EXT_robustness
               GL_EXT_separate_shader_objects GL_EXT_shader_integer_mix
               GL_EXT_shadow_samplers GL_EXT_sRGB
               GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_s3tc
               GL_EXT_texture_filter_anisotropic
               GL_EXT_texture_format_BGRA8888 GL_EXT_texture_sRGB_decode
               GL_EXT_texture_storage GL_EXT_unpack_subimage GL_KHR_debug
               GL_NV_bgr GL_NV_blend_equation_advanced GL_NV_copy_buffer
               GL_NV_copy_image GL_NV_draw_buffers GL_NV_draw_instanced
               GL_NV_draw_texture GL_NV_EGL_stream_consumer_external
               GL_NV_explicit_attrib_location GL_NV_fbo_color_attachments
               GL_NV_framebuffer_blit GL_NV_framebuffer_multisample
               GL_NV_generate_mipmap_sRGB GL_NV_instanced_arrays
               GL_NV_occlusion_query_samples GL_NV_non_square_matrices
               GL_NV_pack_subimage GL_NV_packed_float
               GL_NV_pixel_buffer_object GL_NV_read_buffer GL_NV_read_depth
               GL_NV_read_depth_stencil GL_NV_read_stencil
               GL_NV_shadow_samplers_array GL_NV_shadow_samplers_cube
               GL_NV_sRGB_formats GL_NV_texture_array
               GL_NV_texture_border_clamp GL_NV_texture_compression_latc
               GL_NV_texture_compression_s3tc
               GL_NV_texture_compression_s3tc_update GL_NV_timer_query
               GL_OES_compressed_ETC1_RGB8_texture GL_OES_depth24
               GL_OES_depth32 GL_OES_depth_texture
               GL_OES_depth_texture_cube_map GL_OES_EGL_image GL_OES_EGL_sync
               GL_OES_element_index_uint GL_OES_fbo_render_mipmap
               GL_OES_get_program_binary GL_OES_mapbuffer
               GL_OES_packed_depth_stencil GL_OES_rgb8_rgba8
               GL_OES_standard_derivatives GL_OES_surfaceless_context
               GL_OES_texture_npot GL_OES_texture_half_float
               GL_OES_texture_half_float_linear GL_OES_vertex_array_object
               GL_OES_vertex_half_float
[00:13:09.315] warning: EGL_EXT_buffer_age not supported. Performance could be affected.
[00:13:09.315] GL ES 2 renderer features:
               read-back format: RGBA
               wl_shm sub-image to texture: yes
               EGL Wayland extension: no
[00:13:09.315] x11 output 1024x640, window id 29360133
[00:13:09.315] Loading module '/usr/lib/weston/desktop-shell.so'
[00:13:09.315] Compositor capabilities:
               arbitrary surface rotation: yes
               screen capture uses y-flip: yes
[00:13:09.315] libwayland: using socket /run/user/1000/wayland-0
[00:13:09.330] launching '/usr/lib/weston/weston-desktop-shell'
[00:13:16.026] libwayland: disconnect from client 0xe87b30
[00:13:16.026] libwayland: disconnect from client 0xebeba0

The background seems to be captured framebuffer pieces from X11 but the windows etc. work and perform very well. Starting gnome-calculator with GDK_BACKEND=wayland also works and everything is responsive. Don't know why it uses OpenGL ES 2.0. The driver supports even 3.0.

Last edited by blackout23 (2014-02-23 23:35:56)

Nektarios · 2014-02-26 06:51:00

Nektarios wrote:

I am trying to start weston with my second monitor at 120hz instead of 60hz at it's default resolution of 1680x1050. I used the output section in my ~/.config/weston.ini file, setting the appropriate modeline but it doesn't work. here is the relevant part of the ini:

OK I figured it out (wasted hours, analyzing the weston code, editing it and compiling), the problem was that there is no "modeline" setting, there's just "mode". [strike]The example configuration in the wiki has it wrong and it misguided me completely. It needs to be updated, I'll try to see if I can do it.[/strike] update: I changed it, it's correct now.

For the record, to set the modeline you do it like this:

[output]
name=DVI2
mode=238.5 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync

Last edited by Nektarios (2014-02-26 07:11:21)

Nektarios · 2014-02-26 07:05:33

Now that I tried weston/wayland with a 120hz monitor I can say that it is very fluent and works nice and smooth. I did some simple tests, I opened about 100 terminal windows and moved them around to see if having many windows degrades performance but it was smooth without any stuttering of frame loss/hiccup. I watched the cpu usage of weston process while I was moving the windows around and it was at about 10-15 percent, 0 when I did not move anything . I then tried the zoom function while moving my mouse around and the cpu usage got up to 60% with both screens zoomed in and moving. It was smooth with no frame loss. I consider this very good performance considering that one monitor was working at 120hz 1680x1050 and the second (30inch) at 2560x1600 which require substantial work.

I also tried weston-gears which only delivered 75fps, which is strange because on my 120hz screen it should be 120. I also tried the weston-simple-egl which run at 120fps constant and with no problem, even when moving it around, btw the cpu usage was very low. So far my testing was positive. Although I still feel that on my 120hz monitor, the window movement isn't really rendering at 120fps and it generaly lags a little bit (input lag). Therefore I would like to measure the framerate of weston to find out and make sure, is there a way to do that?

I also have another problem, this time with xwayland. I followed the wiki instructions for xwayland support and installed xorg-server-xwayland-git with xf86-video-wlglamor-xwayland-git with the appropriate config in the weson.ini, but when I run an x client, for instance chromium, it complains that DISPLAY :2 screen is not found. Any help with that?

Last edited by Nektarios (2014-02-26 07:10:28)

haagch · 2014-05-01 00:24:23

I tried a bit today:

qt5-wayland-git almost compiles with the repository's qt5. With minor fixes it works.

I also wanted to try the wayland experience, so I compiled xorg-server-git with added --enable-glamor --enable-xwayland. Apparently weston from the repositories doesn't like that yet, so I also compiled wayland-git and weston-git (--enable-xwayland too, not sure if needed). Then from the weston repository, copying src/weston/weston.ini to ~/.config/ and uncommenting the first line with the xwayland module.

Then xwayland works. But not very well. Crashy, and major gui bugs (not rendering bugs, that's fine, just mouse input etc.)

I heard xf86-video-wlglamor is included so I intentionally didn't install xf86-video-intel-wayland, and it did work, but apparently you only get llvmpipe in xwayland...?

orbital doesn't seem to start right now, weston-desktop-shell always crashes.
hawaii has way too many dependencies for me.

qt5 programs with -platform wayland work okay I guess, weston from the repository crashes easily with playing around in qtcreator, weston-git doesn't.
gtk3 programs work a bit, but when I try midori from the pantheon repository, it crashes when trying to input an url in the url bar....

jdbrown · 2014-05-01 02:19:00

I also had a similar attempt several days ago and I was able to launch gnome 3.12 with some hack on the new xwayland ddx.

I used xorg-server-dev 1.15.99.902, added --enable-xwayland (installed libepoxy-git before building). Installed wayland and weston 1.4.91 (git version also okay). And replaced mutter-wayland package with this git snapshot (mutter is undergoing great changes recently, wayland support is being merged in the main source instead of a separate branch, so I chose an earlier snapshot before that merge).

Gnome shell launches after executing

gnome-session --session=gnome-wayland

in the VT. It generally works but there were some glitches here and there. Also got llvmpipe.

I don't know why xwayland shows that it uses llvmpipe, but what I know is the xwayland in mainline code doesn't seem to have hardware acceleration (see this article for details). The code for glamor integration and dri3 exists at xwayland-glamor branch, but it requires latest git version of mesa (that's why it is not mainlined presently). I compiled that but it failed to launch in my vmware virtual machine (maybe the problem of vmware driver). Those who are interested may try it on other hardware.

A further note is that xwayland now serves as a Device Dependent X and uses glamor for 2d, and I think drivers like xf86-video-intel-wayland and so on are not needed anymore.

Last edited by jdbrown (2014-05-01 02:22:31)

haagch · 2014-05-01 07:42:24

Oh, I didn't know this stuff wasn't mainlined yet.

The xwayland-dri3 branch over there seems to be much more recent: http://cgit.freedesktop.org/~krh/xserve … yland-dri3

edit: Nice

Last edited by haagch (2014-05-01 07:59:28)

haagch · 2014-05-02 09:49:23

gnome-session-wayland doesn't seem to work, it fails in nothing gnome specific, but already glib/gobject...

#0  0x00007ffff6592696 in __strcmp_ssse3 () from /usr/lib/libc.so.6
#1  0x00007ffff6850fc9 in g_str_equal () from /usr/lib/libglib-2.0.so.0
#2  0x000000000041c38f in ?? ()
#3  0x000000000041c598 in ?? ()
#4  0x00007ffff6b50e5b in g_type_create_instance ()
   from /usr/lib/libgobject-2.0.so.0
#5  0x00007ffff6b35375 in ?? () from /usr/lib/libgobject-2.0.so.0
#6  0x00007ffff6b3712d in g_object_newv () from /usr/lib/libgobject-2.0.so.0
#7  0x00007ffff6b378dc in g_object_new () from /usr/lib/libgobject-2.0.so.0
#8  0x0000000000417552 in ?? ()
#9  0x00007ffff6b3250d in g_cclosure_marshal_VOID__UCHARv ()
   from /usr/lib/libgobject-2.0.so.0
#10 0x00007ffff6b30607 in ?? () from /usr/lib/libgobject-2.0.so.0
#11 0x00007ffff6b490a8 in g_signal_emit_valist ()
   from /usr/lib/libgobject-2.0.so.0
#12 0x00007ffff6b49d02 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#13 0x00007ffff685d914 in ?? () from /usr/lib/libglib-2.0.so.0
#14 0x00007ffff6860a65 in g_main_context_dispatch ()
   from /usr/lib/libglib-2.0.so.0
#15 0x00007ffff6860dc8 in ?? () from /usr/lib/libglib-2.0.so.0
#16 0x00007ffff686108a in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#17 0x00000000004091e0 in ?? ()
#18 0x00007ffff648a000 in __libc_start_main () from /usr/lib/libc.so.6
#19 0x00000000004092f8 in ?? ()

blackout23 · 2014-05-09 16:31:41

I made an easy step by step guide on how to run Gnome on Wayland. You basically have to do only 2 things.

http://www.reddit.com/r/LinuxActionShow … d_on_arch/

jdbrown · 2014-05-10 03:53:57

blackout23 wrote:

I made an easy step by step guide on how to run Gnome on Wayland. You basically have to do only 2 things.
http://www.reddit.com/r/LinuxActionShow … d_on_arch/

Great work, I got Gnome on Wayland run on my laptop.

A thing to mention is the Xwayland installed according to your guide doesn't get hardware acceleration. You can see 'llvmpipe' if you run things like glxinfo or so on. You can also notice that the process 'gnome-shell-wayland' eats up over 10% cpu. To get hardware acceleration you can clone from git://people.freedesktop.org/~krh/xserver#branch=xwayland-dri3 and add --enable-glamor in the configure flags. And you have to install mesa 10.2-rc1 or mesa-git (mesa 10.2 will be released soon) before building Xwayland).

blackout23 · 2014-05-10 06:51:57

jdbrown wrote:

blackout23 wrote:
I made an easy step by step guide on how to run Gnome on Wayland. You basically have to do only 2 things.
http://www.reddit.com/r/LinuxActionShow … d_on_arch/
Great work, I got Gnome on Wayland run on my laptop.
A thing to mention is the Xwayland installed according to your guide doesn't get hardware acceleration. You can see 'llvmpipe' if you run things like glxinfo or so on. You can also notice that the process 'gnome-shell-wayland' eats up over 10% cpu. To get hardware acceleration you can clone from git://people.freedesktop.org/~krh/xserver#branch=xwayland-dri3 and add --enable-glamor in the configure flags. And you have to install mesa 10.2-rc1 or mesa-git (mesa 10.2 will be released soon) before building Xwayland).

Thanks. I also noticed that this is in his branch, but wondered if this is also in the official xorg git repo since this: http://lists.x.org/archives/xorg-devel/ … 41579.html

Does hardware acceleration work after that or would it also need some further changes to mutter-wayland? Would I need intel graphics and some extra glamor related packages like glamor-egl? I'm using nouveau atm which doesn't have glamor support as far as I know.

I was able to build Kristians branch with --enable-glamor without installing the dev version of mesa. Didn't change anything. Also installing mesa-git later didn't change anything.

Last edited by blackout23 (2014-05-10 08:02:02)

jdbrown · 2014-05-10 09:02:59

The code mainlined now doesn't seem to have hardware acceleration. See the above posts this page.

I remembered seeing that the dri and glamor part of xwayland needs libgbm (part of mesa) to be newer than 10.2-devel, but I don't really know if that matters.

nouveau should be ok to use hardware acceleration since xwayland now use the built–in glamor as means of acceleration and it is usable if you use the open source drivers.

mutter–wayland doesn't need recompiling. I actually use the same version as yours. You can check whether you get hw acceleration in "System details" in gnome settings.

Last edited by jdbrown (2014-05-10 09:09:52)

progandy · 2014-05-10 09:55:59

jdbrown wrote:

The code mainlined now doesn't seem to have hardware acceleration. See the above posts this page.
I remembered seeing that the dri and glamor part of xwayland needs libgbm (part of mesa) to be newer than 10.2-devel, but I don't really know if that matters.

Hardware acceleration will be added when a stable mesa 20.2 is released.
http://lists.x.org/archives/xorg-devel/ … 41702.html

jdbrown · 2014-05-10 11:00:48

Yeah, things will be much better after that.

surfatwork · 2014-08-07 11:12:57

Hello, apologies if this is a newbie question - I "am" a weston/wayland/hawaii newbie, but have been a arch user for a fairly long time.
anyway, I wanted to try out hawaii, without any X. So I
1. installed arch fresh on a new partition (just base and base-devel), and the basic setup such as locale etc.
2. installed xf86-video-intel,which pulled in intel-dri
3. downgraded mesa, mesa-libgl and intel-dri with the packages from the Maui website
4. added the hawaii repository and installed the binaries using pacman -S
5. check weston was working with weston-launch which launched me into a basic weston desktop with weston-terminal. Exited with ctrl-alt-bkspc
6. ran "hawaii" as a normal user from the CLI (not inside the graphical desktop)
...and got a black screen. No errors. ctrl-alt-bkspc doesnt work. Killing the "hawaii" process from another tty didnt uncover any CLI errors from hawaii/weston. tried hawaii > 1.log, but didnt get any output. also tried hawaii -v, which produced a single line of not very decipherable numbers.

Am I missing something here? thanks

maslascher · 2014-08-09 16:10:47

@up. Well, i won't recommend using Hawaii desktop. This stuff is under critical development and pretty much everything doesn't work. I have managed to start Hawaii but after a moment it was hanging. I have not downgrade mesa because drivers was working.
I would recommend Weston plus few apps and after config you have almost daily usable desktop. But there are some disadvantages. Weston is stable but when you run something through XWayland then after a few minutes Weston will crash (bug is already reported and someone is working on it). Also hardware acceleration is not working but thanks to Wayland and weston is light pretty much everything is running smooth even on ancient hardware.
Also Wayland transform of apps from X is like never ending story, there is some progress but it is to slow and XWayland not always work as it should be.
PS. Libinput in repos is old (0.2) and there is new stable version (0.5), could someone update it? Mutter-git is impossible to build, could someone update PKGBUILD?

Scimmia · 2014-08-09 16:16:51

maslascher wrote:

PS. Libinput in repos is old (0.2) and there is new stable version (0.5), could someone update it? Mutter-git is impossible to build, could someone update PKGBUILD?

Not impossible to build, just use libinput-git.

jdbrown · 2014-08-10 04:20:07

maslascher wrote:

PS. Libinput in repos is old (0.2) and there is new stable version (0.5), could someone update it? Mutter-git is impossible to build, could someone update PKGBUILD?

libinput 0.5 and libinput 0.2 are API incompatible, and the current gnome 3.12 depends on libinput 0.2. That's why the libinput in repo is 0.2. If you want libinput 0.5 (or even newer), you should upgrade nearly the whole gnome stack to unstable versions or just wait until gnome 3.14 hits the official repo in two month's time.

libinput is still in heavy development and there has been several API breaks in recent versions (0.2, 0.3 and 0.4 are incompatible with each other). Only development versions track that API precisely so we'll have to wait if we care about the usability of stable ones.

maslascher · 2014-08-10 15:20:34

@up&2xup- Ok, that will be explain why libinput in newer version break Gnome Shell. Sorry for waste of time.

@Scimmia, last i check (maybe two weeks ago) i was unable to build because of error, all dependencies was installed.

surfatwork · 2014-08-12 08:49:17

I am not sure if anything's happening on hawaii anymore. my post on the maui google groups got 2 views in 4 days - which doesnt seem particularly indicative of a thriving community.
hawaii seems to have had it's 2 mins of fame....a shame, it seemed promising. perhaps the underlying components aren't just mature enough.
oh well, there will be others.

Giselher · 2014-08-14 12:15:59

surfatwork wrote:

I am not sure if anything's happening on hawaii anymore. my post on the maui google groups got 2 views in 4 days - which doesnt seem particularly indicative of a thriving community.
hawaii seems to have had it's 2 mins of fame....a shame, it seemed promising. perhaps the underlying components aren't just mature enough.
oh well, there will be others.

The git repositories still show recent (28 minutes ago) activity. I guess the mailing list was just abandoned.

stozi · 2014-09-05 15:46:33

anyone know why I wouldn't be able to move or close windows in weston?

jdbrown · 2014-09-06 00:52:06

stozi wrote:

anyone know why I wouldn't be able to move or close windows in weston?

Are they gtk3 applications? Their xdg_shell protocol (not yet stable) may be incompatible with weston. The ones in gnome 3.14 and weston 1.6 will be okay I think.

Arch Linux

#251 2014-01-16 12:46:31

Re: Wayland on Arch Linux?

#252 2014-01-30 17:17:18

Re: Wayland on Arch Linux?

#253 2014-02-22 08:15:48

Re: Wayland on Arch Linux?

#254 2014-02-23 23:16:48

Re: Wayland on Arch Linux?

#255 2014-02-26 06:51:00

Re: Wayland on Arch Linux?

#256 2014-02-26 07:05:33

Re: Wayland on Arch Linux?

#257 2014-05-01 00:24:23

Re: Wayland on Arch Linux?

#258 2014-05-01 02:19:00

Re: Wayland on Arch Linux?

#259 2014-05-01 07:42:24

Re: Wayland on Arch Linux?

#260 2014-05-02 09:49:23

Re: Wayland on Arch Linux?

#261 2014-05-09 16:31:41

Re: Wayland on Arch Linux?

#262 2014-05-10 03:53:57

Re: Wayland on Arch Linux?

#263 2014-05-10 06:51:57

Re: Wayland on Arch Linux?

#264 2014-05-10 09:02:59

Re: Wayland on Arch Linux?

#265 2014-05-10 09:55:59

Re: Wayland on Arch Linux?

#266 2014-05-10 11:00:48

Re: Wayland on Arch Linux?

#267 2014-08-07 11:12:57

Re: Wayland on Arch Linux?

#268 2014-08-09 16:10:47

Re: Wayland on Arch Linux?

#269 2014-08-09 16:16:51

Re: Wayland on Arch Linux?

#270 2014-08-10 04:20:07

Re: Wayland on Arch Linux?

#271 2014-08-10 15:20:34

Re: Wayland on Arch Linux?

#272 2014-08-12 08:49:17

Re: Wayland on Arch Linux?

#273 2014-08-14 12:15:59

Re: Wayland on Arch Linux?

#274 2014-09-05 15:46:33

Re: Wayland on Arch Linux?

#275 2014-09-06 00:52:06

Re: Wayland on Arch Linux?

Board footer