Avatar for Username

Search 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

This thread was archived. Please ask a new question if you need help.

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

  • 2 replies
  • 1 has this problem
  • 18 views
  • Last reply by 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?

Chosen solution

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

Read this answer in context 👍 0

All Replies (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 Question owner
more options

Chosen Solution

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

Modified by SkyHook