Created attachment 156173 [details] Disks & Devices opens Elisa instead of Dolphin STEPS TO REPRODUCE 1. Press on `Disks & Devices` Plasmoid 2. Press a `Open in File Manager` button OBSERVED RESULT 3. Witness Elisa opening instead. EXPECTED RESULT 3. Dolphin opens to browse the mounted partition. SOFTWARE/OS VERSIONS Why is this duplicate here if there are selections for these above the summary and description fields already? Much UX genious here, such wow. Have one or the other. Having both just creates user confusion. Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version:
Is Elisa somehow set up to open folders, maybe? If you run `xdg-open ~` in a terminal window, does it open Elisa, or your file manager? Also, can you paste the output of `grep "inode/directory" ~/.config/mimeapps.list`?
(In reply to Nate Graham from comment #1) > Is Elisa somehow set up to open folders, maybe? > > If you run `xdg-open ~` in a terminal window, does it open Elisa, or your file manager? Gives me the following in terminal: ``` qrc:/qml/ElisaMainWindow.qml:18:1: QML ElisaMainWindow: Accessible must be attached to an Item ✔ file:///usr/lib/qt/qml/org/kde/kirigami.2/Page.qml:365: Error: Cannot assign QObject* to PageRow_QMLTYPE_174* file:///usr/lib/qt/qml/org/kde/kirigami.2/Page.qml:365: Error: Cannot assign QObject* to PageRow_QMLTYPE_174* org.kde.elisa.indexers.manager: Local file system indexer is inactive org.kde.elisa.indexers.manager: Baloo indexer is unavailable org.kde.elisa.indexers.manager: Baloo indexer is inactive qrc:/qml/NativeTrayMenu.qml:42: TypeError: Cannot call method 'name' of undefined qrc:/qml/NativeTrayMenu.qml:50: TypeError: Cannot call method 'name' of undefined org.kde.elisa.indexers.manager: Baloo indexer is available org.kde.elisa.indexers.manager: Baloo indexer is active org.kde.elisa.indexers.manager: trigger init of baloo file indexer qrc:/qml/ImageWithFallback.qml:36:5: QML Image: Invalid embedded cover image in /run/media/user/Secondary/Music/Lineage2/L2C2_tower_of_oman.mp3 ``` And does open Elisa. > Also, can you paste the output of `grep "inode/directory" ~/.config/mimeapps.list`? ``` inode/directory=org.kde.elisa.desktop;org.kde.dolphin.desktop; inode/directory=org.kde.elisa.desktop; ``` Still, the button says 'Open in File Manager'. But if the application to open with can be changed somewhere then perhaps it should reflect that and say 'Open in Media Player' or 'Open in ApplicationType' or "Open in [executable name here]" respectively?
Looks like the problem is that Elisa has become somehow configured as your file manager. This isn't something that's supported, and Elisa doesn't register itself as a handler for opening folders, so it's either a configuration issue or a packaging error. I'd recommend fixing this in System Settings > Applications > Default Applications.
(In reply to Nate Graham from comment #3) > Looks like the problem is that Elisa has become somehow configured as your > file manager. This isn't something that's supported, and Elisa doesn't > register itself as a handler for opening folders, so it's either a > configuration issue or a packaging error. I'd recommend fixing this in > System Settings > Applications > Default Applications. Yes, my best guess is when/while I changed waterfox to be my default browser months ago I might have been hovering over the file manager setting for a moment and since my mouse has a really sensitive scroll wheel it might have accidentally switched the file manager there. But that's besides the point and not the issue I'm trying to highlight. I'm trying to highlight that a button label that I assume should be contextual doesn't really reflect the action it's going to trigger. A small and nit-picky and thus surely low priority issue. But if it reflected what application or type of application it would launch that would also immediately communicated to me as a user that I might have misconfigured it rather than being left with a confusing surprise. Or I might still be left confused why the button would even say that but I wouldn't be surprised it opened something other than a file manager.
Changing the icon for the "Open in File Manager" button to actually reflect the current default file manager is actually surprisingly challenging given the current code infrastructure. I'm not sure it's worth doing to make debugging an unsupported edge case easier. The fact that clicking that button opens Elisa instead of a file manager should itself be a clue that something on the system is configured incorrectly. :)
Aye, as said, surely low priority, minor issue. But if nobody ever show interest, it'll never happen.