Disaster! I can't get to my Debian 12 login screen!

I mistakenly thought with kiauh, that I was installing klipper the KDE-Plasma clipboard tool. Anyway, I installed kiauh, klipper and then moonraker. But, when installing moonraker, my Debian 12 server did a reboot/restart midway through the installation of the package and my Debian login screen is gone and replaced with a tty login screen asking for my username and password, which I enter, but it will not accept them. How do I fix this mess? I want kiauh, klipper and moonraker off my system and my login screen back! Please help…

Refer:

1 Like

Two options

  • reload Debian 12 from your last backup
  • login at the tty as root and remove those packages
7 Likes

If something would ruin my system, I’d just restore a systemback snapshot.
Now if you don’t have a snapshot like that either with timeshift or systemback, the job is to investigate all changes that those install scripts made to your system, and revert all of them.
We could help you in this, but it would take maybe weeks.
It’s easier and faster to just reinstall, maybe backup some of your configs beforehand (such as /etc, ~/.config, but maybe your /home as a whole)…
So after reinstalling the system you don’t have to fiddle with all the bells and whistles you had successfully configured in your previous install.

6 Likes

@nevj @kovacslt Thank you both so much for your response. It is very much appreciated. The Debian 12 ‘Bookworm’ stable install is very much new and it was very difficult to achieve on this legacy system, which is a Dell Precision Tower 7910. Everywhere on the Internet it states to disenable secure boot prior to install. But, on this commercial grade Dell server, disenabling secure boot, is and was, anathema. Eventually, a hard reset was required to progress the matter, as the RAM has to be reset as well. I am somewhat techy and so, was also somewhat ashamed, that I had so many protracted issues doing a Debian install. Due to this, I don’t want to go though the labour of reinstalling just yet, given the considerable endeavour it took to achieve it.

I stupidly have not got to establishing a backup system yet. I am so very foolish. I should have just have taken a tarball and stashed it, in lieu of a proper backup system. A proper backup system was on the near-immediate TODO. But, obviously, not soon enough. I will not forget this learning in future.

Fortuitously, I was sshing into my Dell server, as standard, from my tablet, instead of working on it physically, directly, as I have come to favour the tactile nature of the touchscreen: I love Termux and it means that I am not desk-bound. I tried it and I still had access and was not blocked by the tty login which would not accept my username and password. I deleted those recently installed apps. I ripped them out at the roots. I also deleted the good klipper binary on my system as well, a casualty of war, due to being a bit impassioned and over-zealous to get that shite off my system. I fixed it after some fiddling and got the good binary back. The mischevious installs have wreaked havoc. One of my drivers, the FOSS driver for my graphics card was compromised as well as a result. I don’t even know this could happen!

I took the initiative to re-install the Nvidia proprietary graphics driver from the Debian 12 repository, to replace the FOSS driver installed by the initial Debian install and after some fiddling and tweaking, I got it to work. I value the performance improvement as I am intending to run and tune LLMs locally, otherwise I would reinstall the FOSS driver. Ideologically, I favour FOSS, but I am a FOSS pragmatist. If a proprietary driver is better for my usecase, I will not abstain.

I have not got the Debian graphical splash login working again yet, nor accessed any of the graphical environments, but the tty does now accept my username and password, which is a win. I installed Cinnamon in case GNOME and KDE-Plasma are compromised. There is still more to do. It is a mixed blessing, but it is really forcing me to get under-the-hood and apprise myself of the inner workings of the system and its reporting and logging and that can only be a good thing. I will write more later about what I have progressed and resolved and post any queries I have not been able to resolve by my own research and endeavour. I am still mid affray.

2 Likes

What is your native language and keyboard layout?
As non-english speaker I see the most common login problem is caused by different keyboard layout.
An example:
I may setup the password to contain the number “0”.
I may enter my password on a hungarian keyboard, but the key described as “0” actually enters “`” if the layout is set to english. So while I’m sure I enter the correct password, what I actually enter is wrong.
Double check the layout set up locally!

Wasn’t it one time requirement?

3 Likes

Well done thus far. Getting access with ssh is a real breakthrough.
The login manager ( probably gdm if you have gnome) is controlled by a daemon process. You can disable it simply by finding where the daemon binary is ( probably /usr/bin/gdm or /bin/gdm) then just rename it
mv gdm gdm.hide
then boot and you will get a console login on your screen.
That will be a bit more convenient … so you can work and find the problem
When you think you have it right , just rename gdm back to its original name
mv gdm.hide gdm

If you dont have gdm, it might be sddm or lightdm.

The login manager is configured in files in /etc… probably /etc/gdm.conf… and also /etc/logind.conf.
There are 3 things that can make a login manager hang

  • it is configured wrong
  • graphics drivers
  • it cant start X11…ie an Xorg problem… it needs X11 to display the screen.

Hope that helps
Regards
Neville

3 Likes

Great suggestion, been caught with that many times, also number pad not switched to numbers still on directions

1 Like

We quite often fall in that same trap :slight_smile:

1 Like

I have never encountered that, but I have been caught with the caps lock on.

2 Likes