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 can't handle network locations as root #665

Closed
Enkouyami opened this issue Jul 19, 2014 · 7 comments
Closed

Nemo can't handle network locations as root #665

Enkouyami opened this issue Jul 19, 2014 · 7 comments
Labels

Comments

@Enkouyami
Copy link

When nemo is opened as root, trying to access any network location results in an error saying "Could not display "network:///". Nemo cannot handle "network" locations."

@MaDDmin
Copy link

MaDDmin commented Nov 9, 2016

More than 2 years and this is still an open issue??? My jaw just dropped.

@JosephMcc JosephMcc added the BUG label Nov 9, 2016
@ghost
Copy link

ghost commented Dec 21, 2016

+1.

@mattes42
Copy link

mattes42 commented Apr 7, 2018

+1

@leigh123linux
Copy link
Contributor

What you see as an issue I see as a security feature.

@ghost
Copy link

ghost commented Apr 7, 2018

@leigh123linux : you may well have a point. If you do, why not make the feature look less like an ad hoc limitation than it does? That is: why not replace the 'cannot handle' message with something like, 'As a matter of security, root Nemo . .'?

Better (or as an addition): why not, in noot nemo, indicate in advance to the user that the inaccessible locations are inaccessible - by greying out network locations in the side bar, and suchlike?

If people suspect that what they want to do is foreclosed for a good reason, then that limitation is less likely to prompt them to complain or to confuse them.

@leigh123linux
Copy link
Contributor

If you lot really want to use root try

sudo dbus-launch --exit-with-session nemo

https://bbs.archlinux.org/viewtopic.php?id=225665

Other stuff will also work eg: trash and computer

@ghost
Copy link

ghost commented Apr 7, 2018

Thanks, Leigh, but, for my part, it's mainly the user experience that's at issue. That is: it seems to me that the you-can-press-it-but-it-will-do-nothing situation is unsatisfactory and should be resolved in one direction or the other.

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

No branches or pull requests

5 participants