Avatar for Username

Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Learn More

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

about:profiles doesn't "Open Directory" from a profile

  • 2 antwoorden
  • 1 heeft dit probleem
  • 33 weergaven
  • Laatste antwoord van SkyHook

SkyHook
SkyHook
more options

Under an "about:profiles" profile, selecting the "Open Directory" button opens my Linux "Document Viewer" with an "Unable…" warning; expected because that's not what Document Viewer is for.

This could be exactly as predicted in my preferences, but I didn't find any means to redirect that button action at a different helper. I expected it to routinely use my default file manager application and this was a surprise. All I could find searching for the issue focuses on URLs which isn't my problem; I can enter (or copy/paste) the displayed path beside that button okay as "file:///…," so I can call that the workaround.

How is this button action set? Is it a simple thing buried somewhere in the settings?

Under an "about:profiles" profile, selecting the "Open Directory" button opens my Linux "Document Viewer" with an "Unable…" warning; expected because that's not what Document Viewer is for. This could be exactly as predicted in my preferences, but I didn't find any means to redirect that button action at a different helper. I expected it to routinely use my default file manager application and this was a surprise. All I could find searching for the issue focuses on URLs which isn't my problem; I can enter (or copy/paste) the displayed path beside that button okay as "file:///…," so I can call that the workaround. How is this button action set? Is it a simple thing buried somewhere in the settings?

Gekozen oplossing

Okay, great first step. After a deprecation warning, it appears both installed file managers are in my returned list of a dozen; gnome.nautilus and elementary.files.

Eureka! The list were only potential recommendations. I see now that it returned a list of options because one wasn't set. Why not, I'm not worried about, but it feels strange. I went back to the command line with the following and now FF launches my favourite file manager as expected.

Thank you very much.

$ gio mime inode/directory org.gnome.Nautilus.desktop Set org.gnome.Nautilus.desktop as the default for inode/directory

Dit antwoord in context lezen 👍 0

Alle antwoorden (2)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

Sounds something is broken. You can try this command in a terminal window.

  • gvfs-mime --query inode/directory
SkyHook
SkyHook Vraageigenaar
more options

Gekozen oplossing

Okay, great first step. After a deprecation warning, it appears both installed file managers are in my returned list of a dozen; gnome.nautilus and elementary.files.

Eureka! The list were only potential recommendations. I see now that it returned a list of options because one wasn't set. Why not, I'm not worried about, but it feels strange. I went back to the command line with the following and now FF launches my favourite file manager as expected.

Thank you very much.

$ gio mime inode/directory org.gnome.Nautilus.desktop Set org.gnome.Nautilus.desktop as the default for inode/directory

Bewerkt door SkyHook op