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 *** This in particular has been reproducible on Arch Linux with Firefox 123 and Plasma 6.0.1 STEPS TO REPRODUCE 1. Play a video in full screen (unknown if this applies to all videos or just DRM) 2. After a few minutes, pause the video with spacebar 3. Unpause the video and screen will blank until you alt-tab/mash Esc to leave the fullscreen. You can also Ctrl+Alt+F2/F7 to "refresh" the HDMI connection OBSERVED RESULT Monitor registers an HDMI disconnection, need to perform some witchcraft to restore normal usage EXPECTED RESULT Video simply unpauses and starts playing SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 6.7.9.arch1-1 (available in About System) KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION
This could be related to https://bugs.kde.org/show_bug.cgi?id=482264
Does this happen if you change adaptive sync to "Never" or "Always" in the system settings too? This sounds a lot like the driver lets the refresh rate drop too low when playback is completely stopped
Created attachment 167025 [details] attachment-2407405-0.html I will try this again tonight and report back! If that works, maybe I'll add a note to the kde archwiki page On Tue, Mar 12, 2024, 08:07 Zamundaaa <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=483304 > > Zamundaaa <xaver.hugl@gmail.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Resolution|--- |WAITINGFORINFO > CC| |xaver.hugl@gmail.com > Status|REPORTED |NEEDSINFO > > --- Comment #2 from Zamundaaa <xaver.hugl@gmail.com> --- > Does this happen if you change adaptive sync to "Never" or "Always" in the > system settings too? This sounds a lot like the driver lets the refresh > rate > drop too low when playback is completely stopped > > -- > You are receiving this mail because: > You reported the bug.
There is no setting for adaptive sync in my settings, nor can I find documentation on where that would be. I'm using an X11 session, not wayland. I did disable "Allow applications to block compositing", but am open to other options. Some interesting events from the systemd journal, may or may not be related: Mar 12 22:00:48 neon org.kde.powerdevil.backlighthelper[939185]: Detected locale "C" with character encoding "ANSI_X3.4-1968", which is not UTF-8. Qt depends on a UTF-8 locale, and has switched to "C.UTF-8" instead. If this causes problems, reconfigure your locale. See the locale(1) manual for more information. Mar 12 22:00:58 neon kwin_x11[536768]: kwin_core: Failed to focus 0x1a0008b (error 8) Mar 12 22:05:44 neon kwin_x11[536768]: kwin_core: XCB error: 152 (BadDamage), sequence: 8798, resource id: 26119560, major code: 143 (DAMAGE), minor code: 3 (Subtract) Mar 12 21:18:54 neon systemsettings[898248]: qml: Page SubCategoryPage_QMLTYPE_110(0x6323cc9ef790) is already in the PageRow Mar 12 21:18:54 neon systemsettings[898248]: qml: Pushed pages do not conform to the rules. Please check the documentation. Mar 12 21:18:54 neon systemsettings[898248]: push (file:///usr/lib/qt6/qml/org/kde/kirigami/PageRow.qml:223) onActiveSubCategoryRowChanged (qrc:/qt/qml/org/kde/systemsettings/SubCategoryPage.qml:175) expression for onClicked (qrc:/qt/qml/org/kde/systemsettings/SubCategoryPage.qml:197) Mar 12 21:19:20 neon kwin_x11[536768]: OpenGL vendor string: Intel Mar 12 21:19:20 neon kwin_x11[536768]: OpenGL renderer string: Mesa Intel(R) HD Graphics 4000 (IVB GT2) Mar 12 21:19:20 neon kwin_x11[536768]: OpenGL version string: 4.2 (Compatibility Profile) Mesa 24.0.2-arch1.2 Mar 12 21:19:20 neon kwin_x11[536768]: OpenGL shading language version string: 4.20 Mar 12 21:19:20 neon kwin_x11[536768]: Driver: Intel Mar 12 21:19:20 neon kwin_x11[536768]: GPU class: IvyBridge Mar 12 21:19:20 neon kwin_x11[536768]: OpenGL version: 4.2 Mar 12 21:19:20 neon kwin_x11[536768]: GLSL version: 4.20 Mar 12 21:19:20 neon kwin_x11[536768]: Mesa version: 24.0.2 Mar 12 21:19:20 neon kwin_x11[536768]: Requires strict binding: yes Mar 12 21:19:20 neon kwin_x11[536768]: Virtual Machine: no Mar 12 21:19:20 neon kwin_x11[536768]: Timer query support: yes Mar 12 21:19:20 neon kwin_x11[536768]: BlurConfig::instance called after the first use - ignoring Mar 12 21:19:20 neon kwin_x11[536768]: KscreenConfig::instance called after the first use - ignoring Mar 12 21:19:20 neon kwin_x11[536768]: OverviewConfig::instance called after the first use - ignoring Mar 12 21:19:20 neon kwin_x11[536768]: SlideConfig::instance called after the first use - ignoring Mar 12 21:19:20 neon kwin_x11[536768]: SlidingPopupsConfig::instance called after the first use - ignoring Mar 12 21:19:20 neon kwin_x11[536768]: WindowViewConfig::instance called after the first use - ignoring Mar 12 21:19:20 neon kwin_x11[536768]: WobblyWindowsConfig::instance called after the first use - ignoring Mar 12 21:19:20 neon kwin_x11[536768]: ZoomConfig::instance called after the first use - ignoring (yes, my computer is ancient, but it's been working fine up to 6.0!)
One possible workaround is to disable CEC or DDC/CI on your TV/monitor
Okay, then this sounds more like a powerdevil / ddcutil issue. Not sure why it would only trigger with fullscreen windows though.