-
-
Notifications
You must be signed in to change notification settings - Fork 255
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Clicking on any of the open folder buttons in bottles opens the file path in Kate instead of in Dolphin (KDE's file manager) #3365
Comments
It is a xdg bug, not a Bottles bug. This should do the work for Dolphin, probably: |
OMG this worked! thank you so much @Dhizaes ! 😊 Can you please explain what xdg is and what those commands do? I don't get it but it worked! 🥳 |
It can be simplified to this I think: There is a "mimeapps.list" file in your ".config" folder, probably. It defines what should your OS do when that part triggered. Take it as a Default App system. Somehow, text or code editors, takes the default slot for themselves and I don't have any idea why they are doing that. For you, it is Kate; for me, it was VSCode. Also almost same system applies to folders as well and it is stored in "user-dirs.dirs" file, ".config" folder, again. |
Thank you for the link and the detailed explanation, I really appreciate it. It's very annoying when something like this happens because the average user has no idea how to fix it and assumes it's a bug with the program itself, I tried looking under default app settings in KDE but of course there's nothing there related to this issue specifically that I could see. Thanks again and I hope you have a wonderful day! 😊 |
Describe the bug
If you click on any folder icon in bottles which is supposed to direct you to the relevant folder it instead opens the file path in Kate which is a text editor and not a file manager. Please see the attached images:
To Reproduce
Package
Flatpak from Flathub
Distribution
Manjaro (KDE)
Debugging Information
Troubleshooting Logs
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: