Created attachment 174645 [details] Screenshot of the Dolphin Shortcuts SUMMARY For a couple years I had manually bound Dolphin's shortcut to Meta+E. While debugging this on the KDE Matrix channel recently I was informed that this is actually the default shortcut now (fairly certain it used to be Meta+D or something else). However, in my system settings, there is no default shortcut. Up until now I had just manually bound it. Since my upgrade to Fedora 40 KDE (I reinstalled, preserving /home), the keybind won't stick anymore though. About half the time after reboot the keybind is gone. When reassigning the keybind, there is no notification of it being used elsewhere, and after applying it also immediately works perfectly fine. Until again I reboot and either it sticks or it does not. It seems entirely random whether it sticks or not, but I'd say it's about half the time. STEPS TO REPRODUCE 1. Open System Settings > Keyboard > Shortcuts > Dolphin 2. Check the "default" shortcut listed. For me there is none. 3. Bind a custom keybind: Meta+E and Apply. 4. Reboot the system, check 1-2 again. OBSERVED RESULT Meta+E now works, but after the reboot the keybind is gone about half the time. EXPECTED RESULT It should show and use the default keybind without having to manually bind it. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 40 KDE KDE Plasma Version: 6.2.0 (yes I waited for the version :D) KDE Frameworks Version: 6.6.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION As noted above we already debugged this a little on the KDE Matrix channel (conversation was on 01 Oct 2024). We went through a few things: Checking the system desktop file: grep Meta /usr/share/applications/org.kde.dolphin.desktop X-KDE-Shortcuts=Meta+E Making sure I don't have a local one overriding it: ls .local/share/applications | grep dolphin ✘ Making sure there are no conflicting files: grep "Meta+E" /usr/share/applications -R /usr/share/applications/org.kde.plasma-systemmonitor.desktop:X-KDE-Shortcuts=Meta+Esc /usr/share/applications/org.kde.dolphin.desktop:X-KDE-Shortcuts=Meta+E Checking the kglobalaccel file: grep Meta /usr/share/kglobalaccel/org.kde.dolphin.desktop X-KDE-Shortcuts=Meta+E stat /usr/share/kglobalaccel/org.kde.dolphin.desktop File: /usr/share/kglobalaccel/org.kde.dolphin.desktop -> /usr/share/applications/org.kde.dolphin.desktop I then noticed I had a kglobalaccelrc file in my local applications: ~/.local/share/applications cat kglobalaccelrc [Desktop Entry] NoDisplay=true ~/.local/share/applications stat kglobalaccelrc File: kglobalaccelrc Size: 31 Blocks: 8 IO Block: 4096 regular file Device: 253,2 Inode: 17195523 Links: 1 Access: (0600/-rw-------) Uid: ( 1000/ tarulia) Gid: ( 1000/ tarulia) Context: unconfined_u:object_r:data_home_t:s0 Access: 2024-10-01 17:51:18 +0200 Modify: 2022-04-11 02:10:39 +0200 Change: 2024-08-19 13:47:47 +0200 Birth: 2022-04-11 02:10:39 +0200 I don't know where it came from but since it never caused issues for years it shouldn't be related, nevertheless I went ahead and renamed the file as suggested: ls ~/.local/share/applications | grep kglobal kglobalaccelrc~ But that didn't help either.
I'm the person who debugged this with Tarulia and I'm stuck at this point. David, any ideas?
Is there another dolphin desktop file in /usr/local/share/applications? What do you see if you run cat ~/.config/kglobalshortcutsrc | grep -i "Meta+E" -C5
(In reply to fanzhuyifan from comment #2) > Is there another dolphin desktop file in /usr/local/share/applications? No: ls /usr/local/share/applications mimeinfo.cache > What do you see if you run > cat ~/.config/kglobalshortcutsrc | grep -i "Meta+E" -C5 Nothing either: cat ~/.config/kglobalshortcutsrc | grep -i "Meta+E" -C5 ✘ However, I just tried the Shortcut again and it just... miraculously works? And checking the Shortcuts settings there is now a Default shortcut? I'm honestly confused... Only thing that changed was that I got some more updates last night and the KDE Gear 24.08.1 update was among them, including Dolphin. Not sure if it's related to that but it's the only thing that changed...
OK... interesting. So today after booting up, I have yet again no default shortcut. So I guess my initial report was slightly off. I thought that my custom shortcut sometimes stuck and sometimes didn't, but instead it appears that it just so happened to load the default shortcut and since they are the same it just worked. I honestly never thought to check if my custom shortcut is active or the default one. That would also explain the Custom Shortcut going away though. When the default shortcut loads (like last boot), it probably overrides the custom one. And the next time the default shortcut doesn't load (like this boot), the custom one is already gone so I end up with none at all. Are there any debug flags I could set so it spits out something into the journal? I'll attached the one from the current boot, but I don't see anything where it might fail to load the shortcut.
Created attachment 174785 [details] Journal from boot with missing Shortcut
(In reply to Tarulia from comment #4) > Are there any debug flags I could set so it spits out something into the > journal? I'll attached the one from the current boot, but I don't see > anything where it might fail to load the shortcut. You could try setting the environment variable QT_LOGGING_RULES="kf.globalaccel.kglobalacceld.debug=true" in /etc/environment. For reference, could you upload the contents of your ~/.config/kglobalshortcutsrc? Thanks!
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.
Created attachment 177484 [details] filtered journal with kglobalacceld with Custom Shortcut
Created attachment 177485 [details] filtered journal with kglobalacceld with Default/No Shortcut
Created attachment 177486 [details] kglobalshortcutsrc (with Custom Shortcut)
OK so... I already had a suspicion, but I wanted to try getting a log without the Custom Shortcut set and with the Default Shortcut showing up (and more importantly: functioning). And well, I was not successful. After 10 reboots with no Default Shortcut showing, it seems this default only shows up whenever there is a Custom Shortcut set. On my 10th reboot I set the Shortcut again, then rebooted again, and now I have both the Custom Shortcut showing and functioning, as well as the Default Shortcut checkbox showing (but disabled). It is... slightly bizarre 🤔