*** 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 Please remove this comment after reading and before submitting - thanks! *** SUMMARY I am trying to import the Flameshot custom keybinds file (https://raw.githubusercontent.com/flameshot-org/flameshot/master/docs/shortcuts-config/flameshot-shortcuts-kde.khotkeys). However, clicking on "Import" does not open a file picker, except for when the option is "Custom scheme", which does not actually import the file. STEPS TO REPRODUCE 1. Go to Keyboard -> Shortcuts 2. Press "Import..." 3. Click on "Import" OBSERVED RESULT Clicking on "Import" does not open a file picker to choose your custom keybind file. EXPECTED RESULT "Import" should open a file picker. SOFTWARE/OS VERSIONS (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: 6.16.5-arch1-1 KDE Plasma Version: 6.4.4 KDE Frameworks Version: 6.17.0 Qt Version: 6.9.2 ADDITIONAL INFORMATION qrc:/qt/qml/org/kde/kirigami/dialogs/PromptDialog.qml:100: TypeError: Cannot read property 'None' of undefined // After clicking on "Import" org.kde.kcm_keys: Ignoring unknown component "kxkb" org.kde.kcm_keys: Ignoring unknown component "Settings" org.kde.kcm_keys: Ignoring unknown action "Desktop Screenshot to Clipboard" org.kde.kcm_keys: Ignoring unknown action "Mouse Emulation" org.kde.kcm_keys: Ignoring unknown action "Walk Through Desktop List" org.kde.kcm_keys: Ignoring unknown action "Walk Through Desktop List (Reverse)" org.kde.kcm_keys: Ignoring unknown action "Walk Through Desktops" org.kde.kcm_keys: Ignoring unknown action "Walk Through Desktops (Reverse)" org.kde.kcm_keys: Ignoring unknown action "Window Screenshot to Clipboard" org.kde.kcm_keys: Ignoring unknown component "klipper" org.kde.kcm_keys: Ignoring unknown component "krunner"
Can confirm.
*** Bug 428702 has been marked as a duplicate of this bug. ***