https://bugs.kde.org/show_bug.cgi?id=494476
Tarulia <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #7 from Tarulia <[email protected]> --- Sorry for the late reply... I saw the notification and immediately forgot about it. Anyway, I tried pulling the logs from journalctl, but > journalctl -b -u kglobalacceld yielded "No entries", not sure why because I can see kglobalacceld entries when searching manually... So yeah, I used grep instead, the log file is attached. There are actually two, because this issue is getting weirder by the minute. Observations in both logs: 1. The shortcut is registered: > Jan 18 02:29:57 fedora sddm-helper-start-wayland[1636]: > "kf.globalaccel.kglobalacceld: Registering key \"Meta+E\" for > \"org.kde.dolphin.desktop\" : \"_launch\"\n" and then unregistered: > Jan 18 02:30:06 fedora sddm-helper-start-wayland[1636]: > "kf.globalaccel.kglobalacceld: Unregistering key \"Meta+E\" for > \"org.kde.dolphin.desktop\" : \"_launch\" […] 2. Both as you can see are logged from "sddm-helper-start-wayland", but I am running an X11 session. 3. The shortcut is never registered again (4. There is quite a lot of Unregistering and Registering going on after that) The first log file (kglobalacceld.CUshortcut.log) is with my Custom shortcut loaded and functioning. I didn't see the default in the logs (after the Unregister), so I figured maybe it's not loaded when the Custom shortcut is. So I deleted my Custom shortcut, and noticed the Default shortcut WAS listed, but not active. So I checked it, applied, then rebooted again. The second log file (kglobalacceld.NOshortcut.log) is from after the second reboot. Again I can see the Register and Unregister, but no second Register either. Looking at the system settings, the default shortcut listing is now also missing again. I am somewhat confused how the shortcut had not been loaded in the first log, but it still showed up in the system settings, even if it was inactive. I uploaded the kglobalshortcutsrc because it is quite long. This is after adding the custom shortcut again. -- You are receiving this mail because: You are watching all bug changes.
