Bug 510588

This is the Bugzilla product for plasma-login-manager, not SDDM.

That said, it sounds like this is a KWin issue, not an issue in SDDM or plasma-login-manager:

Oct 14 09:18:39 fedora sddm-helper-start-wayland[3951]: "kwin_wayland_drm: atomic commit failed: Permission denied\n"
Oct 14 09:18:39 fedora sddm-helper-start-wayland[3951]: "kwin_wayland_drm: Atomic modeset test failed! Permission denied\n"
Oct 14 09:18:39 fedora sddm-helper-start-wayland[3951]: "kwin_core: Applying output configuration failed!\n"
Oct 14 09:18:39 fedora sddm-helper-start-wayland[3951]: "kwin_wayland_drm: atomic commit failed: Permission denied\n"

Is there a kwin_wayland crash in the output of `coredumpctl --reverse`? If so, please follow the instructions at https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl

(In reply to Nate Graham from comment #1)
> This is the Bugzilla product for plasma-login-manager, not SDDM.
> 
> That said, it sounds like this is a KWin issue, not an issue in SDDM or
> plasma-login-manager:
> 
> Oct 14 09:18:39 fedora sddm-helper-start-wayland[3951]: "kwin_wayland_drm:
> atomic commit failed: Permission denied\n"
> Oct 14 09:18:39 fedora sddm-helper-start-wayland[3951]: "kwin_wayland_drm:
> Atomic modeset test failed! Permission denied\n"
> Oct 14 09:18:39 fedora sddm-helper-start-wayland[3951]: "kwin_core: Applying
> output configuration failed!\n"
> Oct 14 09:18:39 fedora sddm-helper-start-wayland[3951]: "kwin_wayland_drm:
> atomic commit failed: Permission denied\n"
> 
> Is there a kwin_wayland crash in the output of `coredumpctl --reverse`? If
> so, please follow the instructions at
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/
> How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl

Apologies for the wrong product placement, was not sure where it should go.

There are no entries in `coredumpctl --reverse` at the time when this happened.

Thanks, then I guess it's not crashing but rather quitting.

What's bugging me is that I can't seem to find anything noteworthy in the journal logs for both the black screen and the subsequent quit and then freeze in SDDM. I believe the kwin error logs you spotted occurred when the freeze happened however.

For more context I use LACT to apply a higher power usage limit and a slightly lower voltage for my GPU. This is stable every time I stress tested my GPU in benchmarks and video games. In my experience problems with overclocking/undervolting generally result in driver crashes that are very evident in logs, but still I'm not sure if this would be a likely culprit so it's probably worth mentioning.

It would be useful to know if the problem goes away if you return your GPU to its factory state.

Sure thing, I'll run on stock settings for a few days and I'll report back if it happens

Reporting back to say that the problem happened again even with GPU settings reset to defaults. This time I do not see the kwin_wayland_drm messages before in the journal logs. I've attached the entire journal log from the problematic boot.

Created attachment 185871 [details]
full journal log - 2

🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!

Happened again yesterday, nothing new or peculiar in the logs in comparison to the last times.

(In reply to Adi Efendic from comment #0)
> Sometimes when reaching the SDDM login screen after boot and after entering
> my credentials the screen turns black for ~60s after which I log in
> successfully. But then in like 10-15 seconds KDE seems to "crash" in some
> way since it returns me back to the SDDM login screen. There, if I enter my
> credentials to log in again SDDM freezes entirely and never recovers,
> forcing me to reboot.
Are you sure it actually crashes?
It sounds like *something* is switching you to the tty SDDM is on, while keeping the session running. That would also be consistent with the "permission denied" warnings, and not being able to log in again (as the session is already active). 
When it happens again, try switching through a bunch of ttys to find out if the session is still running.

🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!

🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.