Unable to start KDE Plasma X11 desktop
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 --
Marc Chamberlin composed on 2024-04-20 12:39 (UTC-0700):
Duck duck go is not being helpful in trying to grok what it means to have a key rejected by a service. Any ideas?
Is this distinguishable from your bug report issue? https://bugzilla.opensuse.org/show_bug.cgi?id=1222914 Has that issue been solved? -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
On 4/20/24 12:58, Felix Miata wrote:
Marc Chamberlin composed on 2024-04-20 12:39 (UTC-0700):
Duck duck go is not being helpful in trying to grok what it means to have a key rejected by a service. Any ideas? Is this distinguishable from your bug report issue? https://bugzilla.opensuse.org/show_bug.cgi?id=1222914 Has that issue been solved?
Yes, this is a different problem on a different laptop, one I am also upgrading to OpenSuSE 15.5. And No, my other problem reported on bugzilla has not been solved yet, thanks for asking. Marc C.... -- *"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./)
Hello, In the Message; Subject : Unable to start KDE Plasma X11 desktop Message-ID : <10c75486-d1df-4020-b4a1-54081c7dca6d@marcchamberlin.com> Date & Time: Sat, 20 Apr 2024 12:39:04 -0700 [MC] == Marc Chamberlin via openSUSE Users <users@lists.opensuse.org> has written: MC> I have a misbehaving laptop that no longer can bring up the KDE MC> Plasma X11 desktop. On booting up, it reaches the KDE login MC> prompt but after entering my credentials, it flashes a set of MC> commands (too fast to read) and then goes back to the KDE login MC> prompt. The credentials are correct and this happens no matter MC> whether it is another user or root logging in. [...] MC> Apr 19 03:26:25│modprobe[448]│modprobe: ERROR: could not insert 'nvidia': Key MC> was rejected by service │ MC> │Apr 19 03:26:27│modprobe[475]│modprobe: ERROR: could not insert 'nvidia': MC> Key was rejected by service │ MC> │Apr 19 10:26:29│kernel │input: HDA NVidia HDMI/DP,pcm=3 as MC> /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input21 │ MC> │Apr 19 10:26:29│kernel │input: HDA NVidia HDMI/DP,pcm=7 as MC> /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input22 │ MC> │Apr 19 10:26:29│kernel │input: HDA NVidia HDMI/DP,pcm=8 as MC> /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input23 │ MC> │Apr 19 10:26:29│kernel │input: HDA NVidia HDMI/DP,pcm=9 as MC> /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input24 │ MC> │Apr 19 10:26:32│modprobe[637]│modprobe: ERROR: could not insert 'nvidia': MC> Key was rejected by service │ MC> │Apr 19 10:26:33│modprobe[955]│modprobe: ERROR: could not insert 'nvidia': MC> Key was rejected by service │ MC> │ MC> Duck duck go is not being helpful in trying to grok what it MC> means to have a key rejected by a service. Any ideas? It is because of secure boot. If you don't use secure boot, the problem should be solved. Best Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ lake.dti.ne.jp ┃\/彡 ┗━━┛ "Distinguish between what is meaningful to me and what is meaningless, and forget what is meaningless to me. This is where individuality comes into play. This is a function that computer cannot perform." -- Shigehiko Toyama (in Japanes) --
Am Samstag, 20. April 2024, 21:39:04 CEST schrieb Marc Chamberlin via openSUSE Users:
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
--
Maybe: https://en.opensuse.org/SDB:NVIDIA_drivers#Secureboot
On 4/20/24 23:10, Stephan Hemeier via openSUSE Users wrote:
Am Samstag, 20. April 2024, 21:39:04 CEST schrieb Marc Chamberlin via openSUSE Users:
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
-- Maybe: https://en.opensuse.org/SDB:NVIDIA_drivers#Secureboot
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 - mokutil --import /var/lib/nvidia-pubkeys/MOK-nvidia-driver-G0<X>-<driver_version>-<kernel_flavor>.der --root-pw 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. Marc... -- *"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./)
Hello again, I am still trying to find a solution to the problem I am having with my laptop and it's inability to start the KDE Plasma X11 desktop, and my thread seems to have run out of gas? I thought I would add some additional information that I am getting in the "warn" log file, whenever I try to log in on my desktop, and see if that could jog someone's memory. Again Duck Duck Go is not being helpful, though I have tried a number of possible solutions others have tried, but no joy. Here is the messages I am finding in my "warn" log file -
2024-04-30T12:24:18.013688-07:00 marcslaptop sddm-helper: gkr-pam: unable to locate daemon control file 2024-04-30T12:24:18.070632-07:00 marcslaptop sddm[1691]: Auth: sddm-helper exited with 2 2024-04-30T12:24:18.077507-07:00 marcslaptop sddm-greeter[14972]: The X11 connection broke (error 1). Did the X11 server die? 2024-04-30T12:24:22.950960-07:00 marcslaptop sddm[1691]: QProcess: Destroyed while process ("/usr/lib/sddm/sddm-helper") is still running. 2024-04-30T12:24:23.009272-07:00 marcslaptop sddm-greeter[18161]: QFont::fromString: Invalid description '(empty)' 2024-04-30T12:24:23.117822-07:00 marcslaptop sddm-greeter[18161]: QObject: Cannot create children for a parent that is in a different thread.#012(Parent is QGuiApplication(0x7ffccb2f67b 0), parent's thread is QThread(0x55da19e46650), current thread is QThread(0x55da19f60ba0) 2024-04-30T12:24:23.118216-07:00 marcslaptop sddm-greeter[18161]: message repeated 2 times: [ QObject: Cannot create children for a parent that is in a different thread.#012(Parent is Q GuiApplication(0x7ffccb2f67b0), parent's thread is QThread(0x55da19e46650), current thread is QThread(0x55da19f60ba0)] 2024-04-30T12:24:23.118261-07:00 marcslaptop sddm-greeter[18161]: QObject::installEventFilter(): Cannot filter events for objects in a different thread. 2024-04-30T12:24:23.300912-07:00 marcslaptop sddm-greeter[18161]: Failed to find a Kirigami platform plugin 2024-04-30T12:24:23.463365-07:00 marcslaptop sddm-greeter[18161]: Qt Quick Layouts: Polish loop detected. Aborting after two iterations. 2024-04-30T12:24:23.687029-07:00 marcslaptop sddm-greeter[18161]: Hunspell dictionary is missing for "en_GB" . Search paths ("/usr/share/qt5/qtvirtualkeyboard/hunspell", "/usr/share/hun spell", "/usr/share/myspell/dicts")
P.S. I can SSH in to my laptop which is how I am getting this information from it. Just can't login via the KDE prompt and use my laptop normally... Any thoughts? and thanks in advance as always for taking the time to help me guide my laptop into enlightenment! Marc... On 4/23/24 11:13, Marc Chamberlin via openSUSE Users wrote:
On 4/20/24 23:10, Stephan Hemeier via openSUSE Users wrote:
Am Samstag, 20. April 2024, 21:39:04 CEST schrieb Marc Chamberlin via openSUSE Users:
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
-- Maybe: https://en.opensuse.org/SDB:NVIDIA_drivers#Secureboot
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 -
mokutil --import /var/lib/nvidia-pubkeys/MOK-nvidia-driver-G0<X>-<driver_version>-<kernel_flavor>.der --root-pw
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.
Marc...
-- *"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./)
-- *"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./)
I just came across "write my article review" service https://domyessay.com/write-my-article-review, and I must say, it's a game-changer. With my schedule stretched thin, finding time to meticulously review articles is a challenge. This service promises expertly crafted reviews within tight deadlines, providing much-needed relief. Trusting professionals to handle this task ensures a thorough, well-structured review that meets academic criteria.
participants (5)
-
Felix Miata
-
Marc Chamberlin
-
Masaru Nomiya
-
Stephan Hemeier
-
yohannathomas911@gmail.com