https://bugs.kde.org/show_bug.cgi?id=466620
--- Comment #17 from Chema <rondo...@gmail.com> --- Sorry, not true, the new kernel doesn't fix the Powerdevil problem... I explain what has happened. I have a bi-directional EDID emulator connected to the HDMI output. This small connector is used to fool the computer into thinking that it is still receiving the HDMI signal from the monitor even if the HDMI cable is disconnected or other computer is active on a KVM switch. It is mainly used with KVM switches since it allows you to switch between computers instantly since it does not have to recover or readapt the video signal on the monitor when you change computers since the EDID emulator has it saved. It also has another function and that is to be able to use the computer with the monitor disconnected for remote control sessions with applications such as VNC, AnyDesk, etc. That's why the test worked for me, because I didn't realize when I did it that I had this little connector connected and then even if I changed the computer on the KVM switch, the Powerdevil continued to detect the HDMI signal and that's why it didn't fail. You can buy one of these plugs, it will solve the problem of the Powerdevil and they are not expensive at all. What is clear with this test is that the failure is in the interruption of the HDMI signal, at the moment it is cut, the Powerdevil crashes. If the EDID emulator is connected and the computer is still receiving a 'ghost' HDMI signal (provided by the EDID emulator), the Powerdevil does not fail and you can switch between computers without problem. What is certain is that with this version of the kernel one of the errors that it had has been fixed. With the version prior to 6.2.2, if the KDE + Wayland computer was suspended while having the bi-directional EDID emulator, switched to the Windows computer, and then went back to the Linux computer and woke it up, the KDE + Wayland session was completely locked and it was impossible to recover it (in X11 it worked fine). After installing kernel 6.2.2 now this problem in Wayland seems to be fixed. -- You are receiving this mail because: You are watching all bug changes.
