*** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY After updating to dolphin 24.05.0, launching the application gives the warning "There are two actions (, ) that want to use the same shortcut (F3)". Pressing F3 gives another warning stating that the shortcut is ambiguous. The keyboard shortcut configuration menu only lists one action for F3, that being split view. STEPS TO REPRODUCE 1. Open dolphin 24.05.0 OBSERVED RESULT Split view cannot be used via its default shortcut of F3, and there is no way to resolve the (seemingly nonexistent) conflicting action that claims to also use F3. EXPECTED RESULT Split view should be the only action assigned to F3, which was the case in the prior versions of dolphin. SOFTWARE/OS VERSIONS Arch Linux KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1
Very weird. By your description this is very annoying and can't really be resolved as a user, so we usually should get a bunch of bug reports about this. This doesn't seem to be the case yet, so either people haven't updated to the latest Dolphin 24.05 version as fast as you have, or the bug is somewhat specific to your setup in some way. It might be worth looking into deleting your Dolphin configuration files and resetting Dolphin if we don't see a bunch of similar bug reports coming in soon.
Considering that you can't find the conflicting shortcut in Dolphin, I wonder if this could either be a shortcut that is only available while the Konsole panel is active in Dolphin (to check this, first activate Dolphin's terminal panel, then open the Dolphin keyboard shortcuts configuration), or if some global keyboard shortcut might cause a conflict. This is just a stab in the dark on my part though, I don't actually know that much about how such a keyboard conflict could suddenly appear during an update.
(In reply to Felix Ernst from comment #2) > Considering that you can't find the conflicting shortcut in Dolphin, I > wonder if this could either be a shortcut that is only available while the > Konsole panel is active in Dolphin (to check this, first activate Dolphin's > terminal panel, then open the Dolphin keyboard shortcuts configuration), or > if some global keyboard shortcut might cause a conflict. This is just a stab > in the dark on my part though, I don't actually know that much about how > such a keyboard conflict could suddenly appear during an update. Opening the Konsole panel did not bring up any extra options associated with just F3 in the keyboard config menu. I have reset all the shortcuts to their default settings but this also did not resolve the ambiguous shortcut. I would like to delete the config files for Dolphin, but I'm not sure which files to delete within ~/.config/.
(In reply to 1r8l864u from comment #3) > (In reply to Felix Ernst from comment #2) > > Considering that you can't find the conflicting shortcut in Dolphin, I > > wonder if this could either be a shortcut that is only available while the > > Konsole panel is active in Dolphin (to check this, first activate Dolphin's > > terminal panel, then open the Dolphin keyboard shortcuts configuration), or > > if some global keyboard shortcut might cause a conflict. This is just a stab > > in the dark on my part though, I don't actually know that much about how > > such a keyboard conflict could suddenly appear during an update. > > Opening the Konsole panel did not bring up any extra options associated with > just F3 in the keyboard config menu. I have reset all the shortcuts to their > default settings but this also did not resolve the ambiguous shortcut. Ah, that's unfortunate. I am mostly guessing here as well. I don't really know what could be the issue for you. > I would like to delete the config files for Dolphin, but I'm not sure which > files to delete within ~/.config/. For hotkey settings see this answer: https://www.reddit.com/r/kde/comments/cmkwae/where_can_i_find_the_config_file_for_keyboard/ Dolphin settings can be reset by deleting /home/userName/.config/dolphinrc . Not sure if that would help at all though, so maybe only move it out of the way for a moment to test and move it back there if you want to keep some settings.
(In reply to Felix Ernst from comment #4) > Dolphin settings can be reset by deleting /home/userName/.config/dolphinrc . > Not sure if that would help at all though, so maybe only move it out of the > way for a moment to test and move it back there if you want to keep some > settings. I ended up "solving" it by deleting the default shortcuts entirely as well as dolphinrc and reapplying everything myself... Not sure if that was overkill, but there were no more ambiguous shortcuts (partially because there were no shortcuts at all anymore).
(In reply to 1r8l864u from comment #5) > I ended up "solving" it by deleting the default shortcuts entirely as well > as dolphinrc and reapplying everything myself... Not sure if that was > overkill, but there were no more ambiguous shortcuts (partially because > there were no shortcuts at all anymore). Okay, great! I mean, it would be even better if we knew that this was just a weirdness that somehow affected only you and not something we need to fix within KDE somehwere, but it is at least neat that you are no longer affected by this issue. We can probably no longer reproduce the issue now, and there is also no immediate need for it anymore. I guess this means that I should mark this bug as resolved instead of keeping it open indefinitely.