weston issueshttps://gitlab.freedesktop.org/wayland/weston/-/issues2022-01-07T20:16:13Zhttps://gitlab.freedesktop.org/wayland/weston/-/issues/576Required order when emitting globals2022-01-07T20:16:13ZJulian OrthRequired order when emitting globalsWhen globals are emitted from a registry, is there a required order in which they are emitted? I could not find anything like that in the spec but the weston example clients segfault when a wl_seat is emitted before a wl_compositor.When globals are emitted from a registry, is there a required order in which they are emitted? I could not find anything like that in the spec but the weston example clients segfault when a wl_seat is emitted before a wl_compositor.https://gitlab.freedesktop.org/wayland/weston/-/issues/575ibus-pinyin not work when run wps in weston with xwayland2021-12-27T07:09:01ZVollyBirdibus-pinyin not work when run wps in weston with xwaylandHi,guys
I compile and run the weston-10 on Ubuntu 20.04. My weston run commond is:
`weston --xwayland --logger-scopes=log,x11-backend,desktop-shell,xwm-wm-x11`
I have alse installed [wps](https://www.wps.com/office/linux/) on my Ubun...Hi,guys
I compile and run the weston-10 on Ubuntu 20.04. My weston run commond is:
`weston --xwayland --logger-scopes=log,x11-backend,desktop-shell,xwm-wm-x11`
I have alse installed [wps](https://www.wps.com/office/linux/) on my Ubuntu.
I run wps through weston shell commond, but I can't use ibus-pinyin in wps.
![image](/uploads/1e2c1c500d07de590330663e324ae348/image.png)
Due to some format problem, I attach the weston log and weston.ini file, please check.
[weston.ini](/uploads/b80531c331cb5cdb21b18c241ed1c9c7/weston.ini)
[weston.log](/uploads/c6d56b209abde2f1af36a6bccab31983/weston.log)
If I run wps directly(without weston), ibus-pinyin woks fine.
If I run wps through weston shell commond and replace ibus to fcitx5, fcitx5 works fine too.
So, I want to find how to solve this problem, please help me. Thanks a lot!https://gitlab.freedesktop.org/wayland/weston/-/issues/574Implement primary selection protocol2021-12-23T17:57:45ZMax IhlenfeldtImplement primary selection protocolWeston currently does not implement the (admittedly unstable) primary selection protocol. It would be nice if it did :)Weston currently does not implement the (admittedly unstable) primary selection protocol. It would be nice if it did :)https://gitlab.freedesktop.org/wayland/weston/-/issues/573weston_test.move_pointer() sends wl_pointer.motion() event during DnD session2022-04-11T21:48:06ZMax Ihlenfeldtweston_test.move_pointer() sends wl_pointer.motion() event during DnD sessionChromium uses `weston_test` for its automated Wayland tests. During my work on these tests, I noticed that a `weston_test.move_pointer()` request during an active drag and drop session leads to a `wl_pointer.motion` event, and not a `wl_...Chromium uses `weston_test` for its automated Wayland tests. During my work on these tests, I noticed that a `weston_test.move_pointer()` request during an active drag and drop session leads to a `wl_pointer.motion` event, and not a `wl_data_device.motion` event.
If I understand correctly, the `weston_test` interface is not really meant to be used by something other than `weston`'s own tests. But it would be great if this could be fixed nonetheless, as Chromium's Wayland testing would not be possible without `weston_test`.https://gitlab.freedesktop.org/wayland/weston/-/issues/572"require-input" config parameter ignored when using backend-drm2022-01-10T16:32:24ZKenneth Sloat"require-input" config parameter ignored when using backend-drmIn cases where the DRM system is used, a flag was introduced in e57d8ae818c39fc434fcf3bfc97274195296c8d6 called "continue-without-input" that allows the system to run without an input device attached. This can be passed as a arg to westo...In cases where the DRM system is used, a flag was introduced in e57d8ae818c39fc434fcf3bfc97274195296c8d6 called "continue-without-input" that allows the system to run without an input device attached. This can be passed as a arg to weston. There already exists a current and older method to achieve the same via the configuration file using a parameter called "require-input."
The introduction of "continue-without-input" seems to render "require-input" moot since it takes precedence. It seems the former was introduced for test purposes, perhaps without realizing the impact this could have where users are relying on the latter config file param. I do not know the history here, so I wanted to open this for discussion.
I found this in version 9.0 when upgrading from 5.0 running on an embedded Linux system with a DRM back-end.https://gitlab.freedesktop.org/wayland/weston/-/issues/571It's not possible to interact with chromium windows using screen-share2023-11-23T09:16:14ZNicolò OngaroIt's not possible to interact with chromium windows using screen-shareI've tested weston screen share with the rdp backend and with the vnc backend.
It looks like it's working fine except when running chromium. I can interact with chromium using the touchscreen but not from the rdp/vnc client. While chromi...I've tested weston screen share with the rdp backend and with the vnc backend.
It looks like it's working fine except when running chromium. I can interact with chromium using the touchscreen but not from the rdp/vnc client. While chromium is running i can still click outside the window or on other windows.https://gitlab.freedesktop.org/wayland/weston/-/issues/569application get first touch event while the screen is locked2024-02-29T14:41:43Zekapllajapplication get first touch event while the screen is lockedWhen using the screensaver on wayland, the screen fades out but all applications are still there and can get the first click/touch on the display. After the first click, the "Ulock your Desktop" gui is rendered, and from this moment all ...When using the screensaver on wayland, the screen fades out but all applications are still there and can get the first click/touch on the display. After the first click, the "Ulock your Desktop" gui is rendered, and from this moment all events are intercepted by the unlock window.
I just commented the line which turns off the backlight on _weston_compositor_sleep()_ and found out all layers are still there also when the screen is locked.
This is a picture describing the issue. The upper image is made when the screen is locked, then touching on the text input field, the Unlock image is displayed (middle image) and after touching on the green ball, the screen unlocks, and we can see the input field is selected and the keyboard is up.
![weston-screensaver](/uploads/d1dcac16dc09f725b527482f9d49cfc6/weston-screensaver.jpg)
The same issue can be verified also with the screen locked, if we touch on the terminal icon (top left corner), when the screen is unlocked, we can see the terminal is opened.
Debugging the screen locking mechanism (function _lock()_ on _shell.c_ file), _panel_layer_, _fullscreen_layer_, _input_panel_layer_ and _layer_ are hidden, the _lock_layer_ is set, and then the _weston_compositor_sleep()_ is called, which puts the compositor on the sleep status.
From what I sow, none of the previous functions takes effect until the next repaint, which doesn't occur because now the _compositor->state = WESTON_COMPOSITOR_SLEEPING_ is set.
I found a solution to this problem by patching _weston_output_maybe_repaint()_ to consider also this case (compositor on sleep status but _repaint_needed_).
With this patch, everything on screen is hidden, and I have no unwanted clicks/touches propagated into the applications after screen unlock.
I don't know if this is the correct solution, but I'm going to create a pull request and maybe we can discuss about it.https://gitlab.freedesktop.org/wayland/weston/-/issues/568weston_paint_node_ensure_color_transform: Assertion 'it->surf_xform_valid == ...2022-01-25T13:49:44ZAlexandros Frantzisweston_paint_node_ensure_color_transform: Assertion 'it->surf_xform_valid == false' failedI am seeing a crash with: `weston: ../libweston/color.c:217: weston_paint_node_ensure_color_transform: Assertion 'it->surf_xform_valid == false' failed`.
I have seen this happen consistently when trying to make Chrome running under Wine...I am seeing a crash with: `weston: ../libweston/color.c:217: weston_paint_node_ensure_color_transform: Assertion 'it->surf_xform_valid == false' failed`.
I have seen this happen consistently when trying to make Chrome running under Wine-Wayland fullscreen. It's not trivial to set this up, so I hope the attached information will be enough to resolve this. If not, I am happy to provide further instructions.
The attached log of weston is captured with WAYLAND_DEBUG, including the crash and backtrace at the end: [crash-ensure-color-transform.txt](/uploads/a15e4ab65f13bb563fee70731538cd62/crash-ensure-color-transform.txt)Pekka Paalanenppaalanen@gmail.comPekka Paalanenppaalanen@gmail.comhttps://gitlab.freedesktop.org/wayland/weston/-/issues/567How to enable the screenshooter in kiosk-shell2021-11-27T10:18:32ZMihai OlteanuHow to enable the screenshooter in kiosk-shellI've recently switched from desktop-shell to kiosk-shell and noticed the keybindings, and especially the screenshot feature, don't work anymore.
Looking at the source code, [kiosk-shell.c](https://gitlab.freedesktop.org/wayland/weston/-...I've recently switched from desktop-shell to kiosk-shell and noticed the keybindings, and especially the screenshot feature, don't work anymore.
Looking at the source code, [kiosk-shell.c](https://gitlab.freedesktop.org/wayland/weston/-/blob/main/kiosk-shell/kiosk-shell.c#L998) is indeed missing most of the keybindings that are available in [shell.c](https://gitlab.freedesktop.org/wayland/weston/-/blob/main/desktop-shell/shell.c#L4961), so this is to be expected.
But both the kiosk and the desktop call the [screenshooter_create](https://gitlab.freedesktop.org/wayland/weston/-/blob/main/compositor/weston-screenshooter.c#L180) as part of their init process ([here](https://gitlab.freedesktop.org/wayland/weston/-/blob/main/kiosk-shell/kiosk-shell.c#L1174) for kiosk, and [here](https://gitlab.freedesktop.org/wayland/weston/-/blob/main/desktop-shell/shell.c#L5173) for desktop), which contains the needed keybindings for screenshoting and recording. Just reading the code would lead one to believe these features are thus available in kiosk, as well, but trying them out leaves me with no screenshot actually taken. I can successfully take a screenshot in desktop-shell, though.
I've also tried [weston-binder](https://github.com/tarvi-verro/weston-binder) in kiosk and defined a key to call the /bin/weston-screenshooter directly and redirecting the stderr to a tmp file. I get a `display doesn't support screenshooter` error. Weston was started with "--debug" in this case, since without it I get a `error 0: screenshooter failed: permission denied. Debug protocol must be enabled` from /bin/weston-screenshooter.
I would still like to retain the possibility of taking screenshots in kiosk-shell, as well. Can you guide me on how would one achieve that, either with a keybinding or with calling weston-screenshooter directly, an external tool or with patching the source code and rebuilding?https://gitlab.freedesktop.org/wayland/weston/-/issues/566Demote weston-terminal to a demo or remove it2022-01-10T20:59:57ZSimon Sercontact@emersion.frDemote weston-terminal to a demo or remove itI'm not sure it's a good idea for the Weston project to maintain a fully-fledged terminal emulator. I think it would be better to keep it as a demo instead. That way users can lower their expectations in terms of support and feature requ...I'm not sure it's a good idea for the Weston project to maintain a fully-fledged terminal emulator. I think it would be better to keep it as a demo instead. That way users can lower their expectations in terms of support and feature requests.
Potential action items:
- Clearly label it as a demo in the README
- Move it from the Meson option `tools` to `demo-clients`
- Don't install it by defaulthttps://gitlab.freedesktop.org/wayland/weston/-/issues/565Super+R screen capture should be an option2021-11-19T12:03:55ZTestMode1Super+R screen capture should be an optionThere should be an option to disable below in meson_options.txt as it is very easy to accidentally hit Super+R leading to OOM, slowdowns or hangs.
```c
weston_compositor_add_key_binding(ec, KEY_R, MODIFIER_SUPER,
recorder_binding...There should be an option to disable below in meson_options.txt as it is very easy to accidentally hit Super+R leading to OOM, slowdowns or hangs.
```c
weston_compositor_add_key_binding(ec, KEY_R, MODIFIER_SUPER,
recorder_binding, shooter);
```https://gitlab.freedesktop.org/wayland/weston/-/issues/564"static_assert" macro in helpers.h2021-11-16T20:40:04Zca lee"static_assert" macro in helpers.hIn shared\helpers.h, it defines a "static_assert" macro, which is different with macro in c++. When I develop a client in c++, and include \<map\> after "helpers.h", it will report an weird error shows:
```
uses_allocator.h:93: error: ma...In shared\helpers.h, it defines a "static_assert" macro, which is different with macro in c++. When I develop a client in c++, and include \<map\> after "helpers.h", it will report an weird error shows:
```
uses_allocator.h:93: error: macro "static_assert" passed 8 arguments, but takes just 2
" an allocator must be possible if uses_allocator is true");
```
source code is:
```cpp
static_assert(__or_<
is_constructible<_Tp, allocator_arg_t, _Alloc, _Args...>,
is_constructible<_Tp, _Args..., _Alloc>>::value, "construction with"
" an allocator must be possible if uses_allocator is true");
```
It looks like preprocessor can't distinguish comma in template or in args. What I can do now is leaving "helpers.h" behind every other headers. So I wanna know if there is other way to work around this problem, or we can change the macro in "helpers.h"?https://gitlab.freedesktop.org/wayland/weston/-/issues/563Weston X11 crash when image is copied to clipboard2021-11-11T15:18:53Zrichkiz devopserWeston X11 crash when image is copied to clipboardWindows 11 standard installation.
WSL Ubuntu 20.04.
Running any GUI app.
Copying any image data to clipboard, taking screenshot to clipboard -> X11 crashes.
X11 keeps crashing while image data still in the clipboard memory. Copying any a...Windows 11 standard installation.
WSL Ubuntu 20.04.
Running any GUI app.
Copying any image data to clipboard, taking screenshot to clipboard -> X11 crashes.
X11 keeps crashing while image data still in the clipboard memory. Copying any amount of text allows GUI apps to start again.
Pardon me if this report does not confirm to standards.
I am not the developer, just wanted to document is as clearly as my competence allows.
Attaching weston.log and dmesg.log
[weston.log](/uploads/3ca9497afe465c6936f02aad4f9be857/weston.log)
[dmesg.log](/uploads/b69932d415dee2644ef2f2db24ee1476/dmesg.log)https://gitlab.freedesktop.org/wayland/weston/-/issues/562XDG_RUNTIME_DIR is not set in arm device(weston run failure in arm device)2021-11-10T15:03:48Zsss qaXDG_RUNTIME_DIR is not set in arm device(weston run failure in arm device)I have cross compiled the wayland and weston for arm device with meson build system.I have faced below error while run the weston in arm device.
>>> weston
**fatal: environment variable XDG_RUNTIME_DIR is not set.**
Kindly support fo...I have cross compiled the wayland and weston for arm device with meson build system.I have faced below error while run the weston in arm device.
>>> weston
**fatal: environment variable XDG_RUNTIME_DIR is not set.**
Kindly support for run weston on non x11 window system. Need to run weston in frame buffer environment.https://gitlab.freedesktop.org/wayland/weston/-/issues/560Crash on rdp-backend from/by using Windows 10 rdp client2023-11-24T09:35:47ZVyacheslav YurkovCrash on rdp-backend from/by using Windows 10 rdp clientI have pretty recent build of weston from main branch, which I start with rdp backend:
`/usr/bin/weston --backend=rdp-backend.so --rdp-tls-cert tls.crt --rdp-tls-key tls.key` on arm64 board.
I connect to it with Remote Desktop from a Wi...I have pretty recent build of weston from main branch, which I start with rdp backend:
`/usr/bin/weston --backend=rdp-backend.so --rdp-tls-cert tls.crt --rdp-tls-key tls.key` on arm64 board.
I connect to it with Remote Desktop from a Win10 machine. The first connection usually succeeds. But when I close the connection _and_ do not close the Remote Desktop application, but try to reconnect right away I get one of the following:
- either it's https://gitlab.freedesktop.org/wayland/weston/-/issues/509 and connection can't be established;
- or weston crashes. I've got a stacktrace for the crash
```
#0 0x0000ffff812935c4 in notify_motion_absolute (seat=0x0, time=time@entry=0xffffca045d00, x=x@entry=1070, y=y@entry=597) at ../git/libweston/input.c:1837
#1 0x0000ffff80a4ccc0 in xf_mouseEvent (input=<optimized out>, flags=<optimized out>, x=<optimized out>, y=597) at ../git/libweston/backend-rdp/rdp.c:1039
#2 0x0000ffff80937e3c in ?? () from /usr/lib/libweston-10/../libfreerdp2.so.2
#3 0x0000ffff8094af04 in ?? () from /usr/lib/libweston-10/../libfreerdp2.so.2
#4 0x0000ffff8094b7e0 in ?? () from /usr/lib/libweston-10/../libfreerdp2.so.2
#5 0x0000ffff8093afe0 in ?? () from /usr/lib/libweston-10/../libfreerdp2.so.2
#6 0x0000ffff809325e4 in ?? () from /usr/lib/libweston-10/../libfreerdp2.so.2
#7 0x0000ffff8094a524 in ?? () from /usr/lib/libweston-10/../libfreerdp2.so.2
#8 0x0000ffff80a4ce1c in rdp_client_activity (fd=<optimized out>, mask=<optimized out>, data=0xaaaac2f76ff0) at ../git/libweston/backend-rdp/rdp.c:734
#9 0x0000ffff81230e18 in wl_event_loop_dispatch () from /usr/lib/libwayland-server.so.0
#10 0x0000ffff8122e73c in wl_display_run () from /usr/lib/libwayland-server.so.0
#11 0x0000ffff8144290c in wet_main (argc=<optimized out>, argv=0xffffca046958, test_data=<optimized out>) at ../git/compositor/main.c:3506
#12 0x0000ffff812e6994 in __libc_start_main () from /lib/libc.so.6
#13 0x0000aaaabbb1a738 in _start () at ../sysdeps/aarch64/start.S:91
```
It seems to be a null pointer dereference. If you have any ideas what could be the reason, I could look into it further and fix it probably.https://gitlab.freedesktop.org/wayland/weston/-/issues/559Missing mouse support in weston-terminal2022-01-10T20:27:51ZDemi Marie Obenourdemiobenour@gmail.comMissing mouse support in weston-terminalweston-terminal doesn’t have mouse support.weston-terminal doesn’t have mouse support.https://gitlab.freedesktop.org/wayland/weston/-/issues/558Missing escape sequences in weston-terminal2022-01-10T20:27:49ZDemi Marie Obenourdemiobenour@gmail.comMissing escape sequences in weston-terminalweston-terminal is missing support for some escape sequences used by Vim.weston-terminal is missing support for some escape sequences used by Vim.https://gitlab.freedesktop.org/wayland/weston/-/issues/557Provide a comparison of libweston and wlroots2022-01-10T20:05:59ZDemi Marie Obenourdemiobenour@gmail.comProvide a comparison of libweston and wlrootslibweston seems to be little-used in desktops nowadays, with most compositors using wlroots or implementing everything themselves. It would be nice to have a comparison of libweston and wlroots, so that compositor authors could determin...libweston seems to be little-used in desktops nowadays, with most compositors using wlroots or implementing everything themselves. It would be nice to have a comparison of libweston and wlroots, so that compositor authors could determine which is more suitable for them.https://gitlab.freedesktop.org/wayland/weston/-/issues/556Rotary encoder Knobe (Joystick) with Wayland-EGL platform not working2021-11-07T23:12:47ZHitesh ViradiyaRotary encoder Knobe (Joystick) with Wayland-EGL platform not workingI am facing same issue with rotary encoder knobe with imx6 platform. We are using wayland-egl and weston compositor and we are not getting events in GUI.
We have browser application which receives events. If we change QT QPA PLATFORM to...I am facing same issue with rotary encoder knobe with imx6 platform. We are using wayland-egl and weston compositor and we are not getting events in GUI.
We have browser application which receives events. If we change QT QPA PLATFORM to linuxfb everything works fine but when we set wayland-egl it is not working
It looks like events are not mapped correctly as debug log shows:
```
LINUXFB:
2021-10-21T08:50:55.749591+00:00 corecard stderr: qt.qpa.input: Using xkbcommon for key mapping
WAYLAND:
2021-10-21T12:02:26.850376+00:00 corecard stderr: qt.xkb.compose: using xkb compose input context
2021-10-21T12:02:26.850452+00:00 corecard stderr: qt.qpa.wayland: using input method: QComposeInputContext
```
I also read lot of things about SEAT and other things to set in weston.ini but really don't know what to set.
Your quick response is highly appreciated !!
--
Thanks,
Hiteshhttps://gitlab.freedesktop.org/wayland/weston/-/issues/555kiosk-shell/kiosk-shell.c 410:Does it need to process the other situations?2021-11-27T10:15:52ZHankWong-guangdongkiosk-shell/kiosk-shell.c 410:Does it need to process the other situations?There is a "if...else if" case in kiosk-shell.c 406 line, the code is:
if (keyboard &&
wl_list_empty(&shseat->keyboard_focus_listener.link)) {
wl_signal_add(&keyboard->focus_signal,
&shseat->keyboard_focus_listener);
} ...There is a "if...else if" case in kiosk-shell.c 406 line, the code is:
if (keyboard &&
wl_list_empty(&shseat->keyboard_focus_listener.link)) {
wl_signal_add(&keyboard->focus_signal,
&shseat->keyboard_focus_listener);
} else if (!keyboard) {
wl_list_remove(&shseat->keyboard_focus_listener.link);
wl_list_init(&shseat->keyboard_focus_listener.link);
}
I want to ask if it need an else case after the "else if" to process the other situations?