After The Last Two Updates To Current There Are Network And Xorg Problems.

z80 · 02-19-2020, 10:51 AM

I had the same or a very similar problem after installing those updates ...
In addition to the not authorized message I also had a delay when logging in and shutting down was only possible using the power button.

I found the following erros in /var/log/messages

Code:

Feb 18 17:16:08 antares NetworkManager[1247]: <info>  [1582042568.1195] audit: op="connection-activate" uuid="6a1d6304-f057-4c79-bb99-b52c80203d88" name="XXX" pid=1600 uid=501 result="fail" reason="Not authorized to control networking."
Feb 18 17:16:10 antares dbus-daemon[1229]: [system] Activating service name='org.freedesktop.PolicyKit1' requested by ':1.1' (uid=0 pid=1247 comm="/usr/sbin/NetworkManager ") (using servicehelper)
Feb 18 17:16:10 antares dbus-daemon[1229]: [system] Activated service 'org.freedesktop.PolicyKit1' failed: Launch helper exited with unknown return code 127

and

Code:

Feb 18 17:24:05 antares kernel: [   24.622103] traps: upowerd[1434] trap int3 ip:7f71f8bc3855 sp:7ffe606d9180 error:0 in libglib-2.0.so.0.6200.4[7f71f8b8b000+7d000]

and suspected a problem with policykit.

After reinstalling ConsoleKit2-1.2.1-x86_64-2.txz and polkit-0.116-x86_64-2.txz (in single-user mode - just to be safe) everything worked again.

Aeterna · 02-19-2020, 11:09 AM

Quote:

Originally Posted by cwizardone

Yep. I've doing that for years.

yes, then other option is policykit editing as I suggested also. But it seems that this was an error in the policykit package that is fixed now.

bassmadrigal · 02-19-2020, 02:53 PM

Quote:

Originally Posted by Aeterna

sudo (visudo tool) always must be configured (if one wants to use this facility) either by enabling wheel or sudo group, unless rights are configured for single user. That is what I had to do with most of linux distros, OpenIndiana, FreeBSD, OpenBSD (doas). So I assumed that this is pretty obvious.

Correct, but you have to explicitly enable the wheel group for it to be applicable for sudo usage, it's disabled by default. By default, adding a user to the wheel group in Slackware does nothing unless you've specifically done changes to add rights to that group.

Alien Bob · 02-19-2020, 03:07 PM

Quote:

Originally Posted by bassmadrigal

Correct, but you have to explicitly enable the wheel group for it to be applicable for sudo usage, it's disabled by default. By default, adding a user to the wheel group in Slackware does nothing unless you've specifically done changes to add rights to that group.

FYI my SLackware Live ISO images configure the use of the wheel group in sudoers and also add a suauth file. All this to educate people to the ways of the greybeards ;-)

Aeterna · 02-19-2020, 03:44 PM

Quote:

Originally Posted by bassmadrigal

Correct, but you have to explicitly enable the wheel group for it to be applicable for sudo usage, it's disabled by default. By default, adding a user to the wheel group in Slackware does nothing unless you've specifically done changes to add rights to that group.

Right,
so this has nothing to do with Slackware, this is standard issue with configuration of any UNIX(like) OS as listed above. I thought that this is quite obvious. I can create any group or give any user root privileges (limited or unlimited). Refering to wheel seemed to be pretty obvious that user would have to be in a privileged group as it is evident from your posts (and in contrast to past default configs, this is a reason to use wheel).
If I would make reference to aeterna group it would be somehow confusing.

Anyway, you are absolutely correct without configuring sudoers, sudo for group(s) or user(s) would not work

bassmadrigal · 02-19-2020, 05:06 PM

Quote:

Originally Posted by Alien Bob

FYI my SLackware Live ISO images configure the use of the wheel group in sudoers and also add a suauth file. All this to educate people to the ways of the greybeards ;-)

That's good to know!

Quote:

Originally Posted by Aeterna

Right,
so this has nothing to do with Slackware, this is standard issue with configuration of any UNIX(like) OS as listed above. I thought that this is quite obvious. I can create any group or give any user root privileges (limited or unlimited). Refering to wheel seemed to be pretty obvious that user would have to be in a privileged group as it is evident from your posts (and in contrast to past default configs, this is a reason to use wheel).
If I would make reference to aeterna group it would be somehow confusing.

Anyway, you are absolutely correct without configuring sudoers, sudo for group(s) or user(s) would not work

It was just the way it was mentioned in your original post it seemed like all the user would need to do would be to add themselves to the wheel group and it would solve their problem. It would do nothing unless they did additional configuration of their Slackware machine to make the wheel group mean something to the system.