gnome-shell issueshttps://gitlab.gnome.org/GNOME/gnome-shell/-/issues2024-03-15T10:25:29Zhttps://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7485OSK backspace key seems to never get release after long press2024-03-15T10:25:29ZSebastian KellerOSK backspace key seems to never get release after long pressIn `gtk4-widget-factory` in the text view move the cursor to the end of the text and hold backspace long enough to trigger the long press code path then release. This will now continuously keep deleting text until the backspace key is pr...In `gtk4-widget-factory` in the text view move the cursor to the end of the text and hold backspace long enough to trigger the long press code path then release. This will now continuously keep deleting text until the backspace key is pressed again.https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7483"Need keyval or commitString" error message when using OSK keys that don't us...2024-03-15T09:50:57ZSebastian Keller"Need keyval or commitString" error message when using OSK keys that don't use either of thoseWhen pressing the backspace, shift, gear or emoji keys that don't send a keyval or commit string, this error message is generated.When pressing the backspace, shift, gear or emoji keys that don't send a keyval or commit string, this error message is generated.https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6988Stack trace appears when rotating a tablet computer running Gnome2023-09-06T19:42:44ZLanceStack trace appears when rotating a tablet computer running Gnome### Affected version
44 and 45.rc
### Bug summary
When rotating a tablet computer running Gnome a stack trace is produced. Appearing to be the Keyboard crashing. Tested on Wayland.
### Steps to reproduce
Rotate the tablet, see Gnome...### Affected version
44 and 45.rc
### Bug summary
When rotating a tablet computer running Gnome a stack trace is produced. Appearing to be the Keyboard crashing. Tested on Wayland.
### Steps to reproduce
Rotate the tablet, see Gnome change orientation. Spot stack trace messages pop up in logs.
### What happened
No outward appearing issue really, noticed these messages appear when looking for the source of a different issue in logs.
### What did you expect to happen
No stack trace or crash messages
### Relevant logs, screenshots, screencasts etc.
[journalctl_log.txt](/uploads/162e29523160fbba5bb4baf636b98f0d/journalctl_log.txt)https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6693Allow to manually prevent learning typed words when using OSK2023-08-24T18:21:02ZLocnessAllow to manually prevent learning typed words when using OSK### Feature summary
GNOME 43 introduced a nice feature where, when the OSK is on, the system will remember typed words in order to provide suggestions on the OSK, leveraging ibus-typing-booster. However, there is no obvious way to turn ...### Feature summary
GNOME 43 introduced a nice feature where, when the OSK is on, the system will remember typed words in order to provide suggestions on the OSK, leveraging ibus-typing-booster. However, there is no obvious way to turn this off permanently or temporarily, which can be desired in many cases :
- You share or lend your device without a dedicated user account
- Applications do not properly declare their password fields (happens notably with terminal emulators, applications using less popular toolkits, also happened to me when authenticating to a network share in Nautilus on fresh fedora 37, disappeared after updating)
- You worry that a program running unsandboxed could access the remembered words, which are stored in a plain sqlite database under \~/.local/share/ibus-typing-booster.
Considering the above, I would go as far as calling this a major privacy issue since this is basically a forced keylogger for tablet or accessibility users. I'm surprised the privacy implications of this were not considered more.
Also the possibility of turning it off is already present in ibus-typing-booster, called Incognito Mode.
### How would you like it to work
- A button on the OSK or toggle in its settings popup to enable Typing Booster's incognito mode, with the status clearly communicated on the OSK, and
- Maybe a toggle in the settings to enable incognito mode and/or disable tpying booster entirely.
### Relevant links, screenshots, screencasts etc.
- Onboard has [options](/uploads/2f5cb679458a0dda46d8a0275676ca93/Screenshot_20230513_120914.png) to en-/disable learning and suggestions, and showing [a "pause learning" button](/uploads/81d3029a3d29919ac31ff7b1c1362feb/Screenshot_20230513_123110.png). When clicked once, this button will pause learning until switching to another window. Double-clicking it pauses learning until clicking again.
- [Screencast of fake password being learned when using sudo in a QML terminal](/uploads/8a529c7d950e5e474cf49cbda59e5c69/Screencast_from_2023-04-13_19-56-52.webm) (aside from needing to click space to actually have the text be input to the terminal window)https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6676Gnome onscreen keyboard shows suggestions but never input characters onto inp...2023-10-11T02:50:54ZTed ChangGnome onscreen keyboard shows suggestions but never input characters onto input fields<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Affected version
lsb_release -a
LSB Version: n/a
Distributor ID: openSUSE
Des...<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Affected version
lsb_release -a
LSB Version: n/a
Distributor ID: openSUSE
Description: openSUSE Tumbleweed
Release: 20230508
Codename: n/a
gnome-shell --version
GNOME Shell 44.1
Gnome-wayland on a steam deck
<!--
Provide at least the following information:
* Your OS and version
* Affected GNOME Shell version (see https://wiki.gnome.org/Schedule for currently supported versions)
* Does this issue appear in XOrg and/or Wayland
* Does this issue happen without extensions (please follow instructions below)
To properly disable extensions you can use gnome-extensions-app and then restart
your session. Disabling extensions without a restart is not sufficient to rule
out extensions as cause of a bug. If an issue can only be reproduced with a
certain extension, please file a bug report against that extension first.
-->
![image](/uploads/a29bbb531354493415c0c5ba119f6cda/image.png)
Extensions
GSConnect
Customized Ibus
### Bug summary
The gnome onscreen keyboard seems to be broken. Somehow, the touchscreen only allows the space and enter key to be registered onto the application while all other keys creates word suggestion with no option to paste it into the input fields.
The only work around is to add and delete the keyboard. I believe the lockscreen still works
### Steps to reproduce
<!--
1. Open application
2. Highlight input field
3. Open onscreen keyboard
4. Attempt to type into the text field
-->
### What happened
No text has been stage onto the input field
### What did you expect to happen
Ability to type
### Relevant logs, screenshots, screencasts etc.
<!--
If you have further information, such as technical documentation, logs,
screenshots or screencasts related, please provide them here.
If the bug is a crash, please obtain a stack trace with installed debug
symbols (at least for GNOME Shell and Mutter) and attach it to
this issue following the instructions on
https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces.
-->
[2023-05-09_12-15-44.mkv](/uploads/08e291be94006bf0b1833f4eec02a8af/2023-05-09_12-15-44.mkv)
<!-- Do not remove the following line. -->https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6627Terminal on-screen keyboard does not respect keyboard layout2023-07-05T09:55:21ZLukáš VacekTerminal on-screen keyboard does not respect keyboard layout<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Affected version
<!--
Provide at least the following information:
* Your OS an...<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Affected version
<!--
Provide at least the following information:
* Your OS and version
* Affected GNOME Shell version (see https://wiki.gnome.org/Schedule for currently supported versions)
* Does this issue appear in XOrg and/or Wayland
* Does this issue happen without extensions (please follow instructions below)
To properly disable extensions you can use gnome-extensions-app and then restart
your session. Disabling extensions without a restart is not sufficient to rule
out extensions as cause of a bug. If an issue can only be reproduced with a
certain extension, please file a bug report against that extension first.
-->
OS: Fedora Linux 38.20230422.1 (Silverblue)
Sidenote OS: Also happened on postmarket os phosh
GNOME Version: 44.0
Happend to me on Wayland, most probably happens on XOrg
Extensions do not affect it
### Bug summary
The terminal version of on-screen keyboard does not follow keyboard layout
<!--
Provide a short summary of the bug you encountered.
-->
### Steps to reproduce
1. Set language to Czech (QWERTZ)
2. Enable Screen Keyboard in accesibility
3. Open terminal application (gnome-terminal or console)
4. Click on terminal for keyboard to open
<!--
1. Step one
2. Step two
3. ...
-->
### What happened
Keyboard opened with QWERTY layout
<!--
What did GNOME Shell do that was unexpected?
-->
### What did you expect to happen
Keyboard to open with QWERTZ layout
<!--
What did you expect GNOME Shell to do?
-->
### Relevant logs, screenshots, screencasts etc.
![image](/uploads/384eccd961b12bee68197a752b07e199/image.png)
<!--
If you have further information, such as technical documentation, logs,
screenshots or screencasts related, please provide them here.
If the bug is a crash, please obtain a stack trace with installed debug
symbols (at least for GNOME Shell and Mutter) and attach it to
this issue following the instructions on
https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces.
-->
<!-- Do not remove the following line. -->https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6602OSK number keys produce wrong input on AZERTY layout for numeric text boxes2024-01-25T16:51:48ZNicolas SellenetOSK number keys produce wrong input on AZERTY layout for numeric text boxes### Affected version
Version informations:
* Fedora 37
* Gnome 43.4
* Wayland
### Bug summary
When I try to write numeric values in a numeric text boxes, OSK fill in the box with non integer value as seen in the joint video. This prob...### Affected version
Version informations:
* Fedora 37
* Gnome 43.4
* Wayland
### Bug summary
When I try to write numeric values in a numeric text boxes, OSK fill in the box with non integer value as seen in the joint video. This problem may be due to OSK not taking the french keyboard into account in numeric mode.
### Screencast
![Capture_vidéo_du_2023-04-15_16-11-54](/uploads/d28cf1dc2d6b8a6df83ae0ea508e1319/Capture_vidéo_du_2023-04-15_16-11-54.webm)
<!-- Do not remove the following line. -->https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6592add option to remove word suggestion on on-screen keyboard2023-05-03T19:09:53Zfadil fikrillahadd option to remove word suggestion on on-screen keyboard<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Feature summary
<!--
Describe what you would like to be able to do with GNOME...<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Feature summary
<!--
Describe what you would like to be able to do with GNOME Shell
that you currently cannot do.
-->
i'm on fedora 37, gnome 43.3, currently on-screen keyboard doesn't work on all text field there is, like search bar on gnome software, on my firefox extension text field (bitwarden), and because i don't use physical keyboard, to workaround it, and i know it's reckless for password, i type it on plain text field, let's just say, text editor, and paste it on text field which on-screen keyboard doesn't work.
and here's my problem, my password shows up on word suggestion afterwards, and there's no way i could just remove it.
and of course this feature is useful for removing undesired words in general
### How would you like it to work
<!--
If you can think of a way GNOME Shell might be able to do this,
let us know here.
-->
1. the word suggestion doesn't record words with password quantities like combinations of numbers and letters and symbols , but please do record emails like an.example@address.co
2. long press on touch screen, or right click with cursor shows an option to remove the pointed undesired word, like in the screenshot below.
3. or alternatively, trash bin icon on the left side when word suggestions show up, the button itself fixed in place so its predictable where to click/press. click that icon and all current word suggestions become red buttons, click one of the word suggestion, and that word button implodes, indicating it's gone. and the word suggestions return into its normal state with that word never show up again in the future
### Relevant links, screenshots, screencasts etc.
<!--
If you have further information, such as technical documentation,
code, mockups or a similar feature in another desktop environments,
please provide them here.
-->
this is a screenshot of implemented feature number 2 from gboard on android
![feat](/uploads/f032ff1be1a51944efca4852d6a759e2/feat.png)
<!-- Do not remove the following line. -->https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6482After selecting czech querty layout, OSK shows quertz layout instead2023-03-09T10:51:27ZD4VIDAfter selecting czech querty layout, OSK shows quertz layout insteadWhen selecting the czech **querty** layout, the OSK shows the **quertz** layout instead.
Manjaro, up-to-date (09.03.2023)
X11
GNOME Shell 43.3
mutter 43.3
Gnome is the best DE for touch screens.
But the experience using the on ...When selecting the czech **querty** layout, the OSK shows the **quertz** layout instead.
Manjaro, up-to-date (09.03.2023)
X11
GNOME Shell 43.3
mutter 43.3
Gnome is the best DE for touch screens.
But the experience using the on screen keyboard is just terrible.
Please do something about it.https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6365OSK does not open automatically when naming a new folder in nautilus2023-10-11T02:49:21ZPhilip Wilkp.wilk@student.reading.ac.ukOSK does not open automatically when naming a new folder in nautilus<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Affected version
* Nightly flatpak: No
* Other: Fedora 37 gnome 43.2 wayland
<!...<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Affected version
* Nightly flatpak: No
* Other: Fedora 37 gnome 43.2 wayland
<!--
Provide at least the following information:
* Your OS and version
* Affected GNOME Shell version (see https://wiki.gnome.org/Schedule for currently supported versions)
* Does this issue appear in XOrg and/or Wayland
* Does this issue happen without extensions (please follow instructions below)
To properly disable extensions you can use gnome-extensions-app and then restart
your session. Disabling extensions without a restart is not sufficient to rule
out extensions as cause of a bug. If an issue can only be reproduced with a
certain extension, please file a bug report against that extension first.
-->
### Bug summary
When creating a new folder, the OSK does not open automatically when you tap on the input box for the new folder name. It is possible to open the OSK manually by using the swipe gesture.
This does not occur on the flatpak nightly version, but I could not find a bug on this issue, so I am unsure if this is resolved by the flatpak environment or an upstream patch.
<!--
Provide a short summary of the bug you encountered.
-->
### Steps to reproduce
1. In nautilus, long press on empty space so the context menu appears
2. Tap "New folder"
3. Tap on the input box.
### What happened
OSK does not open on tapping the input box
<!--
What did GNOME Shell do that was unexpected?
-->
### What did you expect to happen
OSK should automatically open on tapping the input box.
<!--
What did you expect GNOME Shell to do?
-->
### Relevant logs, screenshots, screencasts etc.
<!--
If you have further information, such as technical documentation, logs,
screenshots or screencasts related, please provide them here.
If the bug is a crash, please obtain a stack trace with installed debug
symbols (at least for GNOME Shell and Mutter) and attach it to
this issue following the instructions on
https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces.
-->
<!-- Do not remove the following line. -->https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6356OSK pushes calculator input field out of screen2023-10-11T02:49:24Z0unknwnOSK pushes calculator input field out of screen<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Affected version
- Fedora Linux 37
- GNOME 43.2
- X11 (can’t test on Wayland a...<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Affected version
- Fedora Linux 37
- GNOME 43.2
- X11 (can’t test on Wayland as OSK does not show up in calculator)
<!--
Provide at least the following information:
* Your OS and version
* Affected GNOME Shell version (see https://wiki.gnome.org/Schedule for currently supported versions)
* Does this issue appear in XOrg and/or Wayland
* Does this issue happen without extensions (please follow instructions below)
To properly disable extensions you can use gnome-extensions-app and then restart
your session. Disabling extensions without a restart is not sufficient to rule
out extensions as cause of a bug. If an issue can only be reproduced with a
certain extension, please file a bug report against that extension first.
-->
### Bug summary
When I input numbers in the calculator it gets pushed out of the screen and I have to move it back manually.
<!--
Provide a short summary of the bug you encountered.
-->
### Steps to reproduce
1. Open calculator and position it to the top
2. Activate OSK
3. Type in something with OSK
### What happened
The window gets pushed out of screen.
### What did you expect to happen
It should have stayed where it was.
### Relevant logs, screenshots, screencasts etc.
![Bildschirmaufzeichnung_vom_2023-02-03__14-52-46](/uploads/3a7774d0a895d43c971dcedb336e07ce/Bildschirmaufzeichnung_vom_2023-02-03__14-52-46.webm)
<!--
If you have further information, such as technical documentation, logs,
screenshots or screencasts related, please provide them here.
If the bug is a crash, please obtain a stack trace with installed debug
symbols (at least for GNOME Shell and Mutter) and attach it to
this issue following the instructions on
https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces.
-->
<!-- Do not remove the following line. -->https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6340OnScreen Keyboard Selects and deletes on firefox with backspace2024-03-06T22:34:12ZsnoutieOnScreen Keyboard Selects and deletes on firefox with backspace<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Affected version
<!--
Provide at least the following information:
* Your OS an...<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Affected version
<!--
Provide at least the following information:
* Your OS and version
* Affected GNOME Shell version (see https://wiki.gnome.org/Schedule for currently supported versions)
* Does this issue appear in XOrg and/or Wayland
* Does this issue happen without extensions (please follow instructions below)
To properly disable extensions you can use gnome-extensions-app and then restart
your session. Disabling extensions without a restart is not sufficient to rule
out extensions as cause of a bug. If an issue can only be reproduced with a
certain extension, please file a bug report against that extension first.
-->
43.2
### Bug summary
The bug is best summarized with the video below
![Screencast_from_2023-01-26_10-18-41](/uploads/d301b4baeb68a8c0d79e37f6f6fca633/Screencast_from_2023-01-26_10-18-41.webm)
### What happened
See video
### What did you expect to happen
Backspace to work normally
<!-- Do not remove the following line. -->https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6279OSK pop up/down animation is stuttery2023-10-11T02:49:24ZPhilip Wilkp.wilk@student.reading.ac.ukOSK pop up/down animation is stuttery<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Affected version
Fedora 37, Gnome 43.2, Wayland.
<!--
Provide at least the foll...<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Affected version
Fedora 37, Gnome 43.2, Wayland.
<!--
Provide at least the following information:
* Your OS and version
* Affected GNOME Shell version (see https://wiki.gnome.org/Schedule for currently supported versions)
* Does this issue appear in XOrg and/or Wayland
* Does this issue happen without extensions (please follow instructions below)
To properly disable extensions you can use gnome-extensions-app and then restart
your session. Disabling extensions without a restart is not sufficient to rule
out extensions as cause of a bug. If an issue can only be reproduced with a
certain extension, please file a bug report against that extension first.
-->
### Bug summary
Often, the OSK's pop up and down animation feels quite stuttery and jarring.
This is not the case when you drag the keyboard up yourself using the gesture - different animation is used.
<!--
Provide a short summary of the bug you encountered.
-->
### Steps to reproduce
1. Drag the OSK up using the gesture - it is smooth.
2. Press the close OSK button - it often jumps a bit.
3. Also noticeable if the OSK auto pops up from any input box.
<!--
1. Step one
2. Step two
3. ...
-->
### What happened
When playing the preset pop up or pop down animation, it feels jumpy, like it is skipping frames.
<!--
What did GNOME Shell do that was unexpected?
-->
### What did you expect to happen
OSK animation should be smooth up and down, like it is when you manually open it with the gesture and drag it about.
<!--
What did you expect GNOME Shell to do?
-->
### Relevant logs, screenshots, screencasts etc.
<!--
If you have further information, such as technical documentation, logs,
screenshots or screencasts related, please provide them here.
If the bug is a crash, please obtain a stack trace with installed debug
symbols (at least for GNOME Shell and Mutter) and attach it to
this issue following the instructions on
https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces.
-->
[Video of me manually opening the OSK, closing it with the button, then opening the OSK by tapping on the gnome search bar.](/uploads/76c98141183ac639ff08be20b20275c5/Kooha-2023-01-01-02-59-40.mkv)
<!-- Do not remove the following line. -->https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6278OSK auto-open behaviour is inconsistent for nautilus and firefox2023-10-11T02:49:22ZPhilip Wilkp.wilk@student.reading.ac.ukOSK auto-open behaviour is inconsistent for nautilus and firefox<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Affected version
Fedora 37, Gnome 43.2, Wayland.
<!--
Provide at least the foll...<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Affected version
Fedora 37, Gnome 43.2, Wayland.
<!--
Provide at least the following information:
* Your OS and version
* Affected GNOME Shell version (see https://wiki.gnome.org/Schedule for currently supported versions)
* Does this issue appear in XOrg and/or Wayland
* Does this issue happen without extensions (please follow instructions below)
To properly disable extensions you can use gnome-extensions-app and then restart
your session. Disabling extensions without a restart is not sufficient to rule
out extensions as cause of a bug. If an issue can only be reproduced with a
certain extension, please file a bug report against that extension first.
-->
### Bug summary
Most Gnome apps open the OSK immediately when you tap the input box. Nautilus will never open the OSK if you tap the search bar after activating it with the search icon. Also, firefox takes two taps to open the search bar for text input instead of just one, even though the first tap already shows the blinking cursor location line in the address bar.
<!--
Provide a short summary of the bug you encountered.
-->
### Steps to reproduce
<!--
1. Step one
2. Step two
3. ...
-->
For nautilus:
1. open nautilus
2. tap search icon
3. tap search bar (however many times you would like)
4. nothing happens
For firefox:
1. open firefox
2. tap search bar - suggestions box appears, blinky line appears, OSK does not
3. tap search bar again - osk appears as expected.
### What happened
OSK does not appear when the text input boxes were pressed for the first time.
<!--
What did GNOME Shell do that was unexpected?
-->
### What did you expect to happen
OSK should immediately appear when a text input box is pressed (once).
<!--
What did you expect GNOME Shell to do?
-->
### Relevant logs, screenshots, screencasts etc.
<!--
If you have further information, such as technical documentation, logs,
screenshots or screencasts related, please provide them here.
If the bug is a crash, please obtain a stack trace with installed debug
symbols (at least for GNOME Shell and Mutter) and attach it to
this issue following the instructions on
https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces.
-->
<!-- Do not remove the following line. -->https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6277Tapping text input section with (wacom) stylus does not automatically open OSK2023-10-11T02:49:24ZPhilip Wilkp.wilk@student.reading.ac.ukTapping text input section with (wacom) stylus does not automatically open OSK<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Affected version
Fedora 37, Gnome 43.2, Wayland.
<!--
Provide at least the foll...<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Affected version
Fedora 37, Gnome 43.2, Wayland.
<!--
Provide at least the following information:
* Your OS and version
* Affected GNOME Shell version (see https://wiki.gnome.org/Schedule for currently supported versions)
* Does this issue appear in XOrg and/or Wayland
* Does this issue happen without extensions (please follow instructions below)
To properly disable extensions you can use gnome-extensions-app and then restart
your session. Disabling extensions without a restart is not sufficient to rule
out extensions as cause of a bug. If an issue can only be reproduced with a
certain extension, please file a bug report against that extension first.
-->
### Bug summary
Tapping text input boxes with my wacom stylus does not open the OSK. AFAIK, there is no other way to type with a stylus than the OSK.
May be related to #4230, as it may be that wacom styli are not regarded as being a touchscreen input, so the device is not put in/is taken out of touchscreen mode - the mouse cursor appears when you use a stylus. Unsure.
<!--
Provide a short summary of the bug you encountered.
-->
### Steps to reproduce
1. Tap the "Type to search" gnome search box from activities or application view using stylus
2. Nothing happens
OR
1. Tap search bars in settings app using stylus
2. Nothing happens
### What happened
Nothing
<!--
What did GNOME Shell do that was unexpected?
-->
### What did you expect to happen
OSK appears on screen so you can type into it with the stylus.
<!--
What did you expect GNOME Shell to do?
-->
### Relevant logs, screenshots, screencasts etc.
<!--
If you have further information, such as technical documentation, logs,
screenshots or screencasts related, please provide them here.
If the bug is a crash, please obtain a stack trace with installed debug
symbols (at least for GNOME Shell and Mutter) and attach it to
this issue following the instructions on
https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces.
-->
<!-- Do not remove the following line. -->https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6166Gnome 43, wayland from Fedora 37 on tablet, osk on-screen-keyboard does not t...2022-11-30T18:25:23ZLukeOGnome 43, wayland from Fedora 37 on tablet, osk on-screen-keyboard does not type (observed in Thunderbird)<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Affected version
Fedora 37 Workstaation (fresh install)
Wayland
Gnome-Shell 4...<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Affected version
Fedora 37 Workstaation (fresh install)
Wayland
Gnome-Shell 41.3-4.fc37
Thunderbird 102.5.0
### Bug summary
The on screen keyboard is stuck in “suggest a word” mode (lists words above keys), and does not type to screen. AFAIK only “Enter” and “backspace” are relayed.
Issue first discovered in Thunderbird on a Dell Tablet (WACOM Touchscreen).
Freshly installed F37 Workstation.
### Steps to reproduce
Start Thunderbird,
“write” new message,
tap the “message text area” → the on-screen-keyboard does not appear,
pull up OSK (gesture: swipe from bottom up),
focus on “message text area” lost → tap again,
start typing.
Either no output appears, or suggestions are highlighted on OSK.
It looks like every key-touch is immediately backspaced.
### What happened
On screen keyboard did not "type" to text input.
### What did you expect to happen
On screen keyboard type to txt input.
### Relevant logs, screenshots, screencasts etc.
![Screencast_from_2022-11-29_19-38-49](/uploads/f1365882b1f93fa1a30a8c39760f852a/Screencast_from_2022-11-29_19-38-49.webm)
<!-- Do not remove the following line. -->https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6115osk extended mode does not respect keyboard layout2023-10-11T02:49:24ZEsokratesosk extended mode does not respect keyboard layoutMy default keyboard language is german, in gnome console, the extended keyboard layout triggers which is great, but it does it's no longer QWERTZ, but QWERTY instead. The normal mode is fine. See in the following screencast demo:
![Scre...My default keyboard language is german, in gnome console, the extended keyboard layout triggers which is great, but it does it's no longer QWERTZ, but QWERTY instead. The normal mode is fine. See in the following screencast demo:
![Screencast_from_2022-11-19_22-31-37](/uploads/9eea960b436d89afef7b365bf25c68cd/Screencast_from_2022-11-19_22-31-37.webm)https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6114osk related stack traces in log2023-10-11T02:49:23ZEsokratesosk related stack traces in logFollow up from https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6085#note_1597833
Gnome Shell 43.0 Wayland on Ubuntu 22.10, rebuilt with changes from https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2543/
```
Nov 18 21:48:...Follow up from https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6085#note_1597833
Gnome Shell 43.0 Wayland on Ubuntu 22.10, rebuilt with changes from https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2543/
```
Nov 18 21:48:15 pc gnome-shell[9270]: Failed to set the markup of the actor '<unnamed>[<ClutterText>:0x55a2d7c2bec0]': Error on line 1 char 14: “<” is not a valid name
Nov 18 21:48:15 pc gnome-shell[9270]: Failed to set the markup of the actor '<unnamed>[<ClutterText>:0x55a2d8907d60]': Error on line 1 char 14: “<” is not a valid name
Nov 18 21:48:15 pc gnome-shell[9270]: Object .Gjs_ui_keyboard_Keyboard (0x55a2d7b3f7f0), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroye>
Nov 18 21:48:15 pc gnome-shell[9270]: == Stack trace for context 0x55a2d759b7d0 ==
Nov 18 21:48:15 pc gnome-shell[9270]: #0 55a2d9d03d58 i resource:///org/gnome/shell/ui/keyboard.js:1992 (28a99b35af10 @ 10)
Nov 18 21:48:15 pc gnome-shell[9270]: == Stack trace for context 0x55a2d759b7d0 ==
Nov 18 21:48:15 pc gnome-shell[9270]: #0 55a2d9d03d58 i resource:///org/gnome/shell/ui/keyboard.js:1992 (28a99b35af10 @ 16)
Nov 18 21:48:15 pc gnome-shell[9270]: Object .Gjs_ui_keyboard_Keyboard (0x55a2d7b3f7f0), has been already disposed — impossible to set any property on it. This might be caused by the object having been destroyed >
Nov 18 21:48:15 pc gnome-shell[9270]: value "inf" of type 'gfloat' is invalid or out of range for property 'translation-y' of type 'gfloat'
Nov 18 21:48:22 pc gnome-shell[9270]: meta_wayland_pointer_set_focus: assertion 'meta_cursor_tracker_get_pointer_visible (cursor_tracker) || clutter_seat_is_unfocus_inhibited (clutter_seat) || surface == NULL' fa>
Nov 18 21:48:23 pc dbus-daemon[8823]: [session uid=1000 pid=8823] Activating via systemd: service name='org.freedesktop.Tracker3.Miner.Extract' unit='tracker-extract-3.service' requested by ':1.60' (uid=1000 pid=>
Nov 18 21:48:23 pc systemd[1938]: Starting Tracker metadata extractor...
Nov 18 21:48:23 pc dbus-daemon[8823]: [session uid=1000 pid=8823] Successfully activated service 'org.freedesktop.Tracker3.Miner.Extract'
Nov 18 21:48:23 pc systemd[1938]: Started Tracker metadata extractor.
Nov 18 21:48:31 pc gnome-shell[9270]: JS ERROR: Error: Argument descendant may not be null
_onCapturedEvent@resource:///org/gnome/shell/ui/keyboard.js:232:24
Nov 18 21:48:32 pc gnome-shell[9270]: Failed to set the markup of the actor '<unnamed>[<ClutterText>:0x55a2d9ab4b70]': Error on line 1 char 14: “<” is not a valid name
Nov 18 21:48:32 pc gnome-shell[9270]: Failed to set the markup of the actor '<unnamed>[<ClutterText>:0x55a2d9fc0b10]': Error on line 1 char 14: “<” is not a valid name
Nov 18 21:48:40 pc gnome-shell[9270]: Object .Gjs_ui_keyboard_Keyboard (0x55a2d7b3f7f0), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroye>
Nov 18 21:48:40 pc gnome-shell[9270]: Object .Gjs_ui_keyboard_Keyboard (0x55a2d7b3f7f0), has been already disposed — impossible to set any property on it. This might be caused by the object having been destroyed >
Nov 18 21:48:40 pc gnome-shell[9270]: == Stack trace for context 0x55a2d759b7d0 ==
Nov 18 21:48:40 pc gnome-shell[9270]: #0 55a2d9b7f338 i resource:///org/gnome/shell/ui/keyboard.js:1992 (28a99b35af10 @ 10)
Nov 18 21:48:40 pc gnome-shell[9270]: #1 55a2d9b7f298 i resource:///org/gnome/shell/ui/layout.js:526 (16f4e2fcb600 @ 65)
Nov 18 21:48:40 pc gnome-shell[9270]: #2 55a2d9b7f210 i resource:///org/gnome/shell/ui/layout.js:625 (16f4e2fcb970 @ 30)
Nov 18 21:48:40 pc gnome-shell[9270]: #3 55a2d9b7f178 i resource:///org/gnome/shell/ui/layout.js:538 (16f4e2fcb650 @ 129)
Nov 18 21:48:40 pc gnome-shell[9270]: #4 55a2d9b7f0e8 i resource:///org/gnome/shell/ui/layout.js:574 (16f4e2fcb790 @ 32)
Nov 18 21:48:40 pc gnome-shell[9270]: #5 55a2d9b7f018 i self-hosted:1121 (16f4e2f7eec0 @ 432)
Nov 18 21:48:40 pc gnome-shell[9270]: == Stack trace for context 0x55a2d759b7d0 ==
Nov 18 21:48:40 pc gnome-shell[9270]: #0 55a2d9b7f338 i resource:///org/gnome/shell/ui/keyboard.js:1992 (28a99b35af10 @ 16)
Nov 18 21:48:40 pc gnome-shell[9270]: #1 55a2d9b7f298 i resource:///org/gnome/shell/ui/layout.js:526 (16f4e2fcb600 @ 65)
Nov 18 21:48:40 pc gnome-shell[9270]: #2 55a2d9b7f210 i resource:///org/gnome/shell/ui/layout.js:625 (16f4e2fcb970 @ 30)
Nov 18 21:48:40 pc gnome-shell[9270]: #3 55a2d9b7f178 i resource:///org/gnome/shell/ui/layout.js:538 (16f4e2fcb650 @ 129)
Nov 18 21:48:40 pc gnome-shell[9270]: #4 55a2d9b7f0e8 i resource:///org/gnome/shell/ui/layout.js:574 (16f4e2fcb790 @ 32)
Nov 18 21:48:40 pc gnome-shell[9270]: #5 55a2d9b7f018 i self-hosted:1121 (16f4e2f7eec0 @ 432)
Nov 18 21:48:40 pc gnome-shell[9270]: == Stack trace for context 0x55a2d759b7d0 ==
Nov 18 21:48:40 pc gnome-shell[9270]: #0 55a2d9b7f338 i resource:///org/gnome/shell/ui/keyboard.js:1992 (28a99b35af10 @ 10)
Nov 18 21:48:40 pc gnome-shell[9270]: #1 55a2d9b7f298 i resource:///org/gnome/shell/ui/layout.js:526 (16f4e2fcb600 @ 65)
Nov 18 21:48:40 pc gnome-shell[9270]: #2 55a2d9b7f210 i resource:///org/gnome/shell/ui/layout.js:625 (16f4e2fcb970 @ 30)
Nov 18 21:48:40 pc gnome-shell[9270]: #3 55a2d9b7f178 i resource:///org/gnome/shell/ui/layout.js:538 (16f4e2fcb650 @ 129)
Nov 18 21:48:40 pc gnome-shell[9270]: #4 55a2d9b7f0e8 i resource:///org/gnome/shell/ui/layout.js:574 (16f4e2fcb790 @ 32)
Nov 18 21:48:40 pc gnome-shell[9270]: #5 55a2d9b7f018 i self-hosted:1121 (16f4e2f7eec0 @ 432)
Nov 18 21:48:40 pc gnome-shell[9270]: == Stack trace for context 0x55a2d759b7d0 ==
Nov 18 21:48:40 pc gnome-shell[9270]: #0 55a2d9b7f338 i resource:///org/gnome/shell/ui/keyboard.js:1992 (28a99b35af10 @ 16)
Nov 18 21:48:40 pc gnome-shell[9270]: #1 55a2d9b7f298 i resource:///org/gnome/shell/ui/layout.js:526 (16f4e2fcb600 @ 65)
Nov 18 21:48:40 pc gnome-shell[9270]: #2 55a2d9b7f210 i resource:///org/gnome/shell/ui/layout.js:625 (16f4e2fcb970 @ 30)
Nov 18 21:48:40 pc gnome-shell[9270]: #3 55a2d9b7f178 i resource:///org/gnome/shell/ui/layout.js:538 (16f4e2fcb650 @ 129)
Nov 18 21:48:40 pc gnome-shell[9270]: #4 55a2d9b7f0e8 i resource:///org/gnome/shell/ui/layout.js:574 (16f4e2fcb790 @ 32)
Nov 18 21:48:40 pc gnome-shell[9270]: #5 55a2d9b7f018 i self-hosted:1121 (16f4e2f7eec0 @ 432)
Nov 18 21:48:40 pc gnome-shell[9270]: == Stack trace for context 0x55a2d759b7d0 ==
Nov 18 21:48:40 pc gnome-shell[9270]: #0 55a2d9b7f338 i resource:///org/gnome/shell/ui/keyboard.js:1992 (28a99b35af10 @ 10)
Nov 18 21:48:40 pc gnome-shell[9270]: #1 55a2d9b7f298 i resource:///org/gnome/shell/ui/layout.js:528 (16f4e2fcb600 @ 101)
Nov 18 21:48:40 pc gnome-shell[9270]: #2 55a2d9b7f210 i resource:///org/gnome/shell/ui/layout.js:625 (16f4e2fcb970 @ 30)
Nov 18 21:48:40 pc gnome-shell[9270]: #3 55a2d9b7f178 i resource:///org/gnome/shell/ui/layout.js:538 (16f4e2fcb650 @ 129)
Nov 18 21:48:40 pc gnome-shell[9270]: #4 55a2d9b7f0e8 i resource:///org/gnome/shell/ui/layout.js:574 (16f4e2fcb790 @ 32)
Nov 18 21:48:40 pc gnome-shell[9270]: #5 55a2d9b7f018 i self-hosted:1121 (16f4e2f7eec0 @ 432)
Nov 18 21:48:40 pc gnome-shell[9270]: == Stack trace for context 0x55a2d759b7d0 ==
Nov 18 21:48:40 pc gnome-shell[9270]: #0 55a2d9b7f338 i resource:///org/gnome/shell/ui/keyboard.js:1992 (28a99b35af10 @ 16)
Nov 18 21:48:40 pc gnome-shell[9270]: #1 55a2d9b7f298 i resource:///org/gnome/shell/ui/layout.js:528 (16f4e2fcb600 @ 101)
Nov 18 21:48:40 pc gnome-shell[9270]: #2 55a2d9b7f210 i resource:///org/gnome/shell/ui/layout.js:625 (16f4e2fcb970 @ 30)
Nov 18 21:48:40 pc gnome-shell[9270]: #3 55a2d9b7f178 i resource:///org/gnome/shell/ui/layout.js:538 (16f4e2fcb650 @ 129)
Nov 18 21:48:40 pc gnome-shell[9270]: #4 55a2d9b7f0e8 i resource:///org/gnome/shell/ui/layout.js:574 (16f4e2fcb790 @ 32)
Nov 18 21:48:40 pc gnome-shell[9270]: #5 55a2d9b7f018 i self-hosted:1121 (16f4e2f7eec0 @ 432)
Nov 18 21:48:40 pc gnome-shell[9270]: == Stack trace for context 0x55a2d759b7d0 ==
Nov 18 21:48:40 pc gnome-shell[9270]: #0 55a2d9b7f338 i resource:///org/gnome/shell/ui/keyboard.js:1992 (28a99b35af10 @ 10)
Nov 18 21:48:40 pc gnome-shell[9270]: #1 55a2d9b7f298 i resource:///org/gnome/shell/ui/layout.js:528 (16f4e2fcb600 @ 101)
Nov 18 21:48:40 pc gnome-shell[9270]: #2 55a2d9b7f210 i resource:///org/gnome/shell/ui/layout.js:625 (16f4e2fcb970 @ 30)
Nov 18 21:48:40 pc gnome-shell[9270]: #3 55a2d9b7f178 i resource:///org/gnome/shell/ui/layout.js:538 (16f4e2fcb650 @ 129)
Nov 18 21:48:40 pc gnome-shell[9270]: value "inf" of type 'gfloat' is invalid or out of range for property 'translation-y' of type 'gfloat'
Nov 18 21:48:40 pc gnome-shell[9270]: #4 55a2d9b7f0e8 i resource:///org/gnome/shell/ui/layout.js:574 (16f4e2fcb790 @ 32)
Nov 18 21:48:40 pc gnome-shell[9270]: #5 55a2d9b7f018 i self-hosted:1121 (16f4e2f7eec0 @ 432)
Nov 18 21:48:40 pc gnome-shell[9270]: == Stack trace for context 0x55a2d759b7d0 ==
Nov 18 21:48:40 pc gnome-shell[9270]: #0 55a2d9b7f338 i resource:///org/gnome/shell/ui/keyboard.js:1992 (28a99b35af10 @ 16)
Nov 18 21:48:40 pc gnome-shell[9270]: #1 55a2d9b7f298 i resource:///org/gnome/shell/ui/layout.js:528 (16f4e2fcb600 @ 101)
Nov 18 21:48:40 pc gnome-shell[9270]: #2 55a2d9b7f210 i resource:///org/gnome/shell/ui/layout.js:625 (16f4e2fcb970 @ 30)
Nov 18 21:48:40 pc gnome-shell[9270]: #3 55a2d9b7f178 i resource:///org/gnome/shell/ui/layout.js:538 (16f4e2fcb650 @ 129)
Nov 18 21:48:40 pc gnome-shell[9270]: #4 55a2d9b7f0e8 i resource:///org/gnome/shell/ui/layout.js:574 (16f4e2fcb790 @ 32)
Nov 18 21:48:40 pc gnome-shell[9270]: #5 55a2d9b7f018 i self-hosted:1121 (16f4e2f7eec0 @ 432)
Nov 18 21:48:40 pc gnome-shell[9270]: Object .Gjs_ui_keyboard_Keyboard (0x55a2d8b64bb0), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroye>
Nov 18 21:48:40 pc gnome-shell[9270]: Object .Gjs_ui_keyboard_Keyboard (0x55a2d8b64bb0), has been already disposed — impossible to set any property on it. This might be caused by the object having been destroyed >
Nov 18 21:48:40 pc gnome-shell[9270]: value "inf" of type 'gfloat' is invalid or out of range for property 'translation-y' of type 'gfloat'
Nov 18 21:48:40 pc gnome-shell[9270]: Object .Gjs_ui_keyboard_Keyboard (0x55a2d7b3f7f0), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroye>
Nov 18 21:48:40 pc gnome-shell[9270]: Object .Gjs_ui_keyboard_Keyboard (0x55a2d7b3f7f0), has been already disposed — impossible to set any property on it. This might be caused by the object having been destroyed >
Nov 18 21:48:40 pc gnome-shell[9270]: value "inf" of type 'gfloat' is invalid or out of range for property 'translation-y' of type 'gfloat'
Nov 18 21:48:40 pc gnome-shell[9270]: Object .Gjs_ui_keyboard_Keyboard (0x55a2d8b64bb0), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroye>
Nov 18 21:48:40 pc gnome-shell[9270]: Object .Gjs_ui_keyboard_Keyboard (0x55a2d8b64bb0), has been already disposed — impossible to set any property on it. This might be caused by the object having been destroyed >
Nov 18 21:48:40 pc gnome-shell[9270]: value "inf" of type 'gfloat' is invalid or out of range for property 'translation-y' of type 'gfloat'
Nov 18 21:48:40 pc gnome-shell[9270]: Failed to set the markup of the actor '<unnamed>[<ClutterText>:0x55a2d9edb6b0]': Error on line 1 char 14: “<” is not a valid name
Nov 18 21:48:40 pc gnome-shell[9270]: Failed to set the markup of the actor '<unnamed>[<ClutterText>:0x55a2da11d440]': Error on line 1 char 14: “<” is not a valid name
```https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6094osk touchscreen gesture steals window focus2023-10-11T02:49:24ZEsokratesosk touchscreen gesture steals window focus<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Affected version
<!--
Provide at least the following information:
* Your OS an...<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Affected version
<!--
Provide at least the following information:
* Your OS and version
* Affected GNOME Shell version (see https://wiki.gnome.org/Schedule for currently supported versions)
* Does this issue appear in XOrg and/or Wayland
-->
All versions of Gnome 4x so far.
### Bug summary
Gnome shell 43 Wayland session.
Not sure if this should be reported here or against mutter, please feel free to reassign accordingly.
Assume the following setting: current window in focus is not maximized, there is another maximized window behind it.
When bringing up the osk via bottom up gesture, the current window in focus disappears behind the background window.
### Steps to reproduce
1. Place small window in front of maximized window
2. Bring up osk via bottom up gesture
### What happened
Small window disappeared behind maximized window.
<!--
What did GNOME Shell do that was unexpected?
-->
### What did you expect to happen
<!--
What did you expect GNOME Shell to do?
-->
Small window should stay in focus.
### Screencast
Please find a video demonstration here: https://youtube.com/shorts/TrkyqvAkV5o
As you can see the console window disappears behind Gnome Software.
<!--
If you have further information, such as technical documentation, logs,
screenshots or screencasts related, please provide them here.
If the bug is a crash, please obtain a stack trace with installed debug
symbols (at least for GNOME Shell and Mutter) and attach it to
this issue following the instructions on
https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces.
-->
### Why this is important
There are still many applications that do not bring up the osk on their own due to text-input-unstable protocol missing in their toolkit (e.g. electron or qt based apps), thus in practice one still needs to invoke the keyboard manually. This issue makes the experience considerably less practical.
<!-- Do not remove the following line. -->https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6009[OSK] Ibus typing booster appears sometimes instead of on-screen keyboard2023-10-11T02:49:24Z0unknwn[OSK] Ibus typing booster appears sometimes instead of on-screen keyboard<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Affected version
<!--
Provide at least the following information:
* Your OS an...<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Affected version
<!--
Provide at least the following information:
* Your OS and version
* Affected GNOME Shell version (see https://wiki.gnome.org/Schedule for currently supported versions)
* Does this issue appear in XOrg and/or Wayland
-->
* Fedora 37 Workstation
* Gnome 43.1 (Wayland)
### Bug summary
<!--
Provide a short summary of the bug you encountered.
-->
When I have the on-screen keyboard activated sometimes it does not pop up when clicking a text field, but instead Ibus typing booster appears with suggestions. It sometimes even appears after the on-screen keyboard is disabled.
### Steps to reproduce
1. Activate on-screen keyboard
2. Click different text fields
3. When the on-screen keyboard does not pop up, type a letter with your physical keyboard
### What happened
Instead of the on-screen keyboard the ibus typing booster suggestions appear (which are quite helpful sometimes). Sometimes it appears also after disabling the OSK. It happens very randomly and is quite annoying. You can make it disappear by restarting ibus with `ibus restart`.
### What did you expect to happen
The on-screen keyboard should pop up every time not just the ibus typing booster.
### Relevant logs, screenshots, screencasts etc.
I am not the only one experiencing this:
- https://www.reddit.com/r/Fedora/comments/ycl8zs/what_tool_is_this_word_suggestionautocorrect_it/
- https://www.reddit.com/r/Fedora/comments/z2eyqu/fedora_37_a_few_concern_things_i_wish_i_knew/
- https://www.reddit.com/r/Fedora/comments/z73y1k/how_is_this_text_suggestion_turned_onoff/
<!--
If you have further information, such as technical documentation, logs,
screenshots or screencasts related, please provide them here.
If the bug is a crash, please obtain a stack trace with installed debug
symbols (at least for GNOME Shell and Mutter) and attach it to
this issue following the instructions on
https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces.
-->
<!-- Do not remove the following line. -->