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

Open As Administrator: Files does not follow stylesheet #2524

Closed
teamcons opened this issue Jan 1, 2025 · 4 comments · Fixed by #2528
Closed

Open As Administrator: Files does not follow stylesheet #2524

teamcons opened this issue Jan 1, 2025 · 4 comments · Fixed by #2528
Labels
Status: Confirmed The occurrence and circumstances of the issue have been verified Status: Out of Scope Not considered a bug or is ot caused by Files or is best dealt with in some other way

Comments

@teamcons
Copy link

teamcons commented Jan 1, 2025

What Happened?

When opened as Root using the quick action, Files does not open with the default Granite stylesheet

Bildschirmfoto von 2025-01-01 17 18 35

Steps to Reproduce

Right click app icon
open new window as administrator

Expected Behavior

For Files to follow system stylesheet - Albeit with a visible indicator it is currently running as root
Tab label can be easily missed, or dismissed as less dramatic than it is

OS Version

8.x (Circe)

Session Type

Secure Session (Wayland)

Software Version

Latest release (I have run all updates)

Log Output

No response

Hardware Info

No response

@ryonakano
Copy link
Member

Just leaving a note that the same issue happened with Code (run pkexec io.elementary.code) on Secure Session.

@ryonakano ryonakano added the Status: Confirmed The occurrence and circumstances of the issue have been verified label Jan 2, 2025
@jeremypw
Copy link
Collaborator

jeremypw commented Jan 5, 2025

Confirm this happens on OS8 (Wayland) but not on OS7.1 or OS8 (Classic). It also happens with non-elementary apps such as dconf-editor on OS8 (Wayland) when run with sudo.

I think this is probably a system or upstream issue rather than an issue with Files in particular.

@jeremypw jeremypw added the Status: Out of Scope Not considered a bug or is ot caused by Files or is best dealt with in some other way label Jan 5, 2025
@tintou
Copy link
Member

tintou commented Feb 4, 2025

The only way to look files with elevated privileges is to actually use the admin:// scheme (i.e. access /usr/lib with admin:///usr/lib) GVFS would then do the rest for us.

@jeremypw
Copy link
Collaborator

jeremypw commented Feb 4, 2025

Need to modify Files to handle admin:// protocol properly though. At the moment you get a "location not mounted" error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Confirmed The occurrence and circumstances of the issue have been verified Status: Out of Scope Not considered a bug or is ot caused by Files or is best dealt with in some other way
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants