[systemsettings] [Bug 420054] Keyboard kded module causes hang after switching back from virtual console
https://bugs.kde.org/show_bug.cgi?id=420054 [email protected] changed: What|Removed |Added CC||[email protected] --- Comment #35 from [email protected] --- I have experienced the same issue on Debian 12, with plasma 5.27.5. I can confirm that disabling the keyboard daemon fixed it for me. An interesting thing to add: `gqrx` can also trigger this. I have some notes here: https://discuss.kde.org/t/plasma-takes-over-a-minute-to-load/10684/24 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420054] Keyboard kded module causes hang after switching back from virtual console
https://bugs.kde.org/show_bug.cgi?id=420054 Beau changed: What|Removed |Added CC||[email protected] --- Comment #34 from Beau --- Disabling the daemon fixed my issues with Xorg breaking after switching to a vt from kde as of this comments date. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420054] Keyboard kded module causes hang after switching back from virtual console
https://bugs.kde.org/show_bug.cgi?id=420054 Zach changed: What|Removed |Added CC||[email protected] --- Comment #33 from Zach --- I believe I'm experiencing something similar with a USB keyboard. This appears to happen after a suspend/resume because all the USB devices are re-detected, but also happens whenever I plugin in a keyboard. The laptop keyboard also stops working when a USB keyboard is plugged in. Switching to virtual console and back works with both keyboards while plasma is hung. Keyboard events seem to buffer, because after some period of time (1m?), the keyboard starts working again and all of the keypresses that were pressed while frozen all replay at once, followed by a brief pause and an error `kded5[1067]: org.kde.kcm_keyboard: Failed with return code: 1`. As mentioned in this post, disabling the keyboard background service and re-plugging the USB keyboard works as expected. Intel graphics, i915 chipset. If this is unrelated, let me know and I can file a new issue. This has been quite a chore to track down, but worth creating a bugs account for. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420054] Keyboard kded module causes hang after switching back from virtual console
https://bugs.kde.org/show_bug.cgi?id=420054 --- Comment #32 from QkiZ --- (In reply to QkiZ from comment #30) > I think I found what is caused the problem. First I renamed .Xmodmap to > something else. Then I removed ibus from the system. After restarting of > system, I enabled Keyboard daemon in Background Services. Now I don't have > lags during login to my account and when I'm switching between virtual > console and KDE. But if I rename .Xmodmap back problem still persists. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420054] Keyboard kded module causes hang after switching back from virtual console
https://bugs.kde.org/show_bug.cgi?id=420054 --- Comment #31 from QkiZ --- Additionally, I installed fcitx but I'm not sure if I really need it. I'm using only one keyboard layout. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420054] Keyboard kded module causes hang after switching back from virtual console
https://bugs.kde.org/show_bug.cgi?id=420054 QkiZ changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #30 from QkiZ --- I think I found what is caused the problem. First I renamed .Xmodmap to something else. Then I removed ibus from the system. After restarting of system, I enabled Keyboard daemon in Background Services. Now I don't have lags during login to my account and when I'm switching between virtual console and KDE. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420054] Keyboard kded module causes hang after switching back from virtual console
https://bugs.kde.org/show_bug.cgi?id=420054 --- Comment #29 from QkiZ --- (In reply to Fabian Vogt from comment #28) > All user processes except for the essential ones like the terminal you're > running and ksmserver. You might be able to find the culprit(s) by > monitoring the CPU usage of processes when you run xmodmap. There are a lot of processes to test. This takes a lot of time. But will try to figure out which one is causing trouble. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420054] Keyboard kded module causes hang after switching back from virtual console
https://bugs.kde.org/show_bug.cgi?id=420054 Fabian Vogt changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #28 from Fabian Vogt --- (In reply to QkiZ from comment #26) > (In reply to Fabian Vogt from comment #25) > > Each xmodmap entry triggers an x11/xkb map change notification to all > > applications, so the question is which one processes them that slowly. > > kglobalaccel5 is the usual candidate, can you re-test whether this still > > happens if kglobalaccel5 is not running? If yes, the easiest option is > > probably to kill processes one by one and check whether that fixed it... > > I killed kglobalaccel5 and then run xmodmap and it still happens. Which > processes do you mean? All user processes except for the essential ones like the terminal you're running and ksmserver. You might be able to find the culprit(s) by monitoring the CPU usage of processes when you run xmodmap. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420054] Keyboard kded module causes hang after switching back from virtual console
https://bugs.kde.org/show_bug.cgi?id=420054 --- Comment #27 from galdera --- Hello Could you please tell us which keyboard customization are you using? >From the log I see: org.kde.kcm_keyboard: Skipping empty shortcut for "pl" -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420054] Keyboard kded module causes hang after switching back from virtual console
https://bugs.kde.org/show_bug.cgi?id=420054 --- Comment #26 from QkiZ --- (In reply to Fabian Vogt from comment #25) > Each xmodmap entry triggers an x11/xkb map change notification to all > applications, so the question is which one processes them that slowly. > kglobalaccel5 is the usual candidate, can you re-test whether this still > happens if kglobalaccel5 is not running? If yes, the easiest option is > probably to kill processes one by one and check whether that fixed it... I killed kglobalaccel5 and then run xmodmap and it still happens. Which processes do you mean? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420054] Keyboard kded module causes hang after switching back from virtual console
https://bugs.kde.org/show_bug.cgi?id=420054 --- Comment #25 from Fabian Vogt --- (In reply to QkiZ from comment #24) > >Whether the issue appears when you run the xmodmap command manually, outside > >of any autostart. > Yes. I didn't notice this before but when I'm running xmodmap manually > Plasma hangs for 15-30 seconds too. Each xmodmap entry triggers an x11/xkb map change notification to all applications, so the question is which one processes them that slowly. kglobalaccel5 is the usual candidate, can you re-test whether this still happens if kglobalaccel5 is not running? If yes, the easiest option is probably to kill processes one by one and check whether that fixed it... -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420054] Keyboard kded module causes hang after switching back from virtual console
https://bugs.kde.org/show_bug.cgi?id=420054 QkiZ changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #24 from QkiZ --- >Whether the issue appears when you run the xmodmap command manually, outside >of any autostart. Yes. I didn't notice this before but when I'm running xmodmap manually Plasma hangs for 15-30 seconds too. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420054] Keyboard kded module causes hang after switching back from virtual console
https://bugs.kde.org/show_bug.cgi?id=420054 Fabian Vogt changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #23 from Fabian Vogt --- (In reply to QkiZ from comment #22) > I'm not sure what you mean by asking > > Does this happen with just "/usr/bin/xmodmap /home/qkiz/.Xmodmap"? > The problem persists no matter if I run xmodmap on autostart or not. Whether the issue appears when you run the xmodmap command manually, outside of any autostart. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420054] Keyboard kded module causes hang after switching back from virtual console
https://bugs.kde.org/show_bug.cgi?id=420054 QkiZ changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420054] Keyboard kded module causes hang after switching back from virtual console
https://bugs.kde.org/show_bug.cgi?id=420054 --- Comment #22 from QkiZ --- > You mean you disabled xmodmap from autostart? Yes I'm not sure what you mean by asking > Does this happen with just "/usr/bin/xmodmap /home/qkiz/.Xmodmap"? The problem persists no matter if I run xmodmap on autostart or not. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420054] Keyboard kded module causes hang after switching back from virtual console
https://bugs.kde.org/show_bug.cgi?id=420054 Fabian Vogt changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #21 from Fabian Vogt --- (In reply to QkiZ from comment #20) > I'm using xmodmap to remap some keys on my laptop but I disabled it on > autostart and it's doesn't change anything. When keyboard daemon is enabled > issue still persists. You mean you disabled xmodmap from autostart? The keyboard daemon calls xmodmap itself, so that won't have any effect. Please answer to: > Does this happen with just "/usr/bin/xmodmap /home/qkiz/.Xmodmap"? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420054] Keyboard kded module causes hang after switching back from virtual console
https://bugs.kde.org/show_bug.cgi?id=420054 --- Comment #20 from QkiZ --- I'm using xmodmap to remap some keys on my laptop but I disabled it on autostart and it's doesn't change anything. When keyboard daemon is enabled issue still persists. I don't know why this appears in logs: lut 01 00:14:05 drag0n dbus-daemon[7769]: [session uid=1000 pid=7769] Activating service name='org.gnome.ScreenSaver' requested by ':1.253' (uid=1000 pid=57873 comm="/usr/lib/x86_64-linux-gnu/notify-osd " label="unconfined") Gnome-screensaver is not installed. It looks like notify-osd is trying to reach gnome-screensaver. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420054] Keyboard kded module causes hang after switching back from virtual console
https://bugs.kde.org/show_bug.cgi?id=420054 --- Comment #19 from Fabian Vogt --- Does this happen with just "/usr/bin/xmodmap /home/qkiz/.Xmodmap"? lut 01 00:14:05 drag0n dbus-daemon[7769]: [session uid=1000 pid=7769] Activating service name='org.gnome.ScreenSaver' requested by ':1.253' (uid=1000 pid=57873 comm="/usr/lib/x86_64-linux-gnu/notify-osd " label="unconfined") indicates that you have some daemon running which starts the gnome screensaver and doesn't appear to be compatible with Plasma. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420054] Keyboard kded module causes hang after switching back from virtual console
https://bugs.kde.org/show_bug.cgi?id=420054 --- Comment #18 from QkiZ --- > Does this happen all the time when you switch VTs? Can you trigger the issue > with "kded5 --replace"? Can you still trigger the issue after "killall > kglobalaccel5"? This happens every time I switch back from the virtual console. After "kded5 --replace" whole Plasma freeze like after switching from the virtual console. After some time it's unblocking itself. Here is the log from the console: kf.kded: Couldn't register name "org.kde.kcookiejar5" with DBUS - another process owns it already! kcm_touchpad: Using X11 backend Width: 1084 height: 554 Approx. resX: 12 resY: 11 Touchpad resolution: x: 31 y: 31 Final resolution x: 31 y: 31 bluedevil: Created Installing the delayed initialization callback. kf.coreaddons: "Could not load plugin from colord: Biblioteka współdzielona niedostępna." kf.kded: found kded module "colord" by prepending 'kded_' to the library path, please fix your metadata. Using XRANDR extension 1.3 or greater. 7 Yes, this happens after "killall kglobalaccel5" -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420054] Keyboard kded module causes hang after switching back from virtual console
https://bugs.kde.org/show_bug.cgi?id=420054
QkiZ changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO |---
--- Comment #17 from QkiZ ---
Here is a journal https://pastebin.com/4ucR34NE
Here is a kded.log https://pastebin.com/N01naPfv
I think this one should be most interesting:
kf.globalaccel: Failed to get dbus path for component "KDE Keyboard Layout
Switcher" QDBusError("org.freedesktop.DBus.Error.NoReply", "Did not receive a
reply. Possible causes include: the remote application did not send a reply,
the message bus security policy blocked the reply, the reply timeout expired,
or the network connection was broken.")
This is related to Keyboard Daemon.
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 420054] Keyboard kded module causes hang after switching back from virtual console
https://bugs.kde.org/show_bug.cgi?id=420054 Fabian Vogt changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #16 from Fabian Vogt --- Please upload the journal or whereever plasma logs to on your system. There are probably device unplug/plug events triggered by VT switching. Does this happen all the time when you switch VTs? Can you trigger the issue with "kded5 --replace"? Can you still trigger the issue after "killall kglobalaccel5"? Please also run QT_LOGGING_RULES=*.debug=true kded5 --replace |& tee kded.log, then trigger the issue and attach the created logfile. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420054] Keyboard kded module causes hang after switching back from virtual console
https://bugs.kde.org/show_bug.cgi?id=420054 Nate Graham changed: What|Removed |Added Component|generic-performance |kcm_keyboard Summary|Hang after switch back from |Keyboard kded module causes |virtual console |hang after switching back ||from virtual console Version|5.16.5 |5.23.5 CC||[email protected], ||[email protected] Product|plasmashell |systemsettings Target Milestone|1.0 |--- --- Comment #15 from Nate Graham --- Thanks, that's helpful. -- You are receiving this mail because: You are watching all bug changes.
