https://bugs.kde.org/show_bug.cgi?id=468971
--- Comment #18 from nick...@outlook.com --- (In reply to Zamundaaa from comment #16) > Sorry, this got completely lost in my emails. Looking at that log, I see > that KWin does the modeset for the three outputs correctly... but then KWin > only presents stuff on the one output until the next hotplug event comes in. > So this is at least unlikely to be a driver bug, as the driver never gets > the requests to show stuff. > > Can you still reproduce this on KWin 5.27.10? Sorry for the delay I actually did two tests, one from 17 days ago (January 23rd), and another one today (February 9th). The crash was able to occur when I tested it on January 23rd, but because I forgot to report it here, I tried testing it again today to see if I could recreate it again. I updated my system again today, and I spent about 20 minutes turning on and off the different monitors, but I wasn't able to get it to crash. It seems like the issue is fixed now. Here's the journalctl log and pacman.log from today: https://1drv.ms/f/s!Aj62egREH4PT1DTAgJABgF6XJ448?e=aaof5Q The crash on January 23rd took me roughly 10 - 15 minutes to trigger it. When it triggered, the GIGABYTE monitor was completely frozen, and once it was frozen, no amount of turning on and off any of the monitors fixed it again. Here's the journalctl log and crash logs from January 23rd if it helps : https://1drv.ms/f/s!Aj62egREH4PT1BPdebxJyAMYROt3?e=2NBx3e -- You are receiving this mail because: You are watching all bug changes.
