I have a misbehaving laptop that no longer can bring up the KDE Plasma X11 desktop. On booting up, it reaches the KDE login prompt but after entering my credentials, it flashes a set of commands (too fast to read) and then goes back to the KDE login prompt. The credentials are correct and this happens no matter whether it is another user or root logging in. In searching through log files (messages, boot.log, warn etc.) the only clue that I found in in the Xorg.0.log file where I observed this very suspicious bit of nonsense. I would be happy to present the entire log but it is rather long, if that would be more helpful. Apr 19 03:26:25│modprobe[448]│modprobe: ERROR: could not insert 'nvidia': Key was rejected by service │ │Apr 19 03:26:27│modprobe[475]│modprobe: ERROR: could not insert 'nvidia': Key was rejected by service │ │Apr 19 10:26:29│kernel │input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input21 │ │Apr 19 10:26:29│kernel │input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input22 │ │Apr 19 10:26:29│kernel │input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input23 │ │Apr 19 10:26:29│kernel │input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input24 │ │Apr 19 10:26:32│modprobe[637]│modprobe: ERROR: could not insert 'nvidia': Key was rejected by service │ │Apr 19 10:26:33│modprobe[955]│modprobe: ERROR: could not insert 'nvidia': Key was rejected by service │ │ Duck duck go is not being helpful in trying to grok what it means to have a key rejected by a service. Any ideas? Thanks, Marc --

Thanks Stephan for the pointer, it looks/looked promising but either it didn't work for me or unfortunately I don't grok it. The article says I should use the following command -

I looked in the directory /var/lib/nvidia-pubkeys and found lots of nvidia drivers (? I am guessing that is what these files are). To try an narrow it down, I went to Yast2 and studied which driver for nvidia was getting installed and think I found the answer. So I used the following command (via SSH) -

mokutil --import /var/lib/nvidia-pubkeys/MOK-nvidia-driver-G06-550.67-lp155.20.1-default.der --root-pw

No response from executing this command, it simply returned. So I rebooted, and no joy, same problem, the KDE/Plasma login screen simply keeps coming back up after I enter my password. The article you pointed me to said that if desperate to try the following command -

mokutil --disable-validation

So I did, rebooted, and still no joy.. So now I am stuck again.

Felix, Masaru, your suggestion to not use secure boot ran me into another problem. I multi boot my laptop into Windows 10 and Windows 11also, and both got rather pissy about not using secure boot. Got told to either re-enable secure boot or go away and bother/use some other OS.

"The Truth is out there" - Spooky

--
_ _ . . . . . . _ _ . _ _ _ _ . . . . _ . . . . _ _ . _ _ _ . . . . _ _ . _ . . _ . _ _ _ _ . _ . _ . _ . _ .

Computers: the final frontier.

These are the voyages of the user Marc.
His mission: to explore strange new hardware.

To seek out new software and new applications.

To boldly go where no Marc has gone before!

(This email is digitally signed. My public key for sending encrypted email to me can be found at - https://keys.openpgp.org/search?q=marc@domesweetdome.us.com or just ask me for it and I will send it to you as an attachment. If you don't understand, no worries, just ignore it and/or ask me to explain it further.)