Søg i Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Opening profile directory

  • 3 svar
  • 0 har dette problem
  • 132 visninger
  • Seneste svar af udlwukc9w

more options

When I click on Profile Directory: Open Directory on the troubleshooting Information page it tries to open in kid3 instead of file manager (Dolphin file manager). Can I change this behaviour. Also happens with Thunderbird. I am using KDE Plasma on Linux. I just can't work this one out. I would be grateful for any suggestions.

When I click on Profile Directory: Open Directory on the troubleshooting Information page it tries to open in kid3 instead of file manager (Dolphin file manager). Can I change this behaviour. Also happens with Thunderbird. I am using KDE Plasma on Linux. I just can't work this one out. I would be grateful for any suggestions.

Valgt løsning

In KDE Plasma, you can use System Settings to specify applications to use. Look at Personalise > Applications > File Associations > Inode : directory.

Læs dette svar i sammenhæng 👍 0

Alle svar (3)

more options

Do you notice Firefox using the wrong file browser for other file system interactions, like Save Page As (Ctrl+S) or the Browse... buttons on this forum?

I'm a Windows person, but I'm aware of some file browser-related settings in Firefox for Linux. You could take a look here:

https://support.mozilla.org/en-US/questions/1386312#answer-1527471

more options

Valgt løsning

In KDE Plasma, you can use System Settings to specify applications to use. Look at Personalise > Applications > File Associations > Inode : directory.

more options

Thanks for your suggestions, guys. Sadly, they didn't help. Everything seemed to be set up correctly.

It turns out that the application kid3-qt (a tag editor) was the problem. I completely removed it, and now Firefox and Thunderbird are functioning properly again. Opening the profile folder in the correct file manager.

I should have realized it was the tag editor earlier. Still, we live and learn.

Thanks for taking the time to look at the problem; it is much appreciated.