To rid myself of an annoying Budgie icon during boot (leftover from when I installed and then removed the Budgie desktop environment), I issued this command : sudo update-alternatives --config default.plymouth
(found on this page: "Getting back Ubunutu's default boot splash" ) and changed the image from the default Budgie icon, back to the normal Ubuntu symbol.
No problem there. So I rebooted to see how it worked. And it worked great -- until I got to the login screen, where I got yet another login loop, where I type my password, hit enter, and it brings me right back.
I'm totally clueless as to how this came about, from switching the boot logo.
Thankfully, I'm still able to login using LXDE, which is what I'm using right now.
So I tried issuing the same command as before (sudo update-alternatives --config default.plymouth
) and changed it back to the Budgie icon, hoping that would fix it.
No luck. I still have a persistent login loop when trying to login to the Ubuntu desktop environment.
During one reboot, I was able to get some information by pressing F2 (I think), but I don't know if this is useful at all:
Any ideas as to what is causing the problem?? Help would be much appreciated.
Update: Using the LXDE desktop environment, I opened the "Logs" application, thinking there might be some useful information. The first entry looks very similar to the error that showed up on my boot screen shown in the second picture. The expanded entry farther down also looks like it could be important:
Does this "timed out" error have something to do with my fstab file? And if so, why would that effect the login manager??
~/.xsession-errors
filecat .xsession-errors
returns a 'no such file or directory', and searching in the file manager doesn't come up with anything either. Apparently it doesn't exist. Is there somewhere else I should look for clues?$XDG_CACHE_HOME/gdm/session.log
instead?cat $XDG_CACHE_HOME/gdm/session.log
doesn't give me anything either, and no luck with the file explorer. Would attempting a login with lightdm or another login manager be a good idea?