Skip to content
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

Nemo action "Mount Archive" does not work for Arch-based distros #1942

Closed
alexnch opened this issue Sep 12, 2018 · 2 comments
Closed

Nemo action "Mount Archive" does not work for Arch-based distros #1942

alexnch opened this issue Sep 12, 2018 · 2 comments

Comments

@alexnch
Copy link
Contributor

alexnch commented Sep 12, 2018

 * Nemo version: 3.8.5
 * Distribution: Manjaro
 * 64 bit

Issue
File action "Mount Archive" has no effect in Arch-based distros.
This is caused by gvfsd-archive's absolute path being located in /usr/lib/gvfsd-archive instead of /usr/lib/gvfs/gvfsd-archive.

Steps to reproduce
Open context menu by right clicking on any archive file inside Nemo folder view and choose "Mount Archive" action.

Expected behaviour
Archive should be mounted.

Workaround
I've created a script file with the path /usr/lib/gvfs/gvfsd-archive and the following contents:

#!/bin/bash

/usr/lib/gvfsd-archive $@

Other information
If there is no solution to this problem from within Nemo project, feel free to discard this issue. Perphaps, the workaround should be added to AUR then.

@mtwebster
Copy link
Member

The action shouldn't have been showing in the menu in the first place if it couldn't find that file. I've fixed that bug here:

b634303

As to the specific issue here, I can't say I agree with those files being located in /usr/lib, being that they're executables (though we've broken plenty of filesystem rules ourselves) - I would suggest that this is something the Arch maintainer might handle - changing the dependency and exec lines.

This is a difficult thing to handle on our end - I started implementing OR dependencies for actions (allowing /usr/lib/gvfsd-archive | /usr/lib/gvfs/gvfsd-archive with either one satisfying the requirement) but this effort would need to be duplicated for the exec line as well, in a more complicated manner. I just don't think this problem warrants that much increase in complexity.

Most things this is intended for would be located in /usr/bin or somewhere else in the path, executables located in non-path locations are sort of outliers I think.

@alexnch
Copy link
Contributor Author

alexnch commented Sep 23, 2018

Thank you for taking the time to review the issue and leaving a reply.

I was suspecting that this is a distribution-specific problem and diverting focus from the home distro in such a way would not be acceptable. Similar thing happened to Cinnamon's remove application feature, which had to be re-implemented for Arch and added to AUR as optional package.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants