![]() I don't know, but the only hack that would work regardless of what display manager is used would be to setup automatic login to the virtual terminal and then have it automatically force logout users and then restart the display manager. Or, it could have something to do with when we did the initial install so that maybe really old installs continue to work without this issue even though they keep their system up to date while newer installs (perhaps after systemd went into effect) do have this issue eventually. I still think it could be the result of something all of us having this issue have installed rather than configuration. I was hoping that by studying the configuration posted by one member in that thread who says he doesn't have this issue, I would be able to see a general solution. I haven't been able to find anything from searching the wiki or forums or google. Of course, if anyone already knows how to solve this or how I can diagnose the problem let me know. If anyone reading this is using either of those packages, please double check that you can log out of your desktop environment more than twice without crashing your display manager and let me know. If I had to guess, I would say either Steam or Chrony is the culprit. I installed steam by downloading … and doing make install and running steam from command line the first time. I also installed Steam, but not from repositories because the key was invalid. ![]()
0 Comments
Leave a Reply. |