On Aurora, after logging in with SDDM monitor will endlessly turn off and on with no display

[Blumoop]

Describe the bug

Hardware: i5-14500, Intel Arc A770, Samsung Odyssey G5 monitor

After doing a fresh install of Aurora 40, I can boot to SDDM and log in, and after a few seconds of getting into Plasma, my monitor will turn off, and then attempt to turn on and find a signal, and endlessly turn off and on.

Anyone else had this specific problem recently?

What did you expect to happen?

Log in to Plasma and be able to use it normally without monitor turning off and on.

Output of rpm-ostree status

I'm running aurora:stable, iso was downloaded today (Oct 31)

Output of groups

No response

Extra information or context

I wonder if it's a new KDE issue? I also nearly had the same problem on Solus. I'm probably going to try doing a bug report on KDE's issue tracker.

[dieselftw]

I'm running Bluefin and the screen turns off if I'm inactive for 30 seconds. This wasn't the case a few days ago. Sounds similar to this so I'm not gonna create a new issue.

I re-checked my display and power settings as well. Nothing's changed there.

[Blumoop]

I have reported this bug on KDE's issue tracker, https://bugs.kde.org/show_bug.cgi?id=495665

I suspect that it's a new bug that popped up recently with my monitor hardware, Plasma, and Wayland. On the latest version of EndeavourOS Neo I installed to pinpoint the issue, the same thing happens unless I switch to X11 (which is only a temporary solution). So this issue isn't specific to Aurora or Fedora KDE.

[Blumoop]

I'm running Bluefin and the screen turns off if I'm inactive for 30 seconds. This wasn't the case a few days ago. Sounds similar to this so I'm not gonna create a new issue.

I re-checked my display and power settings as well. Nothing's changed there.

I have found a workaround, if your monitor happens to have a setting related to switching outputs if a connected device turns on, turn it off and see what happens. This fixed it for me on Plasma.

[Blumoop]

Actually scratch that, that solution doesn't seem to work with Aurora or Fedora KDE unfortately.

[Blumoop]

Turns out this issue is likely because of the Samsung Odyssey G5 monitor, as my bug report is the same issue as two other people who have the same monitor. Hopefully the KDE devs are able to fix it soon.