This doesn't seem consistent, but it might be a problem with just some flatpak and/or snap and/or deb packages. (This comes from a similar bug 2041008)
- gedit (the old Gnome editor) as flatpak lacks Guillemets - gedit (the old Gnome editor) as deb has Guillemets - Text Editor (the new Gnome editor) as flatpak has Guillemets - Text Editor (the new Gnome editor) as deb has Guillemets - TextPieces as flatpak lacks Guillemets - Chromium as snap has Guillemets - Firefox as snap lacks Guillemets - Vivaldi as snap has Guillemets This could perhaps indicate that there are something going on with the runtime environment for flatpak and snap packages. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/2084189 Title: Missing characters on keyboard under Wayland Status in wayland package in Ubuntu: Confirmed Bug description: I have a Logitech Mechanical Mini keyboard, and two characters guillemotleft («) and guillemotright (») that previously worked by pressing [right alt]+[z] and [right alt]+[x] does not work after upgrading to Ubuntu 24.10. The special key is set to default. I'm using Solaar, but there are no rules that should interfere with those keypresses, and it doesn't matter whether that app run or not. Some random testing seems to indicate that it is only those two characters that are missing, but the testing isn't extensive. The characters guillemotleft and guillemotright are also called "sjevroner" and "anførselstegn" in Norwegian, and they are said to be the correct quotation marks in published papers. [Norwegian Wikipedia: Anførselstegn](https://no.wikipedia.org/wiki/Anf%C3%B8rselstegn) The layout is reported as expected by the "keyboard layout" (tecla) app that opens from the accessability menu. Ie. menu in top right corner of the desktop. The same happen both in "Norwegian" and "Norwegian (no dead keys)". The same characters are in use in "Danish", and they are included on keyboard layout, but does not work. They keys as such work as expected (zxZX), but I can't test with other keyboards for the moment. A workaround is to use the sequence [compose][<][<] and [compose][>][>], but I wonder whether that is well known. [addendum] Usually I never use Wayland, but due to upgrade to 24.10 I got Wayland as default. Seems like this anomaly only exist in Wayland, because when I switched back to X11 the keyboard layout was as expected. Under X11/Gnome I get the following ```bash $ localectl System Locale: LANG=nb_NO.UTF-8 LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en VC Keymap: (unset) X11 Layout: no X11 Model: pc105 ``` ```bash $ setxkbmap -query rules: evdev model: pc105+inet layout: no,no,dk,us variant: nodeadkeys,,, options: compose:rctrl ``` Under Wayland/Gnome I get the following ```bash $ setxkbmap -query WARNING: Running setxkbmap against an Xwayland server rules: evdev model: pc105 layout: us ``` Given that I'm understand this correctly libinput is using evdev, so setxkbmap should give the same, but it does not? (Yes, I've seen the warning.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/2084189/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
