Welcome, Guest. Please login or register.
Did you miss your activation email?

Recent Posts

Pages: [1] 2 3 ... 10
1
Upgrade Warnings / Re: [Solved] Siduction Repository Timeout
« Last post by der_bud on Today at 21:21:18 »
... What do I need to change? Was muss ich noch ergänzen?

Hier bei mir fangen die entsprechenden Zeilen in der siduction.list mit
Code: [Select]
deb [signed-by=/usr/share/keyrings/siduction-archive-keyring.gpg] ... an
2
Upgrade Warnings / Re: [Solved] Siduction Repository Timeout
« Last post by Lanzi on Today at 19:05:32 »
Code: [Select]
Hinweis: Fehlendes Signed-By im Eintrag sources.list(5) für »https://ftp.gwdg.de/pub/linux/siduction/extra«
Hinweis: Fehlendes Signed-By im Eintrag sources.list(5) für »https://ftp.gwdg.de/pub/linux/siduction/fixes«

What do I need to change? Was muss ich noch ergänzen?
3
That appears to have fixed it.  Thanks.
4
Thanks towo, I will try that option also.
5
I did the full upgrade as stated above.  Still no change.  I'll try the ctrl-alt-F idea.  Thanks.
6
1. login on tty
2. become root
3. apt update && apt install plasma-desktop plasma-workspace

7
This is a periodically (re-)appearing effect, that to my knowledge is unique to the combination of the "sddm" display manager and KDE/plasma. The effect is, that the enter/return key does not do anything. I, myself, experienced it regularly when upgrading a live (Siduction) KDE-iso image. Sometimes even the window-decorations get lost.

Why am I telling this: Apart from @scholle1's valuable tip to boot into a terminal screen instead of the graphical greeting screen, you can also always do it, even once you are "on sddm". The "ctrl-alt-F?"-mechanism still works, even then!
So press (e.g. ctrl-alt-F3) and you are on a terminal window ("F1" contains the startup messages, "F2" is the sddm-screen"). After logging in from there, you can do anything that does not require "graphics", especially you can update/upgrade.
Usually after some time, when sddm/kde/plasma/qt got their act together, everything works "normal" again!
Such things only happen with rolling releases or sid/unstable (or experimental) versions, not the stable ones and rarely in testing(/trixie). It is the price we have to pay for it, especially during transitions.
9
If you can log into a terminal with one of the two variants, then try a “apt full-upgrade” as described above.
10
Neither one of those options did anything.  Pressing enter or clicking on the login button gets no response, almost like they aren't active.
Pages: [1] 2 3 ... 10