Hello, I encountered an SSDM problem, the system crashed, I selected to report to the developers, via an error prompt, (described below), but was unsuccessful.
The following is a detailed chronological list of events, commands, results, and remediation efforts. System information: uname -a Linux Debian 6.1.0-28-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.119-1 (2024-11-22) x86_64 GNU/Linux Additional Debian bookworm 12.8 x86_64 Kernel: 6.1.0-28-amd64 DE: KDE Plasma 5.27.5 WM Theme: BreezeLinux Debian 12, KDE plasma desktop environment. Issue/problem. After I lock the screen, and I accidentally hit the tab key on my keyboard. This results in the username and password fields longer being present, and I am unable to login via the GUI. This has happened in the past and I restarted via it via Alt Sys req REISUB And was able to login successfully. The most recent re-occurrence, was today, (12/27/2024) I locked the screen, and I accidentally hit the tab key on my keyboard when trying to log back in. The username and password fields disappeared, and my screen lock screen remained., (just no login credentials fields). Attempts to troubleshoot and access the GUI login I was able to login via dropping to the TTY (F2), After logging in I entered the following commands in this order. Restart the screen locker killall kscreenlocker_greet ( this command created no response/result) Attempted a second time, and nothing killall kscreenlocker_greet Then attempted to restart the display manager: sudo systemctl restart sddm That command caused the virtual console/TTY to crash, and I was greeted by a box: "Report issue to devs option, do you consent?" I agreed, and clicked the following options. - agree, share with devs - selected the check box on the following: - Yes, share information with developers. - Yes I remember what i was doing - No I did not retry - I remember what i was doing when the app crashed - Noticed unusual desktop behavior Before I could proceed, the spinning waiting wheel began, It was still spinning after 5 - 8 minutes. That is when I performed the hard reboot: Alt Sys req REISUB And, was able to login via GUI, and all worked fine. If this is a bug, and further information is needed, or if there is a setting/config file, I should edit, let me know. Sincerely, -Chris Sent with [Proton Mail](https://proton.me/mail/home) secure email. ------- Forwarded Message ------- From: chris.bingham <[email protected]> Date: On Friday, December 27th, 2024 at 11:48 AM Subject: Debian KDE SDDM login screen lock login issue, possible bug To: [email protected] <[email protected]> > Hello, > > I encountered an SSDM problem, system crashed, selected to report to the > developers, via an error prompt, (described below), but was unsuccessful. > > The following is a detailed chronological list of events, commands, results, > and remediation efforts. > > System information: > uname -a > Linux Debian 6.1.0-28-amd64 > #1 SMP PREEMPT_DYNAMIC Debian 6.1.119-1 (2024-11-22) x86_64 GNU/Linux > > Additional > Debian bookworm 12.8 x86_64 > Kernel: 6.1.0-28-amd64 > DE: KDE Plasma 5.27.5 > WM Theme: BreezeLinux Debian 12, KDE plasma desktop environment. > > Issue/problem. > After I lock the screen, and I accidentally hit the tab key on my keyboard. > This results in the username and password fields longer being present, and I > am unable to login via the GUI. > > This has happened in the past and I restarted via it via Alt Sys req REISUB > And was able to login successfully. > > The most recent re-occurrence, was today, (12/27/2024) > I locked the screen, and I accidentally hit the tab key on my keyboard when > trying to log back in. > > The username and password fields disappeard, and my screen lock screen > remained., (just no login fields). > > Attempts to troubleshoot and access the GUI login > I was able to login via dropping to the TTY (F2), > After logging in I entered the following commands in this order. > > Restart the screen locker > killall kscreenlocker_greet > ( this command created no response/result) > > Attempted a second time, and nothing > killall kscreenlocker_greet > > Then attempted to restart the display manager: > sudo systemctl restart sddm > > That command caused the virtual console/TTY to crash, and I was greeted by a > box: > "Report issue to devs option, do you consent?" > I agreed, and clicked the following options. > > - agree, share with devs > > - selected the check box on the following: > > - Yes, share information with developers. > > - Yes I remember what i was doing > > - No I did not retry > > - I remember what i was doing when the app crashed > > - Noticed unusual desktop behavior > > Before I could proceed, the spinning waiting wheel began, > It was still spinning after 5 - 8 minutes. > That is when I performed the hard reboot: Alt Sys req REISUB > And, was able to login via GUI, and all worked fine. > > If this is a bug, and further information is needed, or if there is a > setting/config file, I should edit, let me know. > > Sincerely, > -Chris > > Sent with [Proton Mail](https://proton.me/mail/home) secure email.
