I seem to be cursed with a problem that has been addressed a number of times on these discussion boards. My GUI login window accepts the default pi/flightaware login/password combination, then goes dark for a few seconds and repaints the same login screen, but without the login/password entries that I have just made. I have seen numerous solutions suggested and tried on these boards, and many of them have worked, but for only others and never for me.
I know that I’m entering the correct login information, because whenever I vary the input (as a test), the system informs me “Incorrect password, please try again”.
I can log into the console using that same default login/password conversation, and can move about in console mode quite freely. I have examined both the presence and content of various files (as suggested by this and other boards) and find nothing amiss. Permissions all seem to be in order.
My system is about as vanilla as it can be. I started out with everything bright and shiny and right out of the box about a month ago. I was very happy when everything downloaded correctly, and installed properly…until I could not log into the the GUI. (And I need to do this, in part because I need to use VNC, and the FlightAware apparatus will be installed near my friend’s antenna tower. BTW, I get the same login blues when accessing via VNC. Both my friend and I need the GUI.)
In my search for answers, I have even gone beyond the flightaware community to the generic Raspbian and Raspberry Pi boards. I have even found very similar problems and advices the Ubuntu sources. I have found a lot of advice and tried everything that looked even remotely promising, but nothing helps. Because I’ve seen this exact same complaint and proposed answers on both FlightAware and Ubuntu boards, I’m fairly sure it’s a Linux problem and not a FlightAware problem.
I am running FlightAware 3.6.3 on a Raspberry Pi III+, with Raspbian OS downloaded from FlightAware about a month ago. The memory card has a capacity of 32 Gb (!), of which 27 Gb is still available. I did set up an option, very early on, to start the GUI upon boot. It worked right away. I don’t remember what I did to enable that behavior or where I saw the tutorial about how to do it, or I already would have tried turning it off and rebooting/starting it manually.
I’m not a Unix/Linux/Raspbian guru, by any means. But I’ve made my living writing C on MS-DOS, then Windows machines for forty+ years, so I do know my way around. I did some limited work in the mid-80’s on Xenix (Unix from Microsoft, of all things!), so I’m not entirely flummoxed by the OS.
I’ve tried the following, to no avail:
- chown .Xauthority file
- reconfigure lightdb system
- reinstall the lightdb system.
- numerous other attempts, followed by
- dozens and dozens of reboots
My point in posting this generic complaint, containing the proviso that I’ve tried everything I could find, is that this complaint appears to widely in the literature that it must be commonplace. And it has been happening for years. So it seems to me that there has to be a great deal of community experience in dealing with this problem, even to the extent of someone having put together a checklist/cheatsheet of everything to try when the “I can’t log in via the GUI” problem arises.
Is that magic bullet floating around the interwebs somewhere, and I’ve just not recognized it?