SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1a. Either install Neon Unstable from most recent live cd, (neon-unstable-20230702-1120.iso) or 1b. Do pkcon refresh and sudo pkcon update from previously installed, (and functioning) Neon Unstable partition 2. At login screen, type (correct) password at the prompt and press Enter OBSERVED RESULT - Screen goes black for a couple of seconds and then shows the login screen again. If you again type your (correct) password in, it again goes black for a couple of seconds then shows login screen again, ad infinitum, (i.e. you can't get to your desktop at all). - It's definitely not a password issue as if you type the incorrect password in, you still get the shake and "incorrect password" message. - Problem definitely does not exist on a system installed from "neon-unstable-20230625-1121.iso" so long as the system is not updated, (as of 2023-07-02). As soon as the system is updated, the problem will exist, making the computer useless. Note: updating from the 20230625-1121 iso up through 2023-07-01 worked fine. Something was pushed into the updates on 2023-07-02, (before the iso was generated) that caused the problem. EXPECTED RESULT Expected to be logged into the desktop with a functioning system. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: (functioning system from 0625 iso - 5.27.80; can't get to desktop with the 0702 updates, so can't tell you what those versions are) KDE Frameworks Version: (functioning system from 0625 iso - 5.240.0; can't get to desktop with the 0702 updates, so can't tell you what those versions are) Qt Version: (functioning system from 0625 iso - 6.5.1; can't get to desktop with the 0702 updates, so can't tell you what those versions are) ADDITIONAL INFORMATION
Moving to Neon, but it's likely to be a SDDM or another non-KDE issue. There should be a log entry from SDDM explaining why the session failed to start. Would you be able to attach it to the bug report? I've seen common causes for this behavior when /home runs out of storage space or mounted as read-only with other greeters.
(In reply to Ben Bonacci from comment #1) > Moving to Neon, but it's likely to be a SDDM or another non-KDE issue. > > There should be a log entry from SDDM explaining why the session failed to > start. Would you be able to attach it to the bug report? > I've seen common causes for this behavior when /home runs out of storage > space or mounted as read-only with other greeters. Afraid I already reformatted a few hours later to get back to a working system, sorry. Whatever this was isn't happening anymore after blowing away the previous partition and reinstalling several hours later, though I did change the filesystem from ext4, (default in Calamares) to btrfs with Timeshift so that I could easily continue if this kind of thing happened again, so not sure if something got pushed to update that fixed the issue or whether it was just a random fluke. Whatever it was shouldn't have been related to space since it was a pretty new, (~2 days old) previously new/empty (250gb ext4) partition, and since I was actively using the partition for those two days, it at least hadn't been mounted as read-only before the update. In any case, as I said, it's all good for me now, so you can close this for now if you'd like, and I can add back to this one to re-open if it happens again.
(In reply to publiclyvisibleemail from comment #2) > Whatever this was isn't happening anymore after blowing away the previous > partition and reinstalling several hours later, though I did change the > filesystem from ext4, (default in Calamares) to btrfs with Timeshift so that > I could easily continue if this kind of thing happened again, so not sure if > something got pushed to update that fixed the issue or whether it was just a > random fluke. Okay, I'll close this now. Feel free to reopen if the problem comes back.