Open as Root doesn't work on Wayland

[Lassebq]

Distribution

Arch Linux 6.4.4.arch1-1

Package version

5.8.4-1

Frequency

Always

Bug description

Open as root doesn't work on wayland even with xorg-xhost installed.

Steps to reproduce

1. Run nemo
2. Open context menu on any folder
3. Click Open as Root
4. Polkit shows up, asks password, nothing happens

Authorization required, but no authorization protocol specified

Could not parse arguments: Cannot open display: 

This is what gets printed to stdout

Expected behavior

stdout should print

localuser:root being added to access control list

And the folder should open with elevated privileges

Additional information

No response

[dominichayesferen]

#2929

Use admin://PATHHERE as an alternative (CTRL+L or use the toolbar button to switch to path input).

[Lassebq]

Alright, but I still don't understand why #2929 was closed, if the option is there it should work. For example, gparted makes use of xorg-xhost, which lets it start on Wayland without issues. (Without this package it fails with the same error as Nemo)

[leigh123linux]

Alright, but I still don't understand why #2929 was closed, if the option is there it should work. For example, gparted makes use of xorg-xhost, which lets it start on Wayland without issues. (Without this package it fails with the same error as Nemo)

I really don't see why it's the responsibility of all the apps to fix this, shouldn't wayland devs submit patches for pkexec or whatever?
Gparted added a hack to workaround it https://github.com/GNOME/gparted/blob/master/gparted.in#L60

@mtwebster Can we add something to hide 'open as root' under wayland.

[dominichayesferen]

Can we add something to hide 'open as root' under wayland.

What if it just redirected the current folder view to the admin:// equivalent under Wayland, instead of being completely removed, since admin:// effectively does the same job anyway, just in the userland Nemo window instead?

[Lassebq]

I support suggested solution

[Lassebq]

That didn't mean I'm fine with this issue closed. I was expecting it to stay open until suggested fix is implemented either by developers or as a PR

[Lassebq]

Oh, nevermind, there's #3259.

[mtwebster]

It was automatically linked when I closed the issue, but here it is again I guess: 86830eb