Bug 2498492 - KDE starting ibus-typing-booster by default
Summary: KDE starting ibus-typing-booster by default
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: ibus-typing-booster
Version: 44
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Mike FABIAN
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-07-09 12:49 UTC by vorlmaldor
Modified: 2026-08-11 07:36 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)
Enabling OSK on gdm (47.50 KB, image/png)
2026-07-14 14:13 UTC, Mike FABIAN
no flags Details
OSK used on gdm (197.84 KB, image/png)
2026-07-14 14:15 UTC, Mike FABIAN
no flags Details
updates that were completed before the issue started (19.97 KB, text/plain)
2026-07-30 19:39 UTC, vorlmaldor
no flags Details

Description vorlmaldor 2026-07-09 12:49:42 UTC
Do you have any idea how hard it is to type a password in when you have ibus-typing-booster enabled by default on a PC? 

The descision to include this is so far beyond stupid I just can't even.  You set your keyboard during install time, why in the world would you enforce this absulote garbage on everyone? 

typing a password with predictive text popping up is a privacy nightmare. What happened to security?  

You could let people select their device type during install so that we aren't all forced into this level of stupid. 

If feels like you have these issues: 
Blind Probing: The installer only checks generic hardware flags (like looking for a battery indicator or an I2C touchscreen controller).'

False Positives: If you are using a modern desktop motherboard with Bluetooth, or a monitor with a built-in USB controller that registers as "touch capable," Fedora assumes you are on a mobile-adjacent device.Aggressive Packages: 

Because it blindly flags your PC as a "mobile device," it forces the ibus-typing-booster mobile keyboard packages to run during the initial user setup, completely ignoring that you are sitting at a desk typing with a physical 104-key plastic keyboard.

You are better than this. You don't force poor UI design just because you are to lazy to add a device selection screen. 

Reproducible: Always

Steps to Reproduce:
1.install fedora 44
2.try to type a password 
3.get frustrated because stupid descisions were made
Actual Results:
I had serious issues trying to get a nominally secure password to login. 

Expected Results:
I expect a PC to act like a PC and not get moronic tablet defaults pushed onto a PC. 

At the absolute least I would expect an extremely visible toggle on the login page, but you couldn't even be bothered to do that. 

Additional Information:
The fact that this isn't even easily disabled shows just how out of touch you are with reality. You should be completely ashamed of this level of stupid.

Comment 1 Jens Petersen 2026-07-13 08:24:28 UTC
I have no idea what you are doing - and your tone is quite inappropriate.

Typing Booster should never be a default input source unless you make it one.
Which image did you install?

Comment 2 vorlmaldor 2026-07-13 16:25:57 UTC
I did a default install of fedora 44 kde, That's it. I didn't choose special packages I didn't install random software. This happened right from the base install.  

 ibus-typing-booster was installed automatically as part of the Fedora KDE installation—not manually or as an
  application dependency.

  Verified chain:

  - On April 22, 2026, the original Fedora image build installed @kde-desktop-environment.
  - That environment includes Fedora’s input-methods package group.
  - ibus-typing-booster is a default package in input-methods.
  - DNF recorded its installation reason as Group.

then on july 9 I did a system update and thats when ibus typing booster somehow got enabled.   Something as intrusive as that should have an easy disable right on the login manager, and in the base ui under keyboard management.  

after a bunch of looking, seems Fedora’s graphical-session startup started IBus automatically.

Comment 3 Jens Petersen 2026-07-13 17:20:56 UTC
(In reply to vorlmaldor from comment #2)
>   - On April 22, 2026, the original Fedora image build installed
> @kde-desktop-environment.
>   - That environment includes Fedora’s input-methods package group.
>   - ibus-typing-booster is a default package in input-methods.

Right it is installed by default in most Fedora editions/spins.

> then on july 9 I did a system update and thats when ibus typing booster
> somehow got enabled.

That should not be the case: ie that is not supposed to happen.

>   Something as intrusive as that should have an easy
> disable right on the login manager, and in the base ui under keyboard
> management.  
> 
> after a bunch of looking, seems Fedora’s graphical-session startup started
> IBus automatically.

I am not sure what happened but sounds like something changed on the KDE or ibus side perhaps.

If you know what versions of kde/plasma and ibus/ibus-typing-booster changed that might be helpful information.

We will try to have a look anyway, thank you for reporting this.

Comment 4 Derek Enz 2026-07-13 18:02:55 UTC
What version of KDE Plasma?

Comment 5 Mike FABIAN 2026-07-14 12:20:06 UTC
vorlmaldor> typing a password with predictive text popping up is a privacy nightmare. What happened to security?

Where exactly are you typing that password?

Comment 6 Mike FABIAN 2026-07-14 12:38:14 UTC
Is that problem with typing the password on the display manager? You write “I had serious issues trying to get a nominally secure password to login”. If the problem is during login, that sounds like it happens in the display manager. If so, which display manager is used? Is it gdm? lightdm? sddm? Something else?

Comment 7 vorlmaldor 2026-07-14 12:50:46 UTC
during login 

plasma-login-manager-6.7.2-1.fc44

Comment 8 Mike FABIAN 2026-07-14 14:10:09 UTC
I tried plasma-login-manager now, no ibus process is running while I the plasma-login-manager screen is shown.

mfabian@Fedora-Workstation-Live-44-20260:~$ sudo systemctl enable plasmalogin --now 
Created symlink '/etc/systemd/system/display-manager.service' → '/usr/lib/systemd/system/plasmalogin.service'.
mfabian@Fedora-Workstation-Live-44-20260:~$ ps aux | grep ibus
mfabian    11144  0.0  0.0 231444  2540 pts/0    S+   15:59   0:00 grep --color=auto ibus
mfabian@Fedora-Workstation-Live-44-20260:~$ 

Is an ibus process running for you?

A few minutes ago I used gdm instead of plasmalogin and ibus is running while gdm is shown. But there I had no problems either. But default, ibus is running for the `gdm-greeter-2` user, **but** ibus-typing-booster is not running. If I enable the OSK (on-screen-keyboard) by using the accessibility button at the lower right corner, then ibus-typing-booster is started. But that still doesn't cause any problems during password input as input methods are disabled on the password input field.

Comment 9 Mike FABIAN 2026-07-14 14:13:46 UTC
Created attachment 2148595 [details]
Enabling OSK on gdm

I can enable OSK on gdm as shown on this screenshot.
This enables typing booster for use by OSK, but still causes no problems with password input as input methods are disabled on the password field.

Is some on-screen-keyboard used on you plasmalogin display manager? I don't get that.

Comment 10 Mike FABIAN 2026-07-14 14:15:23 UTC
Created attachment 2148596 [details]
OSK used on gdm

After enabling OSK, I can use it on gdm. Typing booster is running in the background, but not used on the password field.

Comment 11 Mike FABIAN 2026-07-14 14:16:35 UTC
(In reply to vorlmaldor from comment #7)
> during login 
> 
> plasma-login-manager-6.7.2-1.fc44

Do you see some on-screen-keyboard during login? Something similar to the OSK used by Gnome?

Comment 12 Jens Petersen 2026-07-15 09:31:03 UTC
A screenshot/photo would be helpful indeed.

Comment 13 Mike FABIAN 2026-07-20 07:21:50 UTC
Can you help us a bit more to figure out what actually happens? Add more detailed information, screenshots, videos, whatever ...
Currently we cannot reproduce this.

Comment 14 vorlmaldor 2026-07-30 19:39:03 UTC
Created attachment 2153057 [details]
updates that were completed before the issue started

updates that were completed before the issue started

Comment 15 vorlmaldor 2026-07-30 19:40:43 UTC
missed the emails sorry. These were the updates done right before the issue. I can't give screenshots right now, but I can reinstall and enable that package but screenshots are still hard since its in the login screen.

Comment 16 Jens Petersen 2026-07-31 08:06:41 UTC
If it is possible got you to take a screenshot with your phone and attach it here, that would be helpful.

Actually we were wondering if it could be the new long-press feature in KDE/qt perhaps.

Comment 17 Mike FABIAN 2026-08-11 07:36:59 UTC
(In reply to vorlmaldor from comment #15)
> missed the emails sorry. These were the updates done right before the issue.
> I can't give screenshots right now, but I can reinstall and enable that
> package but screenshots are still hard since its in the login screen.

Can you still reproduce it?


Note You need to log in before you can comment on or make changes to this bug.