1. Forum
  2. Usenet
  3. COMP.SYS.RASPBERRY-PI

  • rpi4 login problem

    From [email protected]@21:1/5 to All on Tue Mar 28 18:06:46 2023
    I screwed up my rpi4 (4gig) running buster. I need advice on how to 'unscrew' it. For some reason my desktop icons and task bar(?) disappeared. I wanted to restart the gui without rebooting. I typed 'startx' which hung the system. Then I rebooted.
    The pi starts and the desktop comes up without any icons but with a login screen (options are shutdown or login). user pi is the default but when I type in the password the pi tries to restart the desktop which ends up with the login screen ... ad
    infinitum! How do I correct the startup so that I can be logged in as pi automagically. (This is what raspi-config is set to do). I can ssh into the pi so I know the pi working but I want the gui. Thanks for help and advice. I would rather fix than
    do a new buster install. --Steve

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From [email protected]@21:1/5 to jeshgrca on Tue Mar 28 19:44:17 2023
    On Tuesday, March 28, 2023 at 9:29:10 PM UTC-5, jeshgrca wrote:
    startx shouldn't have screwed anything up unless you were running as
    root AFAIK, but you could try messing with the .X* files in your home directory, something like 'mkdir Xfiles && mv .X* Xfiles/' and then try logging in. If that does nothing you can revert the previous command by running 'mv Xfiles/* . && rmdir Xfiles'.

    You could also try simply running 'raspi-config' over SSH and seeing if
    you can fix it that way.

    Issue resolved. In the long run it was as simple as 'sudo rm ~/.Xauthority'. I came to that attempt as one of the boot messages was timeout error on file /home/pi/.Xauthority. So I just deleted the file (ssh from another computer) and all was normal.
    Whew. --Steve

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From jeshgrca@21:1/5 to All on Tue Mar 28 21:29:08 2023
    startx shouldn't have screwed anything up unless you were running as
    root AFAIK, but you could try messing with the .X* files in your home directory, something like 'mkdir Xfiles && mv .X* Xfiles/' and then try
    logging in. If that does nothing you can revert the previous command by
    running 'mv Xfiles/* . && rmdir Xfiles'.

    You could also try simply running 'raspi-config' over SSH and seeing if
    you can fix it that way.
    --
    "If you can't explain it simply, you don't understand it well enough."
    - Attributed to Albert Einstein

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From jeshgrca@21:1/5 to [email protected] on Tue Mar 28 22:28:51 2023
    "[email protected]" <[email protected]> writes:

    On Tuesday, March 28, 2023 at 9:29:10 PM UTC-5, jeshgrca wrote:
    startx shouldn't have screwed anything up unless you were running as
    root AFAIK, but you could try messing with the .X* files in your home
    directory, something like 'mkdir Xfiles && mv .X* Xfiles/' and then try
    logging in. If that does nothing you can revert the previous command by
    running 'mv Xfiles/* . && rmdir Xfiles'.

    You could also try simply running 'raspi-config' over SSH and seeing if
    you can fix it that way.

    Issue resolved. In the long run it was as simple as 'sudo rm
    ~/.Xauthority'. I came to that attempt as one of the boot messages was timeout error on file /home/pi/.Xauthority. So I just deleted the
    file (ssh from another computer) and all was normal. Whew. --Steve

    Some pemissions/ownerships most likely got switched around, thus causing
    X to crash and kick you back to the login screen.
    --
    "If you can't explain it simply, you don't understand it well enough."
    - Attributed to Albert Einstein

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)