Oops! Budgie broke my Nabia...
Last night I tried to install a new desktop, Budgie. Using Synaptic I selected almost all of the extra Budgie modules or applets. I did also get some updates alongside the Budgie download. When I was done with the download and installs I noticed the software updater still wanted to get a little update so I did that too.
When I rebooted and tried to switch to Budgie at the Login screen, I could not login.
Booting up looks a little different:
There is a new splash screen replacing the one with the Trisquel symbol,
One time the splash screen disappears and momentarily the screen is split horizontally in half with 2 different grays,
The last thing I see is the usual 'deblobbed kernel' message.
The Login screen looks like it normally does.
I type in my password and hit enter.
Screen blacks out for a moment then I see the 'deblobbed kernel message again and returns to the Login screen.
I try to go back to the Trisquel-mini desktop but the same thing happens. I just cannot login to Trisquel 10 period.
How should I go about rolling back to the working order?
Fortunately, I have Aramo on the same PC and am using it now.
Looking at https://trisquel.info/en/forum/bootup-wont-progress-past-login-step, I did rename .config file to old.config and rebooted. Still same result.
The new splash screen looks to be the budgie symbol, three infinity symbols in a circle.
Can you log in a text session? To find one, type Ctrl+Alt+F2 (for instance) at the log in screen. Any full partition (the 'df' command can tell)? Anything interesting in the journal (execute 'journalctl')? Does 'sudo apt update && sudo apt uprade' return any error?
Thank you Magic, I appreciate you - maybe I should have held off but being impatient I fixed the problem by giving PureOS a try. Fortunately I was able to backup all important data using Aramo installed on another HD in the same PC.
I did look at logs first and found something similar to this:
requirement "user ingroup nopasswdlogin" not met by user "rose"
(this is from an old thread, the wording that I saw was a little different). I do not remember which log had it but it was the only thing that looked like a clue that I found.
In case anyone with the same problem stumbles on this post, these two threads look relevant. The first is very recent, the 2nd rather long, old and recently updated.
https://www.maketecheasier.com/fix-ubuntu-login-loop/
https://askubuntu.com/questions/223501/ubuntu-gets-stuck-in-a-login-loop