[ANNOUNCE] Weston 11.0 release schedule change
Hi, According to the previous schedule, a new Weston release is due today. However, we've decided to push back the release. We'd want to merge a few more bug fixes before the 11.0 release. The new schedule is as follows: - RC2: September 15th - First possible release: September 22nd As usual, we may do a RC3 if it turns out we need more time for fixes and reviews. Thanks, Simon
Re: Wrong (non modified) key under Wayland when multiple events combined in single SYN_REPORT
Hi, On 9/12/22 23:20, Peter wrote: > Hi all, > > > Op maandag 12 september 2022 om 15:14:09 +0200 schreef Juerd Waalboer > : >> Hans de Goede skribis 2022-09-12 7:16 (+0200): >>> During a big hacker event in the Netherlands this summer (MCH) the logistics >>> team used custom barcodes to keep track of inventory. These custom barcodes >>> contain a # symbol. >> >> In other barcodes, @ symbols. Quite possibly anything with shifted >> characters; I vaguely recall a mixed case (ascii) string where the >> uppercasing was on the wrong letter. > > Yes, that definitely also happened. > >> >>> Juerd, we did not discuss how you were running Wayland (which compositor), >>> I guess you were using GNOME3 when you hit this ? >> >> I'm not sure, as I only encountered the bug as an end user and suggested >> changing to X to work around it (which worked). I've added Peter Hazenberg >> to the CC list; he installed and maintained the computers, and is familiar >> with the bug. Peter, can you confirm that we were using GNOME 3 in both >> Wayland and X? > > Yes, we used gnome 3. It was mostly a boring default Fedora 36 Workstation > installation. > > Good to hear Hans already reproduced the issue at the mentioned hackerspace, > I assume with the exact same hardware Yes I reproduced it on my own laptop inside a terminal under GNOME3. I suspect that it reproduces on any (VTE based?) terminal running under GNOME3 Wayland when using the right barcode-scanner model and scanning specific barcodes. . Regards, Hans
Re: Wrong (non modified) key under Wayland when multiple events combined in single SYN_REPORT
Hi!, On Tue, Sep 13, 2022 at 11:36 AM Hans de Goede wrote: > > Hi, > > On 9/12/22 23:20, Peter wrote: > > Hi all, > > > > > > Op maandag 12 september 2022 om 15:14:09 +0200 schreef Juerd Waalboer > > : > >> Hans de Goede skribis 2022-09-12 7:16 (+0200): > >>> During a big hacker event in the Netherlands this summer (MCH) the > >>> logistics > >>> team used custom barcodes to keep track of inventory. These custom > >>> barcodes > >>> contain a # symbol. > >> > >> In other barcodes, @ symbols. Quite possibly anything with shifted > >> characters; I vaguely recall a mixed case (ascii) string where the > >> uppercasing was on the wrong letter. > > > > Yes, that definitely also happened. > > > >> > >>> Juerd, we did not discuss how you were running Wayland (which compositor), > >>> I guess you were using GNOME3 when you hit this ? > >> > >> I'm not sure, as I only encountered the bug as an end user and suggested > >> changing to X to work around it (which worked). I've added Peter Hazenberg > >> to the CC list; he installed and maintained the computers, and is familiar > >> with the bug. Peter, can you confirm that we were using GNOME 3 in both > >> Wayland and X? > > > > Yes, we used gnome 3. It was mostly a boring default Fedora 36 Workstation > > installation. > > > > Good to hear Hans already reproduced the issue at the mentioned > > hackerspace, I assume with the exact same hardware > > Yes I reproduced it on my own laptop inside a terminal under GNOME3. I > suspect that it reproduces on any (VTE based?) terminal running under GNOME3 > Wayland when using the right barcode-scanner model and scanning specific > barcodes. Thanks Hans/Juerd/Peter. I can reproduce this issue on GNOME Shell with the evemu logs provided. From my multiple tries, the libinput debug output seems pretty much consistent and in line with the evemu output (i.e. press shift, release 't', press '3', release shift), so there does not seem to be any issue there. At the wayland level, the wl_keyboard.modifier events received by the client are somewhat amiss though. Amusingly, running on plain Mutter (e.g. `mutter --wayland --display-server` on a TTY) does also seem to fix the issue. The most immediate difference I can think of is the involvement of input methods. Since this does not seem to be a generic Wayland issue, feel free to file a bug at https://gitlab.gnome.org/GNOME/gnome-shell/-/issues and move discussion there, this might still end up in Mutter, or in IBus, unclear yet. Cheers, Carlos
[ANNOUNCE] wayland-utils 1.1.0
The official release of wayland-utils 1.1.0 is now available. wayland-utils contains wayland-info, a utility for displaying various information about the Wayland protocols supported by the Wayland compositor. Notable changes in wayland-utils 1.1.0 include: * Support for linux_dmabuf version 4 (version 3 still supported) * A human readable description to the dmabuf format modifier tokens using libdrm (optional), * The list of SHM supported formats is now more consistent with the list of dmabuf formats, * Support for wl_output version 4, * A couple of compilation issues on the BSD systems are addressed. The only change since RC1 is a documentation fix for the release procedure. The git shortlog is below: Olivier Fourdan (2): releasing: Use the release script from wayland build: bump to version 1.1.0 for the official release git tag: 1.1.0 https://gitlab.freedesktop.org/wayland/wayland-utils/-/releases/1.1.0/downloads/wayland-utils-1.1.0.tar.xz SHA256: 9e685863025b4feade36d53bbc8e31b43e26498be743dea84c7a84912959410a wayland-utils-1.1.0.tar.xz SHA512: 5b841ecb9b534a9b353e104dda9410961495495380fa65e32ef40855750609b03942a87c2fd66339aab57c05b3b8699e2bee055cfd44151f9609a5f6c53349df wayland-utils-1.1.0.tar.xz PGP: https://gitlab.freedesktop.org/wayland/wayland-utils/-/releases/1.1.0/downloads/wayland-utils-1.1.0.tar.xz.sig OpenPGP_0x14706DBE1E4B4540.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
