Bug 2192354 - no keyboard in certain applications
Summary: no keyboard in certain applications
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: ibus
Version: 38
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: fujiwara
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-05-01 15:34 UTC by Daniel
Modified: 2023-05-02 14:41 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-02 14:41:46 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Daniel 2023-05-01 15:34:34 UTC
Description of problem: Keyboard works in some applications (gnome desktop environment) like terminal windows etc. but does not in other applications. For example, if trying to open the firefox browser ther is no access to it with my keyboard. It says:

IBUS-WARNING **: 17:18:05.683: Events queue growing too big, will start to drop.
[Parent 5451, Main Thread] WARNING: Events queue growing too big, will start to drop.: 'glib warning', file /builddir/bu
ild/BUILD/firefox-112.0.1/toolkit/xre/nsSigHandlers.cpp:167

Same result if opening brave browser:

[5921:5921:0501/171833.719481:ERROR:chrome_browser_cloud_management_controller.cc(162)] Cloud management controller init
ialization aborted as CBCM is not enabled.
WARNING: radv is not a conformant Vulkan implementation, testing use only.

(brave:5921): IBUS-WARNING **: 17:18:33.872: Unable to connect to ibus

The same result if opening evolution email client. This worked perfectly until upgrading from Fedora 37 to 38 and on any fedora versions before. It makes my machine unusable. Now writing from a notebook, there no such errors.

Output from inxi -G:

Graphics:
  Device-1: AMD Cape Verde XT [Radeon HD 7770/8760 / R7 250X] driver: amdgpu
    v: kernel
  Display: x11 server: X.Org v: 1.20.14 with: Xwayland v: 22.1.9 driver: X:
    loaded: amdgpu unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu
    resolution: 1920x1200~60Hz
  API: OpenGL v: 4.6 Mesa 23.0.2 renderer: AMD Radeon HD 7700 Series (verde
    LLVM 16.0.1 DRM 3.49 6.2.13-300.fc38.x86_64)

I'm really not sure what component caused these errors. And again, the system worked perfectly on all fedora versions before upgrade to 38.

Comment 1 Daniel 2023-05-01 16:18:28 UTC
When starting firefox as root, I do have keyboard access to the firefox windows, can type in stuff etc.

Comment 2 Daniel 2023-05-01 19:14:28 UTC
After reboot error still exists. I automatically log in an unprivileged user. It worked for some time when loggin out and in again, but the error returned. Apps like firefox or evolution that once worked in that session do not accept keyboard input after some time. 
Looked at the journal and saw some gdm related messages like:

Gdm: GdmDisplay: Session never registered, failing
Gdm: Failed to list cached users: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable

After restarting gdm (systemctl restart gdm.service) apps like firefox, evolution, evince etc. where accessible again and accepted keyboard input.
If some further information needed just ask. Sorry for bothering.

Comment 3 fujiwara 2023-05-01 23:45:23 UTC
I cannot reproduce your problem.
Which desktop do you use? GNOME Wayland?
Can you reproduce your problem with a new user account instead of the current user account?

Comment 4 Daniel 2023-05-02 14:41:46 UTC
It's a GNOME session with x11 server: X.Org v: 1.20.14 with: Xwayland v: 22.1.9 driver: X:loaded: amdgpu (see inxi -G output above).
Think I have found the source of it all. I wrote a little script which erased my ~/.cache directory during a running session. This was fine for all fedora versions but doesn't work for fedora 38. I've changed the script, and the error didn't appear again. All ibus messages disappeared as well. So if this is finally the root of all evil, then it's not a bug at all but a self-inflicted injury. Sorry for bothering.


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