weston issueshttps://gitlab.freedesktop.org/wayland/weston/-/issues2023-05-23T07:04:32Zhttps://gitlab.freedesktop.org/wayland/weston/-/issues/753sunxi lima driver weston doesn't work2023-05-23T07:04:32ZMarek Beliskosunxi lima driver weston doesn't workI'm trying to enable weston on sunxi H5 board. I've build image using yocto with 5.15 kernel and instead of proprietary mali driver I'm using opensource lima driver with mesa. When trying to start weston in following way:
```
root@orang...I'm trying to enable weston on sunxi H5 board. I've build image using yocto with 5.15 kernel and instead of proprietary mali driver I'm using opensource lima driver with mesa. When trying to start weston in following way:
```
root@orange-pi-pc2:~# weston --modules=systemd-notify.so --debug --tty=7
```
I'm getting following.
```
Date: 2022-04-28 UTC
[17:54:16.468] weston 10.0.1
https://wayland.freedesktop.org
Bug reports to: https://gitlab.freedesktop.org/wayland/weston/issues/
Build: 10.0.1
[17:54:16.468] Command line: weston --modules=systemd-notify.so --debug --tty=7
[17:54:16.468] OS: Linux, 5.15.35, #1 SMP PREEMPT Wed Apr 20 07:34:22 UTC 2022, aarch64
[17:54:16.468] Flight recorder: enabled
[17:54:16.468] Using config file '/etc/xdg/weston/weston.ini'
WARNING: debug protocol has been enabled. This is a potential denial-of-service attack vector and information leak.
[17:54:16.469] Output repaint window is 7 ms maximum.
[17:54:16.469] Loading module '/usr/lib/libweston-10/drm-backend.so'
[17:54:16.489] initializing drm backend
[17:54:16.489] Trying logind launcher...
[17:54:16.490] logind: failed to get session seat
[17:54:16.490] logind: cannot setup systemd-logind helper error: (No data available), using legacy fallback
[17:54:16.490] Trying weston_launch launcher...
[17:54:16.490] could not get launcher fd from env
[17:54:16.490] Trying direct launcher...
[17:54:16.496] using /dev/dri/card1
[17:54:16.496] DRM: supports atomic modesetting
[17:54:16.496] DRM: supports GBM modifiers
[17:54:16.497] DRM: supports picture aspect ratio
[17:54:16.497] Loading module '/usr/lib/libweston-10/gl-renderer.so'
[17:54:16.548] EGL client extensions: EGL_EXT_client_extensions
EGL_EXT_device_base EGL_EXT_device_enumeration
EGL_EXT_device_query EGL_EXT_platform_base
EGL_KHR_client_get_all_proc_addresses EGL_KHR_debug
EGL_EXT_platform_device EGL_EXT_platform_wayland
EGL_KHR_platform_wayland EGL_EXT_platform_x11
EGL_KHR_platform_x11 EGL_MESA_platform_xcb
EGL_MESA_platform_gbm EGL_KHR_platform_gbm
EGL_MESA_platform_surfaceless
[17:54:16.551] EGL device extensions: EGL_EXT_device_drm
[17:54:16.551] EGL version: 1.4
[17:54:16.551] EGL vendor: Mesa Project
[17:54:16.551] EGL client APIs: OpenGL OpenGL_ES
[17:54:16.551] EGL extensions: EGL_ANDROID_blob_cache
EGL_ANDROID_native_fence_sync EGL_EXT_buffer_age
EGL_EXT_image_dma_buf_import
EGL_EXT_image_dma_buf_import_modifiers EGL_KHR_cl_event2
EGL_KHR_config_attribs EGL_KHR_create_context
EGL_KHR_create_context_no_error EGL_KHR_fence_sync
EGL_KHR_get_all_proc_addresses EGL_KHR_gl_colorspace
EGL_KHR_gl_renderbuffer_image EGL_KHR_gl_texture_2D_image
EGL_KHR_gl_texture_3D_image EGL_KHR_gl_texture_cubemap_image
EGL_KHR_image EGL_KHR_image_base EGL_KHR_image_pixmap
EGL_KHR_no_config_context EGL_KHR_partial_update
EGL_KHR_reusable_sync EGL_KHR_surfaceless_context
EGL_EXT_pixel_format_float EGL_KHR_wait_sync
EGL_MESA_configless_context EGL_MESA_drm_image
EGL_MESA_image_dma_buf_export EGL_MESA_query_driver
EGL_WL_bind_wayland_display
[17:54:16.552] EGL_KHR_surfaceless_context available
[17:54:16.562] GL version: OpenGL ES 2.0 Mesa 22.0.3
[17:54:16.563] GLSL version: OpenGL ES GLSL ES 1.0.16
[17:54:16.563] GL vendor: lima
[17:54:16.563] GL renderer: Mali450
[17:54:16.563] GL extensions: GL_EXT_blend_minmax GL_EXT_multi_draw_arrays
GL_EXT_texture_format_BGRA8888
GL_OES_compressed_ETC1_RGB8_texture 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_half_float
GL_OES_texture_half_float_linear GL_OES_texture_npot
GL_OES_vertex_half_float GL_OES_EGL_image GL_OES_depth_texture
GL_OES_packed_depth_stencil GL_OES_get_program_binary
GL_APPLE_texture_max_level GL_EXT_discard_framebuffer
GL_EXT_read_format_bgra GL_EXT_frag_depth
GL_NV_fbo_color_attachments GL_OES_EGL_image_external
GL_OES_EGL_sync GL_OES_vertex_array_object
GL_ANGLE_pack_reverse_row_order GL_EXT_texture_rg
GL_EXT_unpack_subimage GL_NV_draw_buffers GL_NV_read_buffer
GL_NV_read_depth GL_NV_read_depth_stencil GL_NV_read_stencil
GL_EXT_draw_buffers GL_EXT_map_buffer_range GL_KHR_debug
GL_KHR_texture_compression_astc_ldr GL_NV_pixel_buffer_object
GL_OES_required_internalformat GL_OES_surfaceless_context
GL_EXT_separate_shader_objects
GL_EXT_compressed_ETC1_RGB8_sub_texture
GL_EXT_draw_elements_base_vertex GL_EXT_texture_border_clamp
GL_KHR_context_flush_control GL_OES_draw_elements_base_vertex
GL_OES_texture_border_clamp GL_EXT_blend_func_extended
GL_KHR_no_error GL_KHR_texture_compression_astc_sliced_3d
GL_EXT_clip_control GL_KHR_parallel_shader_compile GL_MESA_bgra
[17:54:16.615] GL ES 2.0 - renderer features:
read-back format: BGRA
EGL Wayland extension: yes
[17:54:16.630] event0 - r-gpio-keys: not tagged as supported input device
[17:54:16.658] event0 - not using input device '/dev/input/event0'
[17:54:16.658] warning: no input devices found, but none required as per configuration.
[17:54:16.864] DRM: head 'HDMI-A-1' updated, connector 51 is connected, EDID make 'HWP', model 'HP 27es', serial '3CM8130KPY '
[17:54:16.864] DRM: head 'HDMI-A-1' found, connector 51 is connected, EDID make 'HWP', model 'HP 27es', serial '3CM8130KPY '
[17:54:16.865] Registered plugin API 'weston_drm_output_api_v1' of size 24
[17:54:16.865] Color manager: no-op
[17:54:16.865] Output 'HDMI-A-1' using color profile: built-in default sRGB SDR profile
[17:54:16.865] format 0x34325258 not supported by output HDMI-A-1
[17:54:16.865] failed to create gbm surface
[17:54:16.865] Failed to init output gl state
[17:54:16.865] Enabling output "HDMI-A-1" failed.
[17:54:16.865] Error: cannot enable output 'HDMI-A-1' without heads.
```
Am I missing something or this is not supported ATM? Thanks.https://gitlab.freedesktop.org/wayland/weston/-/issues/752multiple GPU support in drm backend2023-05-11T10:44:25Zsophia gongmultiple GPU support in drm backendHi,
i'm going to enable two gpu in our system, one gpu for client gfx render, both gpu for display output. weston 11 develops a new feature to support multi backend, could this feature support multi gpu in our case? could someone introd...Hi,
i'm going to enable two gpu in our system, one gpu for client gfx render, both gpu for display output. weston 11 develops a new feature to support multi backend, could this feature support multi gpu in our case? could someone introduce more details about how multi backend implement? thanks!
Sophiahttps://gitlab.freedesktop.org/wayland/weston/-/issues/751Add/enforce pointer constraint to kiosk-shell2023-05-03T07:42:52ZMarius VladAdd/enforce pointer constraint to kiosk-shellThis is a follow-up from https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1202 to implement something similar to kiosk-shell.This is a follow-up from https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1202 to implement something similar to kiosk-shell.https://gitlab.freedesktop.org/wayland/weston/-/issues/750Dimming screensaver2023-05-03T12:50:11ZKjeld FlarupDimming screensaverI learned that the external screensaver has been removed from Weston.
I found that it is possible to totally blank the screen with the idle parameter, and wake it up again with input.
This is so far fine, but we are running a kiosk ser...I learned that the external screensaver has been removed from Weston.
I found that it is possible to totally blank the screen with the idle parameter, and wake it up again with input.
This is so far fine, but we are running a kiosk service, and want the screen to dim to save power, and when the screen is touched, then it will increase the backlight to 100% again.
I had hoped this was possible with an external screensaver, but as this is no-longer supported, what can I use then?https://gitlab.freedesktop.org/wayland/weston/-/issues/749Kicad very sluggish when some of its windows are hidden2023-05-02T10:09:00ZNicolas GoyKicad very sluggish when some of its windows are hiddenHello.
First I am sorry if this is not directly a wayland, as I am trying to find what causes it.
I run wayland, with sway 1.8.1, and I use kicad under xwayland.
The issue is quite simple to explain and reproduce, if any of kicad wind...Hello.
First I am sorry if this is not directly a wayland, as I am trying to find what causes it.
I run wayland, with sway 1.8.1, and I use kicad under xwayland.
The issue is quite simple to explain and reproduce, if any of kicad window is not directly visible, the whole application becomes very sluggish, with mini freezes all over the place.
I would really like to help pinpoint and fix this issue as it is the only major issue making kicad hard to use on wayland (xwayland).
References: https://gitlab.com/kicad/code/kicad/-/issues/7207#note_1357779464https://gitlab.freedesktop.org/wayland/weston/-/issues/748Segfault while writing in Firefox2023-11-02T10:16:54ZLink MauveSegfault while writing in FirefoxThis is possibly at the intersection of writing something and a tooltip being displayed by the pointer staying still on top of some other element.
Here is the stack trace:
```
Program terminated with signal SIGSEGV, Segmentation fault.
...This is possibly at the intersection of writing something and a tooltip being displayed by the pointer staying still on top of some other element.
Here is the stack trace:
```
Program terminated with signal SIGSEGV, Segmentation fault.
#0 has_keyboard_focused_child_callback (surface=<optimized out>, user_data=0x7ffecb2d15b7) at ../desktop-shell/shell.c:1594
Downloading source file /usr/src/debug/weston-git/weston/build/../desktop-shell/shell.c
1594 ../desktop-shell/shell.c: Directory not empty.
[Current thread is 1 (Thread 0x7f303840f8c0 (LWP 2376))]
(gdb) bt
#0 has_keyboard_focused_child_callback (surface=<optimized out>, user_data=0x7ffecb2d15b7) at ../desktop-shell/shell.c:1594
#1 0x00007f3038a29519 in weston_desktop_surface_foreach_child (surface=0x5612dbb09d90, callback=callback@entry=0x7f3036448c90 <has_keyboard_focused_child_callback>, user_data=user_data@entry=0x7ffecb2d15b7) at ../libweston/desktop/surface.c:892
#2 0x00007f3036448dde in has_keyboard_focused_child (shsurf=0x5612dbccc040) at ../desktop-shell/shell.c:1614
#3 sync_surface_activated_state (shsurf=<optimized out>) at ../desktop-shell/shell.c:1635
#4 0x00007f303644cb2c in shell_surface_deactivate (shsurf=<optimized out>) at ../desktop-shell/shell.c:1665
#5 activate (shell=0x5612dbb7e460, view=<optimized out>, seat=0x5612db360c40, flags=flags@entry=1) at ../desktop-shell/shell.c:3759
#6 0x00007f303644f2d0 in switcher_destroy (switcher=0x5612db34fa00) at ../desktop-shell/shell.c:4483
#7 0x00007f3038a18d95 in update_modifier_state (state=WL_KEYBOARD_KEY_STATE_RELEASED, key=125, serial=50597, seat=0x5612db360c40) at ../libweston/input.c:2557
#8 notify_key (seat=<optimized out>, time=time@entry=0x7ffecb2d1780, key=125, state=state@entry=WL_KEYBOARD_KEY_STATE_RELEASED, update_state=update_state@entry=STATE_UPDATE_AUTOMATIC) at ../libweston/input.c:2707
#9 0x00007f3038c5c084 in handle_keyboard_key (keyboard_event=0x5612dbb0e9d0, libinput_device=<optimized out>) at ../libweston/libinput-device.c:107
#10 evdev_device_process_event (event=0x5612dbb0e9d0) at ../libweston/libinput-device.c:775
#11 udev_input_process_event (event=0x5612dbb0e9d0) at ../libweston/libinput-seat.c:206
#12 process_event (event=0x5612dbb0e9d0) at ../libweston/libinput-seat.c:216
#13 process_events (input=input@entry=0x5612db349d38) at ../libweston/libinput-seat.c:226
#14 0x00007f3038c5d09d in udev_input_dispatch (input=0x5612db349d38) at ../libweston/libinput-seat.c:237
#15 libinput_source_dispatch (fd=<optimized out>, mask=<optimized out>, data=0x5612db349d38) at ../libweston/libinput-seat.c:247
#16 0x00007f30389cbb23 in wl_event_loop_dispatch (loop=0x5612db33fc30, timeout=timeout@entry=-1) at ../wayland/src/event-loop.c:1027
#17 0x00007f30389c8e67 in wl_display_run (display=display@entry=0x5612db33fb40) at ../wayland/src/wayland-server.c:1471
#18 0x00007f3038c7dc47 in wet_main (argc=<optimized out>, argv=<optimized out>, test_data=0x0) at ../compositor/main.c:4080
#19 0x00007f3038a73790 in __libc_start_call_main (main=main@entry=0x5612da157020 <main>, argc=argc@entry=1, argv=argv@entry=0x7ffecb2d2338) at ../sysdeps/nptl/libc_start_call_main.h:58
#20 0x00007f3038a7384a in __libc_start_main_impl (main=0x5612da157020 <main>, argc=1, argv=0x7ffecb2d2338, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffecb2d2328) at ../csu/libc-start.c:360
#21 0x00005612da157055 in _start ()
```https://gitlab.freedesktop.org/wayland/weston/-/issues/747Segfault while playing a Xwayland game2023-04-25T09:03:56ZLink MauveSegfault while playing a Xwayland gameHere is the stack trace:
```
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007f416483dcb0 in wm_debug_is_enabled (wm=<optimized out>) at ../xwayland/window-manager.c:221
221 ../xwayland/window-manager.c: No such...Here is the stack trace:
```
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007f416483dcb0 in wm_debug_is_enabled (wm=<optimized out>) at ../xwayland/window-manager.c:221
221 ../xwayland/window-manager.c: No such file or directory.
[Current thread is 1 (Thread 0x7f41667e68c0 (LWP 2063))]
(gdb) bt
#0 0x00007f416483dcb0 in wm_debug_is_enabled (wm=<optimized out>) at ../xwayland/window-manager.c:221
#1 wm_printf (wm=0x562bdb775700, fmt=fmt@entry=0x7f41648490d0 "surface for xid %d destroyed\n") at ../xwayland/window-manager.c:230
#2 0x00007f416483dd7d in surface_destroy (listener=0x562bdb7de2d0, data=<optimized out>) at ../xwayland/window-manager.c:1967
#3 0x00007f4166ddeede in weston_signal_emit_mutable (data=0x562bdb7e8200, signal=0x562bdb7e8208) at ../shared/signal.c:62
#4 weston_surface_unref (surface=0x562bdb7e8200) at ../libweston/compositor.c:2170
#5 0x00007f416485358f in desktop_shell_destroy_surface (shsurf=0x562bdb775070) at ../desktop-shell/shell.c:293
#6 0x00007f4166da2a63 in wl_event_loop_dispatch_idle (loop=loop@entry=0x562bdadecc30) at ../wayland/src/event-loop.c:969
#7 0x00007f4166da2b74 in wl_event_loop_dispatch (loop=0x562bdadecc30, timeout=timeout@entry=-1) at ../wayland/src/event-loop.c:1032
#8 0x00007f4166d9fe67 in wl_display_run (display=display@entry=0x562bdadecb40) at ../wayland/src/wayland-server.c:1471
#9 0x00007f4167054c47 in wet_main (argc=<optimized out>, argv=<optimized out>, test_data=0x0) at ../compositor/main.c:4080
#10 0x00007f4166e4a790 in () at /usr/lib/libc.so.6
#11 0x00007f4166e4a84a in __libc_start_main () at /usr/lib/libc.so.6
#12 0x0000562bda80b055 in _start ()
```
It seems the server became `NULL` somehow, according to gdb still:
```
(gdb) p wm->server
$3 = (struct weston_xserver *) 0x0
```
What is strange is that I wasn’t destroying a surface, it might have been a crash of the game or of Xwayland, although I don’t see that in coredumpctl.https://gitlab.freedesktop.org/wayland/weston/-/issues/746Sudden mouse pointer shift with nested weston x11 backend in GNOME xwayland2023-04-25T05:24:12ZKeyu TaoSudden mouse pointer shift with nested weston x11 backend in GNOME xwaylandVersions:
- Arch Linux
- Weston 11.0.1-1
- Xorg-xwayland 23.1.1-1
- gnome-shell 43.4-1
- mutter 43.4-1
Description:
When using nested weston with x11-backend.so in GNOME Wayland session, mouse pointer inside weston shift unexpectedly f...Versions:
- Arch Linux
- Weston 11.0.1-1
- Xorg-xwayland 23.1.1-1
- gnome-shell 43.4-1
- mutter 43.4-1
Description:
When using nested weston with x11-backend.so in GNOME Wayland session, mouse pointer inside weston shift unexpectedly from time to time. I'm not quite sure whether it is a bug of weston, xwayland or GNOME. The wayland-backend.so does not have this issue.
I know that it is very weird to use x11-backend weston in a wayland session, and I found this issue when using nested X server with weston in x11docker -- I guess I should submit a bug report (let user decide whether to start weston in X or Wayland) to them afterwards.
How to reproduce:
1. In a wayland session (I only tested in GNOME) `weston --backend=x11-backend.so`
2. Start terminal inside weston
3. Drag the terminal window for several rounds, and move mouse to any corner of weston window
4. And then your mouse pointer is moved to an unexpected location
Video:
![Kooha-2023-04-25-05-33-49](/uploads/ac564bb810de630db57ca480851871f7/Kooha-2023-04-25-05-33-49.mp4)https://gitlab.freedesktop.org/wayland/weston/-/issues/745event 0 - Nintendo 3DS input: Device removedoved"2023-04-28T20:36:20ZMason Culwellevent 0 - Nintendo 3DS input: Device removedoved"![WIN_20230423_17_08_00_Pro](/uploads/2e43dab35b4de9d547c79e02e670537b/WIN_20230423_17_08_00_Pro.jpg)
I typed in /start-weston.sh, waited a sec and then this screen popped up and at the bottom had this text; event 0 - Nintendo 3DS input:...![WIN_20230423_17_08_00_Pro](/uploads/2e43dab35b4de9d547c79e02e670537b/WIN_20230423_17_08_00_Pro.jpg)
I typed in /start-weston.sh, waited a sec and then this screen popped up and at the bottom had this text; event 0 - Nintendo 3DS input: Device removedoved"
I watched a video and when somebody else did the exact same procedure this didn't happen to them. Any help?https://gitlab.freedesktop.org/wayland/weston/-/issues/744xssstart: X11 extension MIT-SCREEN-SAVER not supported2023-04-19T12:55:14ZOquirellaxssstart: X11 extension MIT-SCREEN-SAVER not supportedI am trying to run clicklock under weston (xwayland) (https://github.com/zpfvo/clicklock) which should be started using xssstart but i get the following error message:
xssstart: X11 extension MIT-SCREEN-SAVER not supported
xdpinfo tells...I am trying to run clicklock under weston (xwayland) (https://github.com/zpfvo/clicklock) which should be started using xssstart but i get the following error message:
xssstart: X11 extension MIT-SCREEN-SAVER not supported
xdpinfo tells me only the following extensions are available:
number of extensions: 19
BIG-REQUESTS
Composite
DAMAGE
DOUBLE-BUFFER
Generic Event Extension
MIT-SHM
Present
RANDR
RENDER
SHAPE
SYNC
X-Resource
XC-MISC
XFIXES
XFree86-VidModeExtension
XInputExtension
XKEYBOARD
XTEST
XVideo
Any idea why this extension is missing or not supported?https://gitlab.freedesktop.org/wayland/weston/-/issues/743Unable to fork repository due to max limit reached2023-04-19T08:15:39ZAshwin PrabhakarUnable to fork repository due to max limit reachedHi, I am trying to fork the weston repository. I have the fork button greyed out with "You have reached your project limit". I would appreciate if someone can help me with the access.Hi, I am trying to fork the weston repository. I have the fork button greyed out with "You have reached your project limit". I would appreciate if someone can help me with the access.https://gitlab.freedesktop.org/wayland/weston/-/issues/742Incorrect mapping of Windows keyboard layout "KBD_CZECH_PROGRAMMERS"2023-04-18T09:02:10Zcarlos-h-hIncorrect mapping of Windows keyboard layout "KBD_CZECH_PROGRAMMERS"In `libweston/backend-rdp/rdp.c`, the Windows keyboard layout `KBD_CZECH_PROGRAMMERS` is mapped to `cz(bksl)`.
This is incorrect, since the Czech Programmers layout is the US layout with accessing the Czech symbols by pressing Right-Alt...In `libweston/backend-rdp/rdp.c`, the Windows keyboard layout `KBD_CZECH_PROGRAMMERS` is mapped to `cz(bksl)`.
This is incorrect, since the Czech Programmers layout is the US layout with accessing the Czech symbols by pressing Right-Alt.
The correct XKB equivalent for it is: layout: `us,cz`, no variants, option: `grp:switch`.https://gitlab.freedesktop.org/wayland/weston/-/issues/741Tablet input should be associated with tablet output for tablets with an inte...2023-04-18T07:44:10ZLink MauveTablet input should be associated with tablet output for tablets with an integrated screenI am testing the now-merged !546 on a Wacom Cintiq 21UX, and Weston doesn’t puts the tablet pointer on the expected (secondary) output, when the main output is my laptop’s screen.
Mutter/gnome-shell does the correct mapping, but I have ...I am testing the now-merged !546 on a Wacom Cintiq 21UX, and Weston doesn’t puts the tablet pointer on the expected (secondary) output, when the main output is my laptop’s screen.
Mutter/gnome-shell does the correct mapping, but I have no idea how this association is described by the kernel.
Ping @mol.https://gitlab.freedesktop.org/wayland/weston/-/issues/740Assert when pressing the power button of a screen2023-06-13T16:35:18ZLink MauveAssert when pressing the power button of a screenWhen pressing the power button of a screen, it triggered an assert with this stack trace, but I couldn’t reproduce afterwards:
```rust
(gdb) bt
#0 0x00007f1f367e88ec in () at /usr/lib/libc.so.6
#1 0x00007f1f36799ea8 in raise () at /us...When pressing the power button of a screen, it triggered an assert with this stack trace, but I couldn’t reproduce afterwards:
```rust
(gdb) bt
#0 0x00007f1f367e88ec in () at /usr/lib/libc.so.6
#1 0x00007f1f36799ea8 in raise () at /usr/lib/libc.so.6
#2 0x00007f1f3678353d in abort () at /usr/lib/libc.so.6
#3 0x00007f1f3678345c in () at /usr/lib/libc.so.6
#4 0x00007f1f367929f6 in () at /usr/lib/libc.so.6
#5 0x00007f1f367158ba in weston_coord_surface_to_global (view=0xcd2a9, view@entry=0x5603ba01e710, coord=...) at ../libweston/compositor.c:722
#6 0x00007f1f305281a6 in get_panel_size (shell=0x5603ba0630a0, height=<synthetic pointer>, width=<synthetic pointer>, view=0x5603ba01e710) at ../desktop-shell/shell.c:340
#7 get_output_panel_size (height=<synthetic pointer>, width=<synthetic pointer>, output=0x5603b97a1e50, shell=0x5603ba0630a0) at ../desktop-shell/shell.c:368
#8 get_output_work_area (shell=0x5603ba0630a0, output=0x5603b97a1e50, area=area@entry=0x7ffcb6fb8ff0) at ../desktop-shell/shell.c:395
#9 0x00007f1f305296eb in get_maximized_size (height=<synthetic pointer>, width=<synthetic pointer>, shsurf=0x5603b9fbe530) at ../desktop-shell/shell.c:2506
#10 set_fullscreen (shsurf=0x5603b9fbe530, fullscreen=<optimized out>, output=0x0) at ../desktop-shell/shell.c:2539
#11 0x00007f1f3052d858 in shell_reposition_view_on_output_change (view=0x5603b9fa4bd0) at ../desktop-shell/shell.c:4678
#12 shell_output_changed_move_layer (shell=<optimized out>, layer=0x5603ba063388, data=<optimized out>) at ../desktop-shell/shell.c:4701
#13 0x00007f1f3052d8d2 in shell_for_each_layer (func=0x7f1f3052d6f0 <shell_output_changed_move_layer>, data=0x0, shell=0x5603ba0630a0) at ../desktop-shell/shell.c:4689
#14 shell_output_destroy (shell_output=0x5603ba05f6e0) at ../desktop-shell/shell.c:4710
#15 0x00007f1f3671c5fe in weston_signal_emit_mutable (data=0x5603b97a2f70, signal=0x5603b97a30c0) at ../shared/signal.c:52
#16 weston_compositor_remove_output (output=0x5603b97a2f70) at ../libweston/compositor.c:6778
#17 0x00007f1f3671c760 in weston_output_disable () at ../libweston/compositor.c:6787
#18 0x00005603ba0605d0 in ()
#19 0x00007f1f3698b28e in drm_head_disable (head=0x5603b97a2f70) at ../compositor/main.c:2564
#20 drm_heads_changed (listener=<optimized out>, arg=0x5603b9793fd0) at ../compositor/main.c:2592
#21 0x00007f1f3670f2b1 in wl_signal_emit (data=0xcd2a9, signal=0x5603b97943f8) at /usr/include/wayland-server-core.h:491
#22 weston_compositor_call_heads_changed (data=0xcd2a9) at ../libweston/compositor.c:5596
#23 0x00007f1f366dca63 in wl_event_loop_dispatch_idle (loop=loop@entry=0x5603b9791c30) at ../wayland/src/event-loop.c:969
#24 0x00007f1f366dcb74 in wl_event_loop_dispatch (loop=0x5603b9791c30, timeout=timeout@entry=-1) at ../wayland/src/event-loop.c:1032
#25 0x00007f1f366d9e67 in wl_display_run (display=0x5603b9791b40) at ../wayland/src/wayland-server.c:1471
#26 0x00007f1f3698fc37 in execute_autolaunch (config=0x5603b9791e10, wet=0x7ffcb6fb9640) at ../compositor/main.c:3692
#27 wet_main (argc=<optimized out>, argv=<optimized out>, test_data=0x0) at ../compositor/main.c:4077
#28 0x00007f1f36784790 in () at /usr/lib/libc.so.6
#29 0x00007f1f3678484a in __libc_start_main () at /usr/lib/libc.so.6
#30 0x00005603b962f055 in _start ()
```https://gitlab.freedesktop.org/wayland/weston/-/issues/739Test-failures on big-endian architectures2023-04-17T14:17:43Zmatoro1Test-failures on big-endian architecturesHi, I am observing a specific subset of tests which fail with assertion failures on all big-endian architectures. There are additional failures on some specific architectures, but all big-endian arches have this subset of failures in co...Hi, I am observing a specific subset of tests which fail with assertion failures on all big-endian architectures. There are additional failures on some specific architectures, but all big-endian arches have this subset of failures in common:
```
Summary of Failures:
5/41 alpha-blending ERROR 3.10s killed by signal 6 SIGABRT
6/41 buffer-transforms ERROR 3.79s killed by signal 6 SIGABRT
13/41 output-transforms ERROR 0.19s killed by signal 6 SIGABRT
15/41 internal-screenshot ERROR 0.57s killed by signal 6 SIGABRT
16/41 output-damage ERROR 0.37s killed by signal 6 SIGABRT
18/41 pointer-shot ERROR 0.28s killed by signal 6 SIGABRT
19/41 single-pixel-buffer ERROR 0.21s killed by signal 6 SIGABRT
27/41 viewporter-shot ERROR 0.24s killed by signal 6 SIGABRT
32/41 yuv-buffer ERROR 0.59s killed by signal 6 SIGABRT
39/41 subsurface-shot ERROR 1.98s killed by signal 6 SIGABRT
40/41 color-icc-output ERROR 0.67s killed by signal 6 SIGABRT
Ok: 29
Expected Fail: 0
Fail: 11
Unexpected Pass: 0
Skipped: 1
Timeout: 0
```
I confirmed this on ppc64 BE and mips64 BE, both had identical failures, here is a sample log from the former: [testlog.txt](/uploads/ebdd9d34fb6fdf4a042b09a6fa409c72/testlog.txt)
This can be cross-referenced with Debian CI. Although note that Debian has 11.0.0 in experimental, and it is showing a segfault in the `xwayland` test that I do not see, so feel free to ignore that one.
s390x: https://buildd.debian.org/status/fetch.php?pkg=weston&arch=s390x&ver=11.0.0-2&stamp=1674156095&raw=1
```
Summary of Failures:
2/45 alpha-blending ERROR 0.05s killed by signal 6 SIGABRT
4/45 buffer-transforms ERROR 0.07s killed by signal 6 SIGABRT
10/45 internal-screenshot ERROR 0.07s killed by signal 6 SIGABRT
14/45 output-damage ERROR 0.09s killed by signal 6 SIGABRT
15/45 output-transforms ERROR 0.06s killed by signal 6 SIGABRT
18/45 pointer-shot ERROR 0.06s killed by signal 6 SIGABRT
23/45 single-pixel-buffer ERROR 0.06s killed by signal 6 SIGABRT
24/45 subsurface-shot ERROR 0.35s killed by signal 6 SIGABRT
30/45 viewporter-shot ERROR 0.06s killed by signal 6 SIGABRT
31/45 yuv-buffer ERROR 0.18s killed by signal 6 SIGABRT
35/45 color-icc-output ERROR 0.36s killed by signal 6 SIGABRT
38/45 xwayland ERROR 0.02s killed by signal 11 SIGSEGV
Ok: 32
Expected Fail: 0
Fail: 12
Unexpected Pass: 0
Skipped: 1
Timeout: 0
```
hppa: https://buildd.debian.org/status/fetch.php?pkg=weston&arch=hppa&ver=11.0.0-2&stamp=1674158398&raw=1
```
Summary of Failures:
2/45 alpha-blending ERROR 0.70s killed by signal 6 SIGABRT
6/45 buffer-transforms ERROR 1.36s killed by signal 6 SIGABRT
11/45 internal-screenshot ERROR 1.71s killed by signal 6 SIGABRT
14/45 output-transforms ERROR 0.82s killed by signal 6 SIGABRT
17/45 output-damage ERROR 1.67s killed by signal 6 SIGABRT
21/45 pointer-shot ERROR 1.91s killed by signal 6 SIGABRT
23/45 single-pixel-buffer ERROR 1.75s killed by signal 6 SIGABRT
28/45 viewporter-shot ERROR 1.38s killed by signal 6 SIGABRT
29/45 subsurface-shot ERROR 4.85s killed by signal 6 SIGABRT
35/45 yuv-buffer ERROR 8.95s killed by signal 6 SIGABRT
36/45 color-icc-output ERROR 7.72s killed by signal 6 SIGABRT
38/45 xwayland ERROR 0.90s killed by signal 11 SIGSEGV
Ok: 32
Expected Fail: 0
Fail: 12
Unexpected Pass: 0
Skipped: 1
Timeout: 0
```
powerpc: https://buildd.debian.org/status/fetch.php?pkg=weston&arch=powerpc&ver=11.0.0-2&stamp=1674157443&raw=1
```
Summary of Failures:
5/45 alpha-blending ERROR 0.06s killed by signal 6 SIGABRT
6/45 buffer-transforms ERROR 0.07s killed by signal 6 SIGABRT
10/45 internal-screenshot ERROR 0.20s killed by signal 6 SIGABRT
13/45 output-damage ERROR 0.20s killed by signal 6 SIGABRT
14/45 output-transforms ERROR 0.19s killed by signal 6 SIGABRT
16/45 pointer-shot ERROR 0.18s killed by signal 6 SIGABRT
19/45 single-pixel-buffer ERROR 0.18s killed by signal 6 SIGABRT
25/45 viewporter-shot ERROR 0.14s killed by signal 6 SIGABRT
29/45 xwayland ERROR 0.08s killed by signal 11 SIGSEGV
34/45 yuv-buffer ERROR 0.17s killed by signal 6 SIGABRT
41/45 subsurface-shot ERROR 0.37s killed by signal 6 SIGABRT
43/45 color-icc-output ERROR 0.57s killed by signal 6 SIGABRT
Ok: 17
Expected Fail: 0
Fail: 12
Unexpected Pass: 0
Skipped: 16
Timeout: 0
```
sparc64: https://buildd.debian.org/status/fetch.php?pkg=weston&arch=sparc64&ver=11.0.0-2&stamp=1674157483&raw=1
```
Summary of Failures:
4/45 alpha-blending ERROR 0.10s killed by signal 6 SIGABRT
5/45 buffer-transforms ERROR 0.11s killed by signal 6 SIGABRT
7/45 color-manager ERROR 0.30s killed by signal 10 SIGBUS
11/45 internal-screenshot ERROR 0.50s killed by signal 6 SIGABRT
14/45 output-damage ERROR 0.46s killed by signal 6 SIGABRT
15/45 output-transforms ERROR 0.45s killed by signal 6 SIGABRT
17/45 pointer-shot ERROR 0.42s killed by signal 6 SIGABRT
20/45 single-pixel-buffer ERROR 0.39s killed by signal 6 SIGABRT
26/45 viewporter-shot ERROR 0.29s killed by signal 6 SIGABRT
30/45 xwayland ERROR 0.20s killed by signal 11 SIGSEGV
34/45 color-metadata-parsing ERROR 0.25s killed by signal 10 SIGBUS
35/45 yuv-buffer ERROR 0.37s killed by signal 10 SIGBUS
41/45 subsurface-shot ERROR 0.50s killed by signal 6 SIGABRT
42/45 color-icc-output ERROR 0.31s killed by signal 10 SIGBUS
Ok: 13
Expected Fail: 0
Fail: 14
Unexpected Pass: 0
Skipped: 18
Timeout: 0
```
As you can see we have a specific subset of 11 tests that fail on all big-endian platforms (none of these tests have assertion failures on LE platforms, including ppc64le where all tests pass for me). sparc has additional issues (the SIGBUS tests) due to its strict alignment requirements, but is otherwise identical to all other BE platforms.
Is there any way these assertion failures could be looked at for users of BE platforms? Thanks!https://gitlab.freedesktop.org/wayland/weston/-/issues/738Kiosk-shell keyboard focus lost after modal dialogs2023-07-27T09:12:39ZFredrik GustafssonKiosk-shell keyboard focus lost after modal dialogsWeston 11.0.1
Open a modal dialog in the Weston kiosk shell close the dialog via keyboard actions. I.e. in a simple default "Ok" button scenario just press enter to close the dialog. After close the keyboard focus is lost and continued n...Weston 11.0.1
Open a modal dialog in the Weston kiosk shell close the dialog via keyboard actions. I.e. in a simple default "Ok" button scenario just press enter to close the dialog. After close the keyboard focus is lost and continued navigation via keyboard is not possible. Clicking with the mouse restores the keyboard focus.
The issue does not reproduce with desktop-shell.https://gitlab.freedesktop.org/wayland/weston/-/issues/737QT Modal windows issus2023-04-26T02:21:18ZNoah-LijcQT Modal windows issusMy current version of Weston is 10.0, but due to stability issues, I cannot upgrade it. However, when using QT, I found that a bug from Weston 9.0 has been fixed. This bug prevented the use of modal windows, but now after commit (a8da208...My current version of Weston is 10.0, but due to stability issues, I cannot upgrade it. However, when using QT, I found that a bug from Weston 9.0 has been fixed. This bug prevented the use of modal windows, but now after commit (a8da208453ccc748bf331e83956b85d43ef0f05f), modal windows can be used again. However, after closing a modal window and clicking on the main window, Weston crashes and commit (5699dbaae7df083e1f34ca88c37f21db669495b0) did not fix this crash bug(The Wayland connection broke. Did the Wayland compositor die?).
May I ask if this problem can be solved? Or is it the case that this issue has already been fixed in Weston 11.0? Can you provide the corresponding commit? Looking forward to your reply.https://gitlab.freedesktop.org/wayland/weston/-/issues/73611.0.0 Weston screen sharing in embedded environment is very laggy with 100% ...2023-12-05T11:22:38Zbot crack11.0.0 Weston screen sharing in embedded environment is very laggy with 100% CPU usageHello,
I have been experiencing a very laggy screen sharing while using Weston 11.0.0 in my embedded environment. The CPU usage also reaches up to 100%. I am using an ARM Cortex-A55 1.5GHz processor and 2GB DDR RAM.
I have performed VN...Hello,
I have been experiencing a very laggy screen sharing while using Weston 11.0.0 in my embedded environment. The CPU usage also reaches up to 100%. I am using an ARM Cortex-A55 1.5GHz processor and 2GB DDR RAM.
I have performed VNC and RDP tests and have configured them in the weston.ini file as follows:
[screen-share]
command=/usr/bin/weston --backend=vnc-backend.so --shell=fullscreen-shell.so
or
[screen-share]
command=/usr/bin/weston --backend=rdp-backend.so --shell=fullscreen-shell.so --no-clients-resize --rdp-tls-cert=/etc/freerdp/keys/server.crt --rdp-tls-key=/etc/freerdp/keys/server.key
To start the screen sharing, I used the following command:
1. weston --backend=drm-backend.so --modules=screen-share.so
2. Press Ctrl + Alt + S to activate the screen sharing. However, the screen becomes very laggy at this point and CPU usage reaches 100%.
Can you please assist me with resolving this issue in my embedded environment?
Thank you.https://gitlab.freedesktop.org/wayland/weston/-/issues/735weston-terminal doesn't display correct Chinese characters with font alias2023-04-09T05:37:05ZYang Hongweston-terminal doesn't display correct Chinese characters with font aliasweston-terminal doesn't display Chinese characters with font alias (monospace), but other application like pango-view,foot could works.
I uses weston 11.0.1 in Archlinux with WSL2
```
[terminal]
font=monospace
font-size=14
```
![weston-...weston-terminal doesn't display Chinese characters with font alias (monospace), but other application like pango-view,foot could works.
I uses weston 11.0.1 in Archlinux with WSL2
```
[terminal]
font=monospace
font-size=14
```
![weston-terminal](/uploads/a6ea0285dccfc3dcb5af117d4a66cb01/weston-terminal.png)
![pango](/uploads/f1ba6f097847604a256006d64dcbb3a3/pango.png)
![wsl](/uploads/f9b387a58a24b787efe08ebc8e7b0b79/wsl.png)
![weston](/uploads/5247f514e478f38856c8f2a3e3feacb8/weston.png)https://gitlab.freedesktop.org/wayland/weston/-/issues/734Test ORIGIN_BOTTOM_LEFT buffer composition2023-04-05T12:27:24ZPekka Paalanenppaalanen@gmail.comTest ORIGIN_BOTTOM_LEFT buffer compositionI don't think we have any test in the test suite that would reliably exercise `ORIGIN_BOTTOM_LEFT` buffers. We should have one that applies to both GL and Pixman renderers.
Only dmabuf buffers could end up with `ORIGIN_BOTTOM_LEFT` via ...I don't think we have any test in the test suite that would reliably exercise `ORIGIN_BOTTOM_LEFT` buffers. We should have one that applies to both GL and Pixman renderers.
Only dmabuf buffers could end up with `ORIGIN_BOTTOM_LEFT` via `ZWP_LINUX_BUFFER_PARAMS_V1_FLAGS_Y_INVERT`, and people have been keen on deleting any use of that flag. Only `simple-dmabuf-v4l` might use it if the V4L2 device indicates so. But dmabuf does not apply with Pixman renderer.
With `wl_shm`, we have no protocol to indicate bottom-left origin, so a test will need to quirk that somehow.
Pixman-renderer never even checks `buffer_origin`, but it has not needed to, because it cannot get bottom-left origin buffers.
Neither does DRM-backend check `buffer_origin` when driving KMS, and theoretically that is a reachable bug.
GL-renderer has code to handle `buffer_origin`.