weston issueshttps://gitlab.freedesktop.org/wayland/weston/-/issues2018-06-30T10:14:02Zhttps://gitlab.freedesktop.org/wayland/weston/-/issues/28weston dnd client render issues2018-06-30T10:14:02ZBugzilla Migration Userweston dnd client render issues## Submitted by Brian Lovin
Assigned to **Wayland bug list**
**[Link to original bug (#56298)](https://bugs.freedesktop.org/show_bug.cgi?id=56298)**
## Description
System Environment:
--------------------------
Distro: Ubuntu 12.0...## Submitted by Brian Lovin
Assigned to **Wayland bug list**
**[Link to original bug (#56298)](https://bugs.freedesktop.org/show_bug.cgi?id=56298)**
## Description
System Environment:
--------------------------
Distro: Ubuntu 12.04
Arch: x86_64
cairo master db488a1703d4ef3bcbd54138b51c01600a2f4d3a
dri2proto master 4eeacce4c4a300b938b7e3fb78a8e443c491780b
drm master 844d75e5a0b3b8f3466a24256955e886275fb298
glproto master ec1eec4355ee4a6c5134f2178192f10b6d28a87a
kbproto master 391a1f6de6315fc0196d407d800597488315cccb
libX11 master d45b3fc19fbe95c41afc4e51d768df6d42332010
libxkbcommon master 3477d9e4480f4f2607d371345cc1c09bb8a35c78
macros master 0890e4003aacfa7113ab3f4e3ad7c5636f8e922a
mesa master df3721fd2e10ef27ce12a0c1025c9770137fa8f7
pixman master 2e17b6dd4ee7c32684fb7ffc70d3ad3ebf7cb2ef
wayland master 0371668dcca5aa29c0fc4b59b974e40bcf073563
weston master 4e07236e8702ff22e2398214a15f7d1e7561caf6
Detailed Description:
-----------------------------
I have observed multiple issues with rendering under the DnD client - I combined them all into this one bug.
Issue 1: When a flower is dropped it "flashes" for a brief moment only when mouse is stopped, if mouse cursor is in movement the flower won't flash
Issue 2: When a flower is clicked it moves a couple pixels - even if the mouse hasn't moved.
Issue 3: When you release the mouse button after draging and dropping, but don't move the mouse the incorrect cursor is displayed.
Issue 4: When DND client is spun around it's axis and a flower is picked up to be dragged it "snaps" back to it's original position - sometimes off the mouse cursor
Steps to Reproduce:
----------------------------
1. start weston under X11 or DRM mode
2. ./dnd
3. Drag and drop items (same window is OK), click items, spin window and drop items, release mouse and observe the incorrect cursorhttps://gitlab.freedesktop.org/wayland/weston/-/issues/32Application always launch on seated output2018-06-30T10:40:09ZBugzilla Migration UserApplication always launch on seated output## Submitted by Anu Reddy
Assigned to **Wayland bug list**
**[Link to original bug (#73715)](https://bugs.freedesktop.org/show_bug.cgi?id=73715)**
## Description
When configuring udev rules on a second pointing device to use the s...## Submitted by Anu Reddy
Assigned to **Wayland bug list**
**[Link to original bug (#73715)](https://bugs.freedesktop.org/show_bug.cgi?id=73715)**
## Description
When configuring udev rules on a second pointing device to use the seat functionality, two pointers appear. One that is bound to the seat and the other that is not bound to the seat. Using the pointer which is not bound to the seat, user should be able to execute applications on both seated and not seated displays. But, applications always show on seated display irrespective of where they are executed from.
Steps:
1. Cold plugged display1, pointing device and display2
2. Create udev rules in Weston.rules using device path of USB
Example
ACTION=="add", SUBSYSTEMS=="input", DEVPATH=="/devices/pci0000:00/0000:00:14.0/usb1/*", ENV{WL_SEAT}+="back0"
3. Configure Weston to seat the second pointing device on the display2
Example:
Output
Name=HDMI2
Seat=back0
4. plug a second pointing device into the USB hub( this will bound to display2)
5. Launch weston-launch.
6. Launch weston-terminal on display1 using mouse pointer( which is not bound to seat). Observe terminal showing on display2.
Software:
wayland (HEAD) 1.3.92-0-gc102c20
drm (HEAD) libdrm-2.4.50-0-g4c5de72
mesa (HEAD) remotes/origin/10.0-0-g3a62718
libva (HEAD) libva-1.2.1-0-g88ed1eb
intel-driver (HEAD) 1.2.1-0-g8f306e3
weston (HEAD) 1.3.92-0-gb637a40https://gitlab.freedesktop.org/wayland/weston/-/issues/36Clients windows can be extended into panel while re-sizing the top edge2018-10-15T20:04:27ZBugzilla Migration UserClients windows can be extended into panel while re-sizing the top edge## Submitted by vivek
Assigned to **vivek**
**[Link to original bug (#80228)](https://bugs.freedesktop.org/show_bug.cgi?id=80228)**
## Description
Created attachment 101352
screenshot of the bug
When we resize the top edge of the...## Submitted by vivek
Assigned to **vivek**
**[Link to original bug (#80228)](https://bugs.freedesktop.org/show_bug.cgi?id=80228)**
## Description
Created attachment 101352
screenshot of the bug
When we resize the top edge of the client window. it extends into the compositor panel and after that we cannot move or resize the window.
**Attachment 101352**, "screenshot of the bug":
![Screenshot_from_2014-06-19](/uploads/7546672d1c9997c2a46a62a6f50bc504/Screenshot_from_2014-06-19.png)https://gitlab.freedesktop.org/wayland/weston/-/issues/39Fix shell interactions with minimized state2019-04-26T08:26:45ZBugzilla Migration UserFix shell interactions with minimized state## Submitted by Manuel Bachmann
Assigned to **Wayland bug list**
**[Link to original bug (#81977)](https://bugs.freedesktop.org/show_bug.cgi?id=81977)**
## Description
When a surface becomes fullscreen, and then gets minimized wit...## Submitted by Manuel Bachmann
Assigned to **Wayland bug list**
**[Link to original bug (#81977)](https://bugs.freedesktop.org/show_bug.cgi?id=81977)**
## Description
When a surface becomes fullscreen, and then gets minimized with "xdg_surface_set_minimized()", Weston will stay in the fullscreen state and only display a totally black screen.
Video of the issue :
https://www.youtube.com/watch?v=ajFbTjQozhc
Here is the patch that fixes this :
http://lists.freedesktop.org/archives/wayland-devel/2014-July/016257.html
Video after the patch :
https://www.youtube.com/watch?v=nwDFvEjFXZUhttps://gitlab.freedesktop.org/wayland/weston/-/issues/40terminal: console not clearing on exit from vim, vi or nano2018-06-30T10:44:54ZBugzilla Migration Userterminal: console not clearing on exit from vim, vi or nano## Submitted by kabeer
Assigned to **Wayland bug list**
**[Link to original bug (#82766)](https://bugs.freedesktop.org/show_bug.cgi?id=82766)**
## Description
Created attachment 104816
Screenshot of bug while using vim in weston c...## Submitted by kabeer
Assigned to **Wayland bug list**
**[Link to original bug (#82766)](https://bugs.freedesktop.org/show_bug.cgi?id=82766)**
## Description
Created attachment 104816
Screenshot of bug while using vim in weston console
I am new to community. While testing weston I found that screen is not clearing when we exit from any of the console editors. This problem persists with vim,vi and nano.
Screenshot is attached
**Attachment 104816**, "Screenshot of bug while using vim in weston console":
![WestonVimBug](/uploads/cb8d850200540f14839649790b152b86/WestonVimBug.png)
Version: 1.5.0https://gitlab.freedesktop.org/wayland/weston/-/issues/43Weston screen does not lock on vt switch2021-07-05T08:49:20ZBugzilla Migration UserWeston screen does not lock on vt switch## Submitted by Anu Reddy
Assigned to **Wayland bug list**
**[Link to original bug (#83212)](https://bugs.freedesktop.org/show_bug.cgi?id=83212)**
## Description
Steps to Repro:
1. Launch weston : weston –i5
2. Switch away, then s...## Submitted by Anu Reddy
Assigned to **Wayland bug list**
**[Link to original bug (#83212)](https://bugs.freedesktop.org/show_bug.cgi?id=83212)**
## Description
Steps to Repro:
1. Launch weston : weston –i5
2. Switch away, then switch back to VT via `<ctrl>`+`<alt>`+`<fn>`
3. Wait for screen to lock
4. Notice that weston does not lock it’s screen after vt switch
Software Stack
wayland (HEAD) remotes/origin/HEAD-0-g6d0f298
drm (HEAD) heads/master-16-gd686160
mesa (HEAD) remotes/origin/10.2-0-gd82ca4e
libva (HEAD) libva-1.3.1-0-g053f70f
intel-driver (HEAD) 1.3.1-0-ga720bc8
cairo (HEAD) heads/1.12-0-g59e2a93
libinput (HEAD) heads/master-163-gbb10ec8
weston (HEAD) remotes/origin/master-0-g652c794https://gitlab.freedesktop.org/wayland/weston/-/issues/44fail to receive touch_frame after final touch_up (Qt)2019-12-14T23:28:35ZBugzilla Migration Userfail to receive touch_frame after final touch_up (Qt)## Submitted by Shawn Rutledge
Assigned to **Wayland bug list**
**[Link to original bug (#83383)](https://bugs.freedesktop.org/show_bug.cgi?id=83383)**
## Description
In Qt applications it was not possible to press any QPushButton...## Submitted by Shawn Rutledge
Assigned to **Wayland bug list**
**[Link to original bug (#83383)](https://bugs.freedesktop.org/show_bug.cgi?id=83383)**
## Description
In Qt applications it was not possible to press any QPushButton or QtQuick MouseArea on a touchscreen because of this: it waits for the release in order to treat the press-release sequence as a "click". So we added a workaround: if all touch points have been released, send ourselves an artificial touch_frame. But it has been said that this might be a regression after the latest work with wayland using libinput.
https://codereview.qt-project.org/#/c/93572/
Tested with the latest git versions of wayland, weston and libinput on Arch Linux, on two different systems both with touchscreens.
Version: 1.5.0https://gitlab.freedesktop.org/wayland/weston/-/issues/45Weston-editor text deleted when inserting new text2018-06-30T10:50:35ZBugzilla Migration UserWeston-editor text deleted when inserting new text## Submitted by Anu Reddy
Assigned to **Wayland bug list**
**[Link to original bug (#83778)](https://bugs.freedesktop.org/show_bug.cgi?id=83778)**
## Description
Steps to Reproduce:
1. Launch weston
2. Execute weston-editor
3. Usi...## Submitted by Anu Reddy
Assigned to **Wayland bug list**
**[Link to original bug (#83778)](https://bugs.freedesktop.org/show_bug.cgi?id=83778)**
## Description
Steps to Reproduce:
1. Launch weston
2. Execute weston-editor
3. Using weston-keyboard, type some text into Entry field.
4. Now, touch anywhere within the line to insert new text
5. Observe that text gets selected.
5. When you try to type new text, the selected text will be deleted. See attached video for more info.
Software Stack
wayland (HEAD) remotes/origin/HEAD-0-g44bf13b
drm (HEAD) heads/master-16-gd686160
mesa (HEAD) remotes/origin/10.2-0-g7ffc855
libva (HEAD) libva-1.3.1-0-g053f70f
intel-driver (HEAD) 1.3.1-0-ga720bc8
cairo (HEAD) remotes/origin/1.12-0-g4b65497
libinput (HEAD) heads/master-163-gbb10ec8https://gitlab.freedesktop.org/wayland/weston/-/issues/47Simplify/unify Weston's transformation code2019-11-21T10:39:05ZBugzilla Migration UserSimplify/unify Weston's transformation code## Submitted by Derek Foreman `@derek`
Assigned to **Wayland bug list**
**[Link to original bug (#83895)](https://bugs.freedesktop.org/show_bug.cgi?id=83895)**
## Description
Weston's renderers may use different co-ordinate system...## Submitted by Derek Foreman `@derek`
Assigned to **Wayland bug list**
**[Link to original bug (#83895)](https://bugs.freedesktop.org/show_bug.cgi?id=83895)**
## Description
Weston's renderers may use different co-ordinate systems and have conceptually different ways of handling image data (pixman moves the pixels, gl moves the rectangle they're drawn on)
We currently represent transformations with a handful of floats(scale, translation) and an enum(monitor orientations).
This makes the pixman renderer easily broken since a lot of cases (all the monitor orientations) have to be considered for every change.
By creating transformation matrices and reducing as many of these special cases as possible to simple matrix multiplication we should be able to make the pixman renderer more maintainable and simplify a lot of other code as well.
Current work in progress at:
https://github.com/ManMower/weston/commits/transforms
Based on the work started at:
https://github.com/jekstrand/weston/commits/wip/transforms
### Depends on
* [Bug 83989](https://bugs.freedesktop.org/show_bug.cgi?id=83989)https://gitlab.freedesktop.org/wayland/weston/-/issues/51Ensure that 'make check' does not use any Weston components outside the build2019-11-21T10:53:37ZBugzilla Migration UserEnsure that 'make check' does not use any Weston components outside the build## Submitted by Pekka Paalanen
Assigned to **Wayland bug list**
**[Link to original bug (#83986)](https://bugs.freedesktop.org/show_bug.cgi?id=83986)**
## Description
'make check' should not require 'make install' first.
Add some...## Submitted by Pekka Paalanen
Assigned to **Wayland bug list**
**[Link to original bug (#83986)](https://bugs.freedesktop.org/show_bug.cgi?id=83986)**
## Description
'make check' should not require 'make install' first.
Add some sort of tests, that ensure all files are loaded from the build directory, and nothing is accidentally loaded from the system, including: weston.ini, weston plugins, backends, helper programs (weston-desktop-shell, weston-keyboard, etc.).
We want to notice if anything gets used from the system, because that compromises the test results.
There could still be some cases where some components might be picked up from the system. All those need to be fixed.
Maybe we should have a some sort of switch to Weston to put it into test mode, which makes it skip all normal search paths?
http://cgit.freedesktop.org/wayland/weston/commit/?id=c7210434d45cff0135e42bd3047988e1274d49dd
was a good step in that direction. Is it enough? Are there any security implications?
### Blocking
* [Bug 83980](https://bugs.freedesktop.org/show_bug.cgi?id=83980)https://gitlab.freedesktop.org/wayland/weston/-/issues/53Use toytoolkit in a test for interactive window move2018-06-30T10:54:01ZBugzilla Migration UserUse toytoolkit in a test for interactive window move## Submitted by Pekka Paalanen
Assigned to **Wayland bug list**
**[Link to original bug (#83990)](https://bugs.freedesktop.org/show_bug.cgi?id=83990)**
## Description
Write a test, that:
1. creates a window with normal decorations...## Submitted by Pekka Paalanen
Assigned to **Wayland bug list**
**[Link to original bug (#83990)](https://bugs.freedesktop.org/show_bug.cgi?id=83990)**
## Description
Write a test, that:
1. creates a window with normal decorations using toytoolkit
2. check the window position via the test extension
3. sends fake input events
3.1. move the pointer over the window title bar
3.2. button down
3.3. move the pointer to another place
3.4. button up
4. check the window position via the test extension, that it moved correctly
This sounds simple, but requires one to write the infrastructure for using toytoolkit in tests, maybe change how wl_test pointer events are done, and add a way to query surface location.
For examples, see https://github.com/01org/wayland-fits for the test protocol and the weston plugin.
If bug #83987 is implemented, can also add screenshot based verification, which would make sure that toytoolkit draws decorations properly. But that opens a whole new road for adding tests.
### Blocking
* [Bug 83980](https://bugs.freedesktop.org/show_bug.cgi?id=83980)https://gitlab.freedesktop.org/wayland/weston/-/issues/54input-method.xml has a factory for wl_keyboard causing version conflict2018-06-30T10:54:22ZBugzilla Migration Userinput-method.xml has a factory for wl_keyboard causing version conflict## Submitted by Pekka Paalanen
Assigned to **Wayland bug list**
**[Link to original bug (#84034)](https://bugs.freedesktop.org/show_bug.cgi?id=84034)**
## Description
Request wl_input_method_context.grab_keyboard creates a new wl_...## Submitted by Pekka Paalanen
Assigned to **Wayland bug list**
**[Link to original bug (#84034)](https://bugs.freedesktop.org/show_bug.cgi?id=84034)**
## Description
Request wl_input_method_context.grab_keyboard creates a new wl_keyboard object.
wl_seat.get_keyboard is the primary request for creating wl_keyboard objects.
This causes a runtime interface versioning conflict.
wl_keyboard in core is already at version 4, but you can only create wl_keyboard version 1 via wl_input_method_context. You cannot bump wl_input_method_context version without starting to get wl_keyboards of higher version. The major problem comes, when you bump input-method interface version beyond what is currently the highest version of wl_seat, and then someone adds a new thing to wl_keyboard. Input-method would start dealing out wl_keyboards automatically with a version claiming to support the new thing without clients or servers ever implementing the support.
wl_input_method_context.grab_keyboard should not be creating objects of type wl_keyboard, but the type should be unique for wl_input_method_context.https://gitlab.freedesktop.org/wayland/weston/-/issues/57Define further keybindings in weston.ini2018-07-10T22:17:28ZBugzilla Migration UserDefine further keybindings in weston.ini## Submitted by Jonas Heinrich
Assigned to **Wayland bug list**
**[Link to original bug (#85474)](https://bugs.freedesktop.org/show_bug.cgi?id=85474)**
## Description
Hi,
I wish to map commands like dmenu or terminal to specific k...## Submitted by Jonas Heinrich
Assigned to **Wayland bug list**
**[Link to original bug (#85474)](https://bugs.freedesktop.org/show_bug.cgi?id=85474)**
## Description
Hi,
I wish to map commands like dmenu or terminal to specific keybindings in weston.ini. For now I have to hack additional keybindings into the weston source code.https://gitlab.freedesktop.org/wayland/weston/-/issues/58Copy and paste not working properly + crash2021-01-24T11:10:15ZBugzilla Migration UserCopy and paste not working properly + crash## Submitted by Jonas Heinrich
Assigned to **Wayland bug list**
**[Link to original bug (#85475)](https://bugs.freedesktop.org/show_bug.cgi?id=85475)**
## Description
Hi,
I'm using the latest Wayland and Weston version 1.6.
Tryin...## Submitted by Jonas Heinrich
Assigned to **Wayland bug list**
**[Link to original bug (#85475)](https://bugs.freedesktop.org/show_bug.cgi?id=85475)**
## Description
Hi,
I'm using the latest Wayland and Weston version 1.6.
Trying to copy text in Epiphany or files in Nautilus sometimes work but often there is nothing in the clipboard. Trying to copy something repeatedly could cause a crash and Weston quits.https://gitlab.freedesktop.org/wayland/weston/-/issues/59dim-layer focus animation doesn't work with more outputs2018-06-30T10:56:27ZBugzilla Migration Userdim-layer focus animation doesn't work with more outputs## Submitted by Marek Chalupa
Assigned to **Wayland bug list**
**[Link to original bug (#85597)](https://bugs.freedesktop.org/show_bug.cgi?id=85597)**
## Description
Steps to reproduce:
1) set dim-layer focus animation
2) run wes...## Submitted by Marek Chalupa
Assigned to **Wayland bug list**
**[Link to original bug (#85597)](https://bugs.freedesktop.org/show_bug.cgi?id=85597)**
## Description
Steps to reproduce:
1) set dim-layer focus animation
2) run weston with more outputs
3) run a wayland client on second output
4) observe that only default output gets dimmed, no matter where the client is or what the client does.
Regards,
Marekhttps://gitlab.freedesktop.org/wayland/weston/-/issues/60wl_fixed is not precise enough for high dpi mice2022-09-29T15:53:51ZBugzilla Migration Userwl_fixed is not precise enough for high dpi mice## Submitted by Derek Foreman `@derek`
Assigned to **Wayland bug list**
**[Link to original bug (#85715)](https://bugs.freedesktop.org/show_bug.cgi?id=85715)**
## Description
(Related to [bug 85632](https://bugs.freedesktop.org/sh...## Submitted by Derek Foreman `@derek`
Assigned to **Wayland bug list**
**[Link to original bug (#85715)](https://bugs.freedesktop.org/show_bug.cgi?id=85715)**
## Description
(Related to [bug 85632](https://bugs.freedesktop.org/show_bug.cgi?id=85632))
I have a mouse here (a Razer Abyssus) with a 3500DPI sensor.
There is discussion about having libinput normalize mouse input to a 400dpi standard - some patches have landed in libinput, but there isn't yet a way to change from the default 400dpi setting.
Once that works, this 3500 dpi mouse will have its deltas multiplied by 400/3500 before being fed to the pointer acceleration filter. On the other end of the accel filter this slow motion becomes even slower, and the deltas end up below the threshold for wl_fixed. It's entirely possible to slowly move your mouse along indefinitely without any motion occurring.
I have confirmed that this is not just really slow motion (that will eventually accumulate to on screen movement) - motion is being rounded to zero during the wl_fixed_to_double() conversion in weston's libinput-device.c
To reproduce:
Get a ridiculous mouse. The more blue LEDs the better. (3000+ DPI can show the problem easily, 2000 will do in a pinch)
Use libinput master branch and change device->dpi = DEFAULT_MOUSE_DPI; in src/evdev.c to whatever is appropriate
### Blocking
* [Bug 84014](https://bugs.freedesktop.org/show_bug.cgi?id=84014)https://gitlab.freedesktop.org/wayland/weston/-/issues/61weston windows don't regain focus after returning to tty2023-03-23T16:46:24ZBugzilla Migration Userweston windows don't regain focus after returning to tty## Submitted by Andrew Engelbrecht
Assigned to **Wayland bug list**
**[Link to original bug (#87752)](https://bugs.freedesktop.org/show_bug.cgi?id=87752)**
## Description
after switching from weston's tty to another, then returnin...## Submitted by Andrew Engelbrecht
Assigned to **Wayland bug list**
**[Link to original bug (#87752)](https://bugs.freedesktop.org/show_bug.cgi?id=87752)**
## Description
after switching from weston's tty to another, then returning to weston, the front window didn't regain keyboard focus. i noticed this with a weston terminal and a full screen window ("flare", under sdl2). clicking into the window brings back the focus.
it might be nice if the front-most window regains focus upon returning to that tty.https://gitlab.freedesktop.org/wayland/weston/-/issues/62Dangling pointers and memory corruption after output recreate.2018-07-02T11:31:29ZBugzilla Migration UserDangling pointers and memory corruption after output recreate.## Submitted by Andriy Prystupa
Assigned to **Wayland bug list**
**[Link to original bug (#87824)](https://bugs.freedesktop.org/show_bug.cgi?id=87824)**
## Description
Way to reproduce:
- weston backend closes current output and c...## Submitted by Andriy Prystupa
Assigned to **Wayland bug list**
**[Link to original bug (#87824)](https://bugs.freedesktop.org/show_bug.cgi?id=87824)**
## Description
Way to reproduce:
- weston backend closes current output and creates new one.
- old weston_output structure is released.
- compositor views have pointers to old weston_output.
- these pointers became dangling.
Fix:
in weston_compositor_remove_output(...) add resetting reference to output:
wl_list_for_each(view, &compositor->view_list, link) {
if (view->output == remove_output) {
view->output = NULL;
view->surface->output = NULL;
}
}https://gitlab.freedesktop.org/wayland/weston/-/issues/63loading cms-colord.so causes "terminate" to fail2018-06-30T11:02:11ZBugzilla Migration Userloading cms-colord.so causes "terminate" to fail## Submitted by James
Assigned to **Wayland bug list**
**[Link to original bug (#88892)](https://bugs.freedesktop.org/show_bug.cgi?id=88892)**
## Description
On Arch Linux, wayland 1.6.1-1, weston 1.6.1-1.
Starting from a VT with...## Submitted by James
Assigned to **Wayland bug list**
**[Link to original bug (#88892)](https://bugs.freedesktop.org/show_bug.cgi?id=88892)**
## Description
On Arch Linux, wayland 1.6.1-1, weston 1.6.1-1.
Starting from a VT with just "weston", running the drm-backend.so, loading cms-colord.so in ".config/weston.ini", with "modules=xwayland.so,cms-colord.so", as described in man 5 weston.ini, causes "terminate" to fail, using "keymap_options=terminate:ctrl_alt_bksp". This is on a two-headed display.
After attempting to terminate, one screen shows a virtual terminal, though not the VT from which weston was started, the other screen continuing to show the weston display, the keyboard becomes "locked", and weston continues to run. From a remote terminal, "ps" shows weston sleeping, and weston-keyboard and weston-desktop-shell as zombies. "kill -2" does nothing. "kill -9" terminates weston, and the display and keyboard return to normal operation.
For what it might be worth, running as "WAYLAND_DEBUG=1 weston" ends with:
Killed70.967] -> wl_subcompositor@5.destroy()rface@21) 0)0, 5)ttach(10592907wl_buffer@37)_buffer@)_buffer@, 2774551, )300)@6000014)-motion button
Of course, simply not including cms-colord.so in "modules" avoids the problem.https://gitlab.freedesktop.org/wayland/weston/-/issues/1Input serials are broken2023-07-10T06:31:45ZBugzilla Migration UserInput serials are broken## Submitted by Daniel Stone `@daniels`
Assigned to **Daniel Stone `@daniels`**
**[Link to original bug (#11)](https://phabricator.freedesktop.org/T11)**
## Description
Currently Weston has one global serial counter, where we shou...## Submitted by Daniel Stone `@daniels`
Assigned to **Daniel Stone `@daniels`**
**[Link to original bug (#11)](https://phabricator.freedesktop.org/T11)**
## Description
Currently Weston has one global serial counter, where we should be generating disjoint serials for pointer, keyboard and touch.Daniel Stonedaniel@fooishbar.orgDaniel Stonedaniel@fooishbar.org