KDEneon sudoers.d files not working again

[Snowhog]

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?

[oshunluvr]

This appears to be a regression.

Previous thread and bug report:
https://www.kubuntuforums.net/showth...hlight=sudoers
https://bugs.launchpad.net/ubuntu/+s...e/+bug/1584549

Sometime in the last month, some update or another caused the files in sudoers.d to not be honored yet again. I've tried different formats in the files to see if the syntax changed Nothing has worked and ALL of them are being ignored. I suspect the functionality no longer works or the formatting has changed dramatically and recently.

Here's the info in case anyone wants to look into it to verify what I'm experiencing;

All files under /etc/sudoers.d/ are permissions 0440 and root owned.
visudo -c confirms the syntax passes the checks.

I have tried the following formats. All of these passed syntax check and the first one is what worked beginning in 16.04 when the functionality first stopped working properly (see bug report above):

stuart office.smith.lan = (root) NOPASSWD: /usr/bin/apt-get,/usr/bin/apt,/usr/bin/add-apt-repository,/usr/bin/apt-add-repository

stuart office.smith.lan = (root) NOPASSWD: /usr/bin/apt-get
stuart office.smith.lan = (root) NOPASSWD: /usr/bin/apt
stuart office.smith.lan = (root) NOPASSWD: /usr/bin/add-apt-repository
stuart office.smith.lan = (root) NOPASSWD: /usr/bin/apt-add-repository

stuart office = (root) NOPASSWD: /usr/bin/apt-get,/usr/bin/apt,/usr/bin/add-apt-repository,/usr/bin/apt-add-repository

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

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

None of these work. not even the last one which is the least restrictive. Prior to 16.04, #3 above worked. I reported the bug after 16.04 came out that required the Fully Qualified Domain Name (#1 above) instead of the shortened hostname that occurred at the 16.04 release, but no one ever responded. I'd like to know if the syntax changed or if it works normally for anyone else before I report it as a bug.