KDEneon sudoers.d files not working again

[oshunluvr]

Newest attempt:
Created new KDEneon Virtual installation
Verified sudoers still did not work.
Installed "gcc make perl" packages so I could install VirtualBox Guest Extensions and share a folder.
Rebooted and verified sudoers still did not work.
Mounted the root btrfs file system and made a snapshot of "@" so I could revert to new without reinstallling.
Took package list difference and removed all lib, libreoffice, linux-kernel, xorg, python, and fonts files leaving 132 packages.
Results of sudo apt update (password required( then installing the 132 packages and their depends.
This failed due to a conflict with kmail.
I removed kmail and the install completed of 382 packages.
This resulted in sudoers working.
I restored the original subvolume and rebooted.
Verified sudoers still did not work.

I then went through the 132 packages and installed them each until I found the culprit: Installing kubuntu-desktop-settings forces removal of neon-settings. This single package change results in sudoers working again. Here's the apt output of the package change:

The following packages will be REMOVED:
neon-settings
The following NEW packages will be installed:
kubuntu-settings-desktop
0 upgraded, 1 newly installed, 1 to remove and 2 not upgraded.
Need to get 303 kB of archives.
After this operation, 125 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 kubuntu-settings-desktop
all 1:18.04ubuntu11 [303 kB]
Fetched 303 kB in 0s (833 kB/s)
(Reading database ... 190386 files and directories currently installed.)
Removing neon-settings (0.0+p18.04+git20190506.0955) ...
Removing 'diversion of /usr/share/applications/display-im6.desktop to /usr/share/applica
tions/display-im6.desktop.distrib by neon-settings'
Removing 'diversion of /usr/share/applications/display-im6.q16.desktop to /usr/share/app
lications/display-im6.q16.desktop.distrib by neon-settings'
Removing 'diversion of /usr/share/applications/vim.desktop to /usr/share/applications/vi
m.desktop.distrib by neon-settings'
Removing 'diversion of /lib/systemd/system/setvtrgb.service to /lib/systemd/system/setvt
rgb.service.distrib by neon-settings'
Removing 'diversion of /usr/bin/firefox to /usr/bin/_neon.firefox by neon-settings'
Selecting previously unselected package kubuntu-settings-desktop.
(Reading database ... 190335 files and directories currently installed.)
Preparing to unpack .../kubuntu-settings-desktop_1%3a18.04ubuntu11_all.deb ...
Unpacking kubuntu-settings-desktop (1:18.04ubuntu11) ...
Setting up kubuntu-settings-desktop (1:18.04ubuntu11) ...
Installing new version of config file /etc/xdg/kcm-about-distrorc ...
update-alternatives: using /etc/newt/palette.original to provide /etc/newt/palette (newt
-palette) in manual mode
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/99_breeze-grub.cfg'
Generating grub configuration file ...
Found theme: /boot/grub/themes/breeze/theme.txt
Found linux image: /boot/vmlinuz-4.18.0-20-generic
Found initrd image: /boot/initrd.img-4.18.0-20-generic
Found memtest86+ image: /@/boot/memtest86+.elf
Found memtest86+ image: /@/boot/memtest86+.bin
done
Processing triggers for mime-support (3.60ubuntu1) ...
Processing triggers for desktop-file-utils (0.23-1ubuntu3.18.04.2) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
stuart@neon-VirtualBox:~/Public/Documents$

So some setting in or change effected by that package is causing the issue.

[Snowhog]

Well, interesting for sure.

I know you are no novice, but, after installing and creating the file in /etc/sudoers.d, did you logout/reboot?

[oshunluvr]

Well, agree or not I just again created a new KDEneon VM and the sudoers files I'm using on Kubuntu does not work. Try it yourself.

This exact file on both fresh install of Kubuntu 18;04 and KDEneon: /etc/sudoers.d/apt

stuart ALL = (root) NOPASSWD: /ust/bin/apt

Kubuntu:


Neon:

[Snowhog]

Conclusion: There is a package(s) that sudoers.d needs to parse the files and the default Neon install does not have it/them. No it's just a matter of figuring out which one(s).

I'm not sure I agree with that, at least, given that the KDE neon I have was a 'stock' install (not recently, but it was stock when it was installed), and when I created my file in /etc/sudoers.d (per your post), it worked, and still works, as it should.

I'm not at the house; having my morning coffee at my local coffee shop; but when I get back, I'll run a reverse depends on sudo and post the results. You can compare it to yours.

[oshunluvr]

It's not the sudoers file - they all match.

I've determined it's definitely a missing package - undeclared dependency or something like that. Here's what I did this morning:

Test installs: 18.04.2 Kubuntu along side KDEneon LTS latest - both have an Ubuntu 18.04 base.
Created identical /etc/sudoers.d/apt files in both installs (as noted above).

Results: No password required for Kubuntu but still required for Neon.

Then I dumped dpkg file lists from both installs, trimmed it to just a list of package names, then extracted a list of packages that were installed to Kubuntu but not Neon. I removed libreoffice and kernel packages from the list, then installed all remaining packages into Neon.

Results: Neon no longer needs a password for apt.

Conclusion: There is a package(s) that sudoers.d needs to parse the files and the default Neon install does not have it/them. Now it's just a matter of figuring out which one(s).

[Snowhog]

in KDEneon, what is in your sudoers file? sudo visudo

[oshunluvr]

Both versions of Kubuntu (18.04 and 19.04) this /etc/sudoers.d/apt works:

stuart ALL = (root) NOPASSWD: /usr/bin/apt-get, /usr/bin/apt

but the exact same entry in KDEneon 18.04 does not.

[oshunluvr]

Kubuntu 18.04.2 does not have the error. Seems related to KDEneon only.

moving thread...

[Snowhog]

sudo --version

Sudo version 1.8.21p2
Sudoers policy plugin version 1.8.21p2
Sudoers file grammer version 46
Sudoers I/O plugin version 1.8.21p2

apt-cache policy sudo

Installed: 1.8.21p2-3ubuntu1
Candidate: 1.8.21p2-3ubuntu1

[oshunluvr]

Paul, what sudo package is on your system? @here it's 1.8.21p2-3ubuntu1

[oshunluvr]

I'm using KDEneon 18.04 not Kubuntu 18.04. I generally only post in the KDEneon section when I know it's related specifically to KDEneon and not generally an Ubuntu 18.04 problem - which both KDEneon and Kubuntu are based on. Since this issue is not a Desktop Environment issue, I surmised it was more likely related to Ubuntu packages as those are identical across both Kubuntu and KDEneon.

It may in fact be an issue with my install and not specific to the KDE packages at all, but my initial VM test shows a fresh KDEneon responding identically to my install. It is very curious that your KDEneon 18.04 works where my brand-new untouched (but updated) KDEneon does not.

Obviously more digging is required.

[Snowhog]

I haven't tried Kubuntu 18.04 yet nor KDEneon Unstable.

But you posted this in 18.04. I'm confused.

Just fired up my KDE neon User Edition 5.15 (based on Ubuntu 18.04) the content of /etc/sudoers.d/ is working; I have one file there named paul which contains:

paul barley-cat = (root) NOPASSWD: /usr/bin/apt,/usr/bin/apt-get,/usr/bin/add-apt-repository,/usr/bin/apt-add-repository,/usr/bin/ucaresystem-core

Permissions and ownership on /etc/sudoers.d is drwxr-xr-x root root

Permissions on /etc/sudoers.d/paul is -r--r----- root root

[oshunluvr]

OK, I installed a fresh KDEneon LTS Useredition in a VM and sudoers is not working. BUT I also installed a fresh Kubuntu 19.04 and the same exact file in sudoers.d WORKED. So whatever is bug or problem is, it's either fixed upstream or solely a KDEneon problem.

I haven't tried Kubuntu 18.04 yet nor KDEneon Unstable.

[Snowhog]

Anything here useful?

[oshunluvr]

I'll check when I'm back at the house (out having my morning coffee at the moment). I don't have 18.04 installed, but I do have 18.10, and have my own file in /etc/sudoers.d. Or is this specific to 18.04?

I don't know as haven't installed 18.10 anywhere. Be interesting to know if it works in 18.10 and above.