Can't open root tools using xfce

Hello,

i just installed fresh Slowroll Iso Build 46.2 with xfce desktop due to a drive change.
My old Slowroll was up to date and working fine (except scanner).

Repos are default plus packman.

Now i can’t open tools in root mode like “myrlyn”, “lightdm-gtk” or “gsmartcontrol”.
When clicking the menu entry nothing happens. Opening via terminal works.

I also noted a change to my old Slowroll install when calling sudo in terminal
now the password request pops up in a graphical window which i don’t like.

Any ideas?

Selinux maybe???

I didn’t make any changes to Selinux while installing and don’t have any experience with it.

sestatus
SELinux status: enabled
SELinuxfs mount: /sys/fs/selinux
SELinux root directory: /etc/selinux
Loaded policy name: targeted
Current mode: enforcing
Mode from config file: enforcing
Policy MLS status: enabled
Policy deny_unknown status: allowed
Memory protection checking: actual (secure)
Max kernel policy version: 35

Can you check if you are in wayland session

xfce4-about

lightdm still doesn’t open in wayland session as root here, but I’m using SDDM.
Myrlyn should work in wayland if you didn’t modify the command to open it. (myrlyn-sudo)
gsmartcontrol I have no clue, I have not use it.

In an effort to help I installed gsmartcontrol. It doesn’t open in wayland session using sudo.
Here is the warning:

Gtk-WARNING **: 11:11:22.878: cannot open display: 

Though it opens using
su -c gsmartcontrol

Running X11 on AMD graphic card here.

Does myrlyn-sudo work for you? It really should.

It takes care of preserving a number of environment variables across the sudo call:

If you don’t like the graphical password prompt, copy it and change the last line to

sudo /usr/bin/env $ENV /usr/bin/myrlyn $MYRLYN_ARGS

This might also help to understand the problem and what’s going on:

Could be a bug :thinking:

myrlyn-sudo via terminal is opening. myrlyn via xfce menu and nothing happens. same with other tools that require root priviliges.

yes looks like a bug.

Check if you have the sudo-policy-wheel-auth-self package installed. This sets up sudo to give the members of the wheel user group root privileges, and - important - it asks for your user password, not the root password.

If you are not already, add your user account to the wheel user group:

sudo usermod -aG wheel $USER

Conflicting packages. This is a fresh install.

Problem: 1: das installierte run0-wrappers-0.4+git20260109.43967c3-1.1.x86_64 steht im Konflikt mit ‘sudo-policy-wheel-auth-self’, das von dem zu installierenden sudo-policy-wheel-auth-self-1.9.17p2-1.1.noarch bereitgestellt wird
Lösung 1: Deinstallation von run0-wrappers-0.4+git20260109.43967c3-1.1.x86_64
Lösung 2: sudo-policy-wheel-auth-self-1.9.17p2-1.1.noarch nicht installieren

If you are not actively and intentionally using run0-wrappers, you might want to choose solution (1) to remove it in favor of sudo-policy-wheel-auth-self.

You can still use the plain run0 without that package if you really want to. I found the good old sudo much better, but that’s just my opinion.

I don’t even know about run0-wrappers and already was wondering why i couldn’t find the sudo config file in /etc.

I downloaded Slowroll Build 44.6 Iso. Maybe i try a fresh install instead.

Like many other configurations, the system configuration is now in /usr/etc/sudoers (usr because it’s from the system - don’t ask) and /usr/etc/sudoers.d/.

A file in /etc/sudoers.d or /etc/sudoers will override values from /usr/etc.

If that sounds more complicated, that’s because it is. :slightly_smiling_face: But it’s also much more flexible.

A fresh installation won’t improve anything; you’ll be right back where you are right now. Some things have simply changed (don’t they always).

I see and think it has something to do with usr merge. Those things don’t happen in FreeBSD or Slackware.

run0-wrapper seems like it’s a systemd component…

I had a fresh Slowroll installation end of last year and no problems with sudo and graphical polkit popup windows.

The usr-merge was about moving everything from /bin/usr/bin and /sbin/usr/sbin.

This configuration split is actually intended to make life easier for admins: All packages come with a default configuration, and that is now in /usr/etc, and in many cases split up into small pieces so several system components / packages can bring their own specific configuration snippet. If a package is updated, there is no more conflict between the system default and whatever the admin might have configured personally, because those custom configs now live separately in /etc or /etc/mysubsystem.d/50-my-snippet.conf.

A package update on Debian / Ubuntu would ask in such a case if you’d want to keep your own custom config or overwrite it with the package’s default config; an RPM package OTOH would create a .rpmsave file, and you never knew if that was your lost opportunity to get a much better new default for that thing, or if they’d renamed and thus ignored your own holy config.

Now a new package can change the default config, and if you didn’t touch it, you get some new additional parameters with it, but your personal config is still there, and it still overrides any values from the system config.

It does make sense, and it is an improvement, but it makes everything a bit more complicated:

  • You have to know that /usr/etc/mysubsystem.d and /usr/etc/mysubsystem exist and copy some values from there
  • You need to create a new /etc/mysubsystem.d/50-my-holy.conf with those values - and only those - that you want to change.

But you now can also backup those snippets for archiving and to distribute to your other machines, and that’s really cool.

It takes some getting used to, but you might like it over time. I do.

2 Likes

Yes, of course; another small step from the Poettering universe to take over world domination. :wink:

run0 (“run as user #0”, i.e. root) is the systemd universe version of sudo. I learned about it from a pull request against Myrlyn:

And I modified it to have a stand-alone version for fans of run0, but without making myrlyn-sudo a lot more complex. It now lives as myrlyn-run0 here:

Thanks for the illustration.

I prefer the KISS principle and my main reason i’m trying Slowroll is because of the rolling release/up to date system and i don’t like being an Arch beta tester.

Seems to me like openSUSE changed something in sudo calls within the last months.

Yes, sudo on openSUSE now behaves like it always did on Debian and Ubuntu; if you install that package sudo-policy-wheel-auth-self.

That means that you can now give some privileges to do some minor admin tasks (enable / diable printer etc.) to a user without telling the root password.

I reinstalled Slowroll with an older Iso hoping it would fix the issue under xfce but still tools with root priviliges wouldn’t open.

Tried replacing run0-wrappers with sudo-policy-wheel-auth-self package fixed it.
You were right. Now i have the old behaviour and everything is working.

Thank you.

1 Like