Kernel 5.17 rc2 panics when linux517-nvidia is installed along with it. journalctl -b -1 returns the journal of the boot before the kernel upgrade. So I guess the kernel panics at initramfs stage itself. Removing linux517-nvidia fixes the issue, but of course I am unable to use my Nvidia d-gpu.
If the overall goal is to remain in-line with systemd, I think a file should be created in /etc/sudoers.d… I just question whether 10-installer is a meaningful filename that explains the files purpose.
i agree, my only concern is if someone gets the syntax wrong in the drop-in file will it screwup the whole sudo mechanism, does visudo syntax-checking mechanism extend to the included drop-in files.
This happens when the package has different permission than what it was before, you could usually change the permission or leave it as it may be a mistake by packager. Usually not a real issue I think.
I’ve got issues with sudo
“$USER is not in the sudoers file. This incident will be reported”
GUI applications has no issues with getting priviledges, though. KDE Plasma
I don’t know if it’s related, but i have also got microphone not being recognized on PipeWire after a reboot, using systemctl restart --user pipewire pipewire-pulse solved this
I have a huge problem with printer drivers since the update, but I can’t be sure if this introduced in this or previous updates. I believe I saw some comments about printing issue with the previous update.
Now the printer became completely unusable, because each white space is printed as dark gray (using up a lot of ink and making the document unreadable).
What can I do to debug this? I already tried various settings, nothing helped. The system sees the document correctly, only the printer is not handling it properly. The same documents (pdf and others) printed on the same printer from windows, are correct.