Summary: | Monitor instantly wakes up from energy saving in Wayland | ||
---|---|---|---|
Product: | [Plasma] Powerdevil | Reporter: | Mircea Kitsune <sonichedgehog_hyperblast00> |
Component: | general | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | enricobe, kwin-bugs-null, mail, natalie_clarius, nate, postix, sonichedgehog_hyperblast00, suse |
Priority: | NOR | ||
Version: | 5.24.4 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | https://invent.kde.org/plasma/kwin/-/commit/482a1f0fb5bddb6d376a6b8d39a04bc16786cc97 | Version Fixed In: | 6.0 |
Sentry Crash Report: |
Description
Mircea Kitsune
2022-04-12 15:42:17 UTC
> Graphics Platform: X11
Are you sure you're on Wayland? :) I guess you reported the bug while you were on X11?
(In reply to Nate Graham from comment #1) > Are you sure you're on Wayland? :) I guess you reported the bug while you were on X11? Yes: I use X11 due to this issue. I only logged into Wayland temporarily to test how the problem behaves in Plasma 5.24. I can confirm. For a fast check you can issue this command to turn the monitor off: $ sleep 0.5 && qdbus org.kde.kglobalaccel /component/org_kde_powerdevil invokeShortcut "Turn Off Screen" I have two desktop computers to test: 1. AMD Ryzen 5700G; integrated GPU; openSUSE Tumbleweed 20220412; KDE Plasma 5.24.2; Framework 5.93.0 The monitor turn on again a few seconds after turning off. 2. Intel i7-4770; integrated GPU; OpenSUSE Leap 15.3; The monitor looks like it's polling for a signal or so. Although it's not showing a picture its power LED goes on and off periodically. => Slightly different behavior between Intel an AMD, but one common issue: Under wayland it's not possible to really turn off the monitor. No issue with X11 (to test: sleep 0.5; xset dpms force off) Logs aren't helpful: # journalctl -f Apr 09 11:18:38 alone klauncher[8730]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Apr 09 11:18:38 alone kactivitymanagerd[8882]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Apr 09 11:18:38 alone akonadi_birthdays_resource[9179]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Apr 09 11:18:38 alone akonadi_followupreminder_agent[9182]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Apr 09 11:18:38 alone akonadi_akonotes_resource[9177]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Apr 09 11:18:38 alone akonadi_control[8986]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Apr 09 11:18:38 alone akonadi_maildispatcher_agent[9195]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Apr 09 11:18:38 alone akonadi_migration_agent[9198]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Apr 09 11:18:38 alone akonadi_indexing_agent[9184]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Apr 09 11:18:38 alone akonadi_contacts_resource[9180]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Apr 09 11:18:38 alone akonadi_mailmerge_agent[9197]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Apr 09 11:18:38 alone akonadi_archivemail_agent[9178]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Apr 09 11:18:38 alone akonadi_mailfilter_agent[9196]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Apr 09 11:18:38 alone akonadi_maildir_resource[9185]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Apr 09 11:18:38 alone akonadi_notes_agent[9200]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Apr 09 11:18:38 alone akonadi_ical_resource[9183]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Apr 09 11:18:38 alone baloorunner[10060]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Apr 09 11:18:38 alone kiod5[10432]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Apr 09 11:18:38 alone akonadi_newmailnotifier_agent[9199]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Apr 09 11:18:38 alone akonadi_sendlater_agent[9201]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Apr 09 11:18:38 alone kwrite[10286]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Apr 09 11:18:38 alone kwalletd5[9397]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Apr 09 11:18:38 alone akonadi_unifiedmailbox_agent[9210]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Apr 09 11:18:38 alone akonadi_davgroupware_resource[9181]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Apr 09 11:18:38 alone dolphin[10137]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Apr 09 11:18:39 alone rtkit-daemon[2175]: Supervising 6 threads of 3 processes of 1 users. Apr 09 11:18:39 alone rtkit-daemon[2175]: Successfully made thread 10512 of process 8958 owned by 'dom' RT at priority 5. Apr 09 11:18:39 alone rtkit-daemon[2175]: Supervising 7 threads of 3 processes of 1 users. A possibly relevant merge request was started @ https://invent.kde.org/plasma/kwin/-/merge_requests/2940 Only addition I can make is confirming the issue is heavily dependent on the monitor model. I just bought a new Samsung Odyssey to replace my Viewsonic monitor over multiple issues: Where the Viewsonic wouldn't normally stay in sleep under either X11 or Wayland, the Samsung does so in both with KScreen2 enabled and on either HDMI or DP cables. The old monitor was moved to another computer... on it standby actually works now, despite not working on the same cable on my box. And both machines use AMD cards, I forgot if I still enable amdgpu on my mother's PC which may explain why there it's working at least in X11. Hopefully affected monitor models will also be fixed, there seem to be quite a few especially around lower end products. I have the same problem on a Intel NUC (NUC12WSHi5) with Intel i5-1240P and the Xe integrated graphic. I've tested many workarounds found online, but nothing solved the problem. To be honest, I've also tested this problem on Fedora (GNOME) on Wayland and the monitor can't go in standby mode. Can this be considered a Wayland problem and not a Plasma/Qt issue? On X11 everything works fine. I post a workaround I found, maybe it can be useful for someone: I've set the monitor to use only the HDMI source instead of the "Auto" mode which automatically detects the video source. With "HDMI" mode the standby works fine while in "Auto" the screen never goes in standby. It seems that the monitor sends some kind of signal to the PC and it wakes up... Git commit 482a1f0fb5bddb6d376a6b8d39a04bc16786cc97 by Xaver Hugl. Committed on 27/09/2023 at 00:02. Pushed by zamundaaa into branch 'master'. backends/drm: don't wake displays up when outputs get temporarily removed When some displays go to sleep, that can be wrongly detected as a temporary hotunplug by the driver. In order to not wrongly wake up the system with such a display, detect that scenario and set the 'new' output to dpms off again. Related: bug 379474 M +22 -0 src/backends/drm/drm_backend.cpp M +1 -1 src/backends/drm/drm_backend.h M +3 -0 src/workspace.cpp https://invent.kde.org/plasma/kwin/-/commit/482a1f0fb5bddb6d376a6b8d39a04bc16786cc97 Hello, thank you very much for fixing this annoying issue! Can you please help me to understand in which version we should have this fixed? So I can check if it's solved on my configuration. On the latest Neon Unstable the monitor goes in stanby as expected. Many many many many many many thanks! I was stuck on X11 due to this problem <3 |