Unix & Linux Stack Exchange
Q&A for users of Linux, FreeBSD and other Unix-like operating systems
Latest Questions
2
votes
1
answers
183
views
Screen Energy Saving not working with KDE Wayland
My desktop uses Kubuntu 24.04, fully updated, with KDE Plasma 5.27.12. About a week ago I decided to give Wayland another try, and this time I found everything to work smoothly, except for the fact that the Screen Energy Saving option does not seem to work... To be precise, it does work initially, o...
My desktop uses Kubuntu 24.04, fully updated, with KDE Plasma 5.27.12. About a week ago I decided to give Wayland another try, and this time I found everything to work smoothly, except for the fact that the Screen Energy Saving option does not seem to work...
To be precise, it does work initially, once the idle time has elapsed, and the screen turns black. But it remains black for about 10 seconds only, then the screen comes back on again. Obviously, there is something overriding the settings defined (by me) in System Settings -> Power.
The very same thing happens if I turn off the screen via CLI (
kscreen-doctor -d off
), i.e. the screen remains black for about 10 seconds, then lights up again. If I choose to put the pc in sleep/hibernate mode after the same amount of time, the screen does not light up again, but this of course is not what I want.
After the screen lights up again, in System Settings -> Display and Monitor, there appears the following information:
*A new output has been added. Settings have been reloaded.* I get in fact the following, interesting, output:
tail -f /var/log/syslog
......
2025-02-14T16:15:20.425314+01:00 kaus kactivitymanagerd: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-14T16:15:20.425640+01:00 kaus kded5: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-14T16:15:20.425915+01:00 kaus polkit-kde-authentication-agent-1: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-14T16:15:20.426185+01:00 kaus foot: warn: wayland.c:1382: unknown global removed: 0x0000004f
2025-02-14T16:15:20.426443+01:00 kaus DiscoverNotifier: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-14T16:15:20.426480+01:00 kaus foot: wayland: unknown global removed: 0x0000004f
2025-02-14T16:15:20.426679+01:00 kaus plasmashell: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-14T16:15:20.426909+01:00 kaus xdg-desktop-portal-kde: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-14T16:15:20.446383+01:00 kaus org_kde_powerdevil: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-14T16:15:20.452066+01:00 kaus org_kde_powerdevil: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-14T16:15:20.456716+01:00 kaus org_kde_powerdevil: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-14T16:15:20.477425+01:00 kaus org_kde_powerdevil: Initializing "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
2025-02-14T16:15:20.487835+01:00 kaus org_kde_powerdevil: Initializing "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
2025-02-14T16:15:20.492526+01:00 kaus plasmashell: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-14T16:15:20.524998+01:00 kaus plasmashell: Initializing "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
2025-02-14T16:15:20.566383+01:00 kaus plasmashell: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-14T16:15:20.571856+01:00 kaus kded5: xsettingsd: Reloading configuration
2025-02-14T16:15:20.572028+01:00 kaus kded5: xsettingsd: Loaded 12 settings from /home/mario/.config/xsettingsd/xsettingsd.conf
2025-02-14T16:15:20.573351+01:00 kaus plasmashell: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-14T16:15:20.586841+01:00 kaus plasmashell: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
2025-02-14T16:15:20.600327+01:00 kaus plasmashell: Initializing "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
2025-02-14T16:15:20.602521+01:00 kaus plasmashell: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
2025-02-14T16:15:20.606076+01:00 kaus plasmashell: file:///usr/share/plasma/wallpapers/org.kde.slideshow/contents/ui/main.qml:20: TypeError: Cannot read property 'pluginName' of null
2025-02-14T16:15:20.606343+01:00 kaus plasmashell: file:///usr/share/plasma/wallpapers/org.kde.slideshow/contents/ui/main.qml:75: TypeError: Cannot read property 'configuration' of null
2025-02-14T16:15:20.606506+01:00 kaus plasmashell: file:///usr/share/plasma/wallpapers/org.kde.slideshow/contents/ui/main.qml:78: TypeError: Cannot read property 'pluginName' of null
2025-02-14T16:15:20.606659+01:00 kaus plasmashell: file:///usr/share/plasma/wallpapers/org.kde.slideshow/contents/ui/main.qml:80: TypeError: Cannot read property 'configuration' of null
2025-02-14T16:15:20.606797+01:00 kaus plasmashell: file:///usr/share/plasma/wallpapers/org.kde.slideshow/contents/ui/main.qml:81: TypeError: Cannot read property 'configuration' of null
2025-02-14T16:15:20.606941+01:00 kaus plasmashell: file:///usr/share/plasma/wallpapers/org.kde.slideshow/contents/ui/main.qml:82: TypeError: Cannot read property 'configuration' of null
2025-02-14T16:15:20.607092+01:00 kaus plasmashell: file:///usr/share/plasma/wallpapers/org.kde.slideshow/contents/ui/main.qml:83: TypeError: Cannot read property 'configuration' of null
2025-02-14T16:15:20.607265+01:00 kaus plasmashell: file:///usr/share/plasma/wallpapers/org.kde.slideshow/contents/ui/main.qml:84: TypeError: Cannot read property 'configuration' of null
2025-02-14T16:15:20.607421+01:00 kaus plasmashell: file:///usr/share/plasma/wallpapers/org.kde.slideshow/contents/ui/main.qml:16: TypeError: Cannot read property 'configuration' of null
2025-02-14T16:15:20.607579+01:00 kaus plasmashell: file:///usr/share/plasma/wallpapers/org.kde.slideshow/contents/ui/main.qml:17: TypeError: Cannot read property 'configuration' of null
2025-02-14T16:15:20.607733+01:00 kaus plasmashell: file:///usr/share/plasma/wallpapers/org.kde.slideshow/contents/ui/main.qml:18: TypeError: Cannot read property 'configuration' of null
2025-02-14T16:15:20.700216+01:00 kaus kded5: xsettingsd: Reloading configuration
2025-02-14T16:15:20.700254+01:00 kaus kded5: xsettingsd: Loaded 12 settings from /home/mario/.config/xsettingsd/xsettingsd.conf
2025-02-14T16:15:20.816145+01:00 kaus kwin_wayland_wrapper: OpenGL vendor string: Intel
2025-02-14T16:15:20.816430+01:00 kaus kwin_wayland_wrapper: OpenGL renderer string: Mesa Intel(R) UHD Graphics 630 (CFL GT2)
2025-02-14T16:15:20.816557+01:00 kaus kwin_wayland_wrapper: OpenGL version string: 4.6 (Core Profile) Mesa 24.2.8-1ubuntu1~24.04.1
2025-02-14T16:15:20.816656+01:00 kaus kwin_wayland_wrapper: OpenGL shading language version string: 4.60
2025-02-14T16:15:20.816745+01:00 kaus kwin_wayland_wrapper: Driver: Intel
2025-02-14T16:15:20.816825+01:00 kaus kwin_wayland_wrapper: GPU class: Coffee Lake
2025-02-14T16:15:20.816948+01:00 kaus kwin_wayland_wrapper: OpenGL version: 4.6
2025-02-14T16:15:20.817030+01:00 kaus kwin_wayland_wrapper: GLSL version: 4.60
2025-02-14T16:15:20.817110+01:00 kaus kwin_wayland_wrapper: Mesa version: 24.2.8
2025-02-14T16:15:20.817207+01:00 kaus kwin_wayland_wrapper: X server version: 1.23.2
2025-02-14T16:15:20.817330+01:00 kaus kwin_wayland_wrapper: Linux kernel version: 6.8
2025-02-14T16:15:20.817448+01:00 kaus kwin_wayland_wrapper: Requires strict binding: no
2025-02-14T16:15:20.817546+01:00 kaus kwin_wayland_wrapper: GLSL shaders: yes
2025-02-14T16:15:20.817643+01:00 kaus kwin_wayland_wrapper: Texture NPOT support: yes
2025-02-14T16:15:20.817738+01:00 kaus kwin_wayland_wrapper: Virtual Machine: no
2025-02-14T16:15:21.020900+01:00 kaus kwin_wayland_wrapper: BlurConfig::instance called after the first use - ignoring
2025-02-14T16:15:21.023996+01:00 kaus kwin_wayland_wrapper: ZoomConfig::instance called after the first use - ignoring
2025-02-14T16:15:21.025121+01:00 kaus kwin_wayland_wrapper: WindowViewConfig::instance called after the first use - ignoring
2025-02-14T16:15:21.026215+01:00 kaus kwin_wayland_wrapper: SlidingPopupsConfig::instance called after the first use - ignoring
2025-02-14T16:15:21.026382+01:00 kaus kwin_wayland_wrapper: SlideConfig::instance called after the first use - ignoring
2025-02-14T16:15:21.026613+01:00 kaus kwin_wayland_wrapper: OverviewConfig::instance called after the first use - ignoring
2025-02-14T16:15:21.027160+01:00 kaus kwin_wayland_wrapper: KscreenConfig::instance called after the first use - ignoring
2025-02-14T16:15:21.027885+01:00 kaus kwin_wayland_wrapper: DesktopGridConfig::instance called after the first use - ignoring
2025-02-14T16:15:21.500242+01:00 kaus org_kde_powerdevil: Initializing "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
2025-02-14T16:15:21.532164+01:00 kaus plasmashell: Initializing "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
2025-02-14T16:15:21.543067+01:00 kaus plasmashell: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
2025-02-14T16:15:21.543131+01:00 kaus plasmashell: Checking screens: available: (QScreen(0x5fedb26e8010, name="DP-3")) redundant: QHash() fake: QSet(QScreen(0x5fedb2832170, name="")) all: (QScreen(0x5fedb2832170, name=""), QScreen(0x5fedb26e8010, name="DP-3"))
2025-02-14T16:15:21.607762+01:00 kaus kded5: xsettingsd: Reloading configuration
2025-02-14T16:15:21.607819+01:00 kaus kded5: xsettingsd: Loaded 12 settings from /home/mario/.config/xsettingsd/xsettingsd.conf
2025-02-14T16:15:21.724534+01:00 kaus kwin_wayland_wrapper: OpenGL vendor string: Intel
2025-02-14T16:15:21.724669+01:00 kaus kwin_wayland_wrapper: OpenGL renderer string: Mesa Intel(R) UHD Graphics 630 (CFL GT2)
2025-02-14T16:15:21.724707+01:00 kaus kwin_wayland_wrapper: OpenGL version string: 4.6 (Core Profile) Mesa 24.2.8-1ubuntu1~24.04.1
2025-02-14T16:15:21.724742+01:00 kaus kwin_wayland_wrapper: OpenGL shading language version string: 4.60
2025-02-14T16:15:21.724769+01:00 kaus kwin_wayland_wrapper: Driver: Intel
2025-02-14T16:15:21.724802+01:00 kaus kwin_wayland_wrapper: GPU class: Coffee Lake
2025-02-14T16:15:21.724829+01:00 kaus kwin_wayland_wrapper: OpenGL version: 4.6
2025-02-14T16:15:21.724918+01:00 kaus kwin_wayland_wrapper: GLSL version: 4.60
2025-02-14T16:15:21.724948+01:00 kaus kwin_wayland_wrapper: Mesa version: 24.2.8
2025-02-14T16:15:21.724981+01:00 kaus kwin_wayland_wrapper: X server version: 1.23.2
2025-02-14T16:15:21.725010+01:00 kaus kwin_wayland_wrapper: Linux kernel version: 6.8
2025-02-14T16:15:21.725039+01:00 kaus kwin_wayland_wrapper: Requires strict binding: no
2025-02-14T16:15:21.725071+01:00 kaus kwin_wayland_wrapper: GLSL shaders: yes
2025-02-14T16:15:21.725102+01:00 kaus kwin_wayland_wrapper: Texture NPOT support: yes
2025-02-14T16:15:21.725170+01:00 kaus kwin_wayland_wrapper: Virtual Machine: no
2025-02-14T16:15:21.732241+01:00 kaus kwin_wayland_wrapper: BlurConfig::instance called after the first use - ignoring
2025-02-14T16:15:21.733999+01:00 kaus kwin_wayland_wrapper: ZoomConfig::instance called after the first use - ignoring
2025-02-14T16:15:21.735218+01:00 kaus kwin_wayland_wrapper: WindowViewConfig::instance called after the first use - ignoring
2025-02-14T16:15:21.736053+01:00 kaus kwin_wayland_wrapper: SlidingPopupsConfig::instance called after the first use - ignoring
2025-02-14T16:15:21.736185+01:00 kaus kwin_wayland_wrapper: SlideConfig::instance called after the first use - ignoring
2025-02-14T16:15:21.736374+01:00 kaus kwin_wayland_wrapper: OverviewConfig::instance called after the first use - ignoring
2025-02-14T16:15:21.736800+01:00 kaus kwin_wayland_wrapper: KscreenConfig::instance called after the first use - ignoring
2025-02-14T16:15:21.737320+01:00 kaus kwin_wayland_wrapper: DesktopGridConfig::instance called after the first use - ignoring
2025-02-14T16:15:21.807503+01:00 kaus plasmashell: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
2025-02-14T16:15:21.823266+01:00 kaus plasmashell: message repeated 3 times: [ qt.qpa.wayland: Wayland does not support QWindow::requestActivate()]
2025-02-14T16:15:22.372133+01:00 kaus DiscoverNotifier: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-14T16:15:22.372448+01:00 kaus foot: warn: wayland.c:1382: unknown global removed: 0x00000051
2025-02-14T16:15:22.372711+01:00 kaus polkit-kde-authentication-agent-1: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-14T16:15:22.372930+01:00 kaus kactivitymanagerd: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-14T16:15:22.373094+01:00 kaus kded5: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-14T16:15:22.373141+01:00 kaus foot: wayland: unknown global removed: 0x00000051
2025-02-14T16:15:22.373394+01:00 kaus xdg-desktop-portal-kde: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-14T16:15:22.373731+01:00 kaus plasmashell: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-14T16:15:22.397611+01:00 kaus org_kde_powerdevil: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-14T16:15:22.398211+01:00 kaus org_kde_powerdevil: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-14T16:15:22.404861+01:00 kaus org_kde_powerdevil: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-14T16:15:22.419837+01:00 kaus org_kde_powerdevil: Initializing "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
2025-02-14T16:15:22.427077+01:00 kaus org_kde_powerdevil: Initializing "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
2025-02-14T16:15:22.451625+01:00 kaus plasmashell: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-14T16:15:22.488961+01:00 kaus plasmashell: Initializing "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
2025-02-14T16:15:22.521557+01:00 kaus kded5: xsettingsd: Reloading configuration
2025-02-14T16:15:22.524481+01:00 kaus kded5: xsettingsd: Loaded 12 settings from /home/mario/.config/xsettingsd/xsettingsd.conf
2025-02-14T16:15:22.547828+01:00 kaus plasmashell: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-14T16:15:22.553843+01:00 kaus plasmashell: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-14T16:15:22.561598+01:00 kaus plasmashell: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
2025-02-14T16:15:22.576030+01:00 kaus plasmashell: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
2025-02-14T16:15:22.577459+01:00 kaus plasmashell: file:///usr/share/plasma/wallpapers/org.kde.slideshow/contents/ui/main.qml:20: TypeError: Cannot read property 'pluginName' of null
2025-02-14T16:15:22.577520+01:00 kaus plasmashell: file:///usr/share/plasma/wallpapers/org.kde.slideshow/contents/ui/main.qml:75: TypeError: Cannot read property 'configuration' of null
2025-02-14T16:15:22.577566+01:00 kaus plasmashell: file:///usr/share/plasma/wallpapers/org.kde.slideshow/contents/ui/main.qml:78: TypeError: Cannot read property 'pluginName' of null
2025-02-14T16:15:22.577591+01:00 kaus plasmashell: file:///usr/share/plasma/wallpapers/org.kde.slideshow/contents/ui/main.qml:80: TypeError: Cannot read property 'configuration' of null
2025-02-14T16:15:22.577613+01:00 kaus plasmashell: file:///usr/share/plasma/wallpapers/org.kde.slideshow/contents/ui/main.qml:81: TypeError: Cannot read property 'configuration' of null
2025-02-14T16:15:22.577639+01:00 kaus plasmashell: file:///usr/share/plasma/wallpapers/org.kde.slideshow/contents/ui/main.qml:82: TypeError: Cannot read property 'configuration' of null
2025-02-14T16:15:22.577663+01:00 kaus plasmashell: file:///usr/share/plasma/wallpapers/org.kde.slideshow/contents/ui/main.qml:83: TypeError: Cannot read property 'configuration' of null
2025-02-14T16:15:22.577686+01:00 kaus plasmashell: file:///usr/share/plasma/wallpapers/org.kde.slideshow/contents/ui/main.qml:84: TypeError: Cannot read property 'configuration' of null
2025-02-14T16:15:22.577738+01:00 kaus plasmashell: file:///usr/share/plasma/wallpapers/org.kde.slideshow/contents/ui/main.qml:16: TypeError: Cannot read property 'configuration' of null
2025-02-14T16:15:22.577761+01:00 kaus plasmashell: file:///usr/share/plasma/wallpapers/org.kde.slideshow/contents/ui/main.qml:17: TypeError: Cannot read property 'configuration' of null
2025-02-14T16:15:22.577795+01:00 kaus plasmashell: file:///usr/share/plasma/wallpapers/org.kde.slideshow/contents/ui/main.qml:18: TypeError: Cannot read property 'configuration' of null
2025-02-14T16:15:22.582656+01:00 kaus plasmashell: Initializing "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
2025-02-14T16:15:22.674442+01:00 kaus kded5: xsettingsd: Reloading configuration
2025-02-14T16:15:22.674478+01:00 kaus kded5: xsettingsd: Loaded 12 settings from /home/mario/.config/xsettingsd/xsettingsd.conf
2025-02-14T16:15:22.800943+01:00 kaus kwin_wayland_wrapper: OpenGL vendor string: Intel
2025-02-14T16:15:22.801060+01:00 kaus kwin_wayland_wrapper: OpenGL renderer string: Mesa Intel(R) UHD Graphics 630 (CFL GT2)
2025-02-14T16:15:22.801131+01:00 kaus kwin_wayland_wrapper: OpenGL version string: 4.6 (Core Profile) Mesa 24.2.8-1ubuntu1~24.04.1
2025-02-14T16:15:22.801256+01:00 kaus kwin_wayland_wrapper: OpenGL shading language version string: 4.60
2025-02-14T16:15:22.801345+01:00 kaus kwin_wayland_wrapper: Driver: Intel
2025-02-14T16:15:22.801561+01:00 kaus kwin_wayland_wrapper: GPU class: Coffee Lake
2025-02-14T16:15:22.801704+01:00 kaus kwin_wayland_wrapper: OpenGL version: 4.6
2025-02-14T16:15:22.801839+01:00 kaus kwin_wayland_wrapper: GLSL version: 4.60
2025-02-14T16:15:22.801982+01:00 kaus kwin_wayland_wrapper: Mesa version: 24.2.8
2025-02-14T16:15:22.802086+01:00 kaus kwin_wayland_wrapper: X server version: 1.23.2
2025-02-14T16:15:22.802246+01:00 kaus kwin_wayland_wrapper: Linux kernel version: 6.8
2025-02-14T16:15:22.802422+01:00 kaus kwin_wayland_wrapper: Requires strict binding: no
2025-02-14T16:15:22.802565+01:00 kaus kwin_wayland_wrapper: GLSL shaders: yes
2025-02-14T16:15:22.802709+01:00 kaus kwin_wayland_wrapper: Texture NPOT support: yes
2025-02-14T16:15:22.802906+01:00 kaus kwin_wayland_wrapper: Virtual Machine: no
2025-02-14T16:15:22.970701+01:00 kaus kwin_wayland_wrapper: BlurConfig::instance called after the first use - ignoring
2025-02-14T16:15:22.972646+01:00 kaus kwin_wayland_wrapper: ZoomConfig::instance called after the first use - ignoring
2025-02-14T16:15:22.973338+01:00 kaus kwin_wayland_wrapper: WindowViewConfig::instance called after the first use - ignoring
2025-02-14T16:15:22.974403+01:00 kaus kwin_wayland_wrapper: SlidingPopupsConfig::instance called after the first use - ignoring
2025-02-14T16:15:22.974496+01:00 kaus kwin_wayland_wrapper: SlideConfig::instance called after the first use - ignoring
2025-02-14T16:15:22.974650+01:00 kaus kwin_wayland_wrapper: OverviewConfig::instance called after the first use - ignoring
2025-02-14T16:15:22.974989+01:00 kaus kwin_wayland_wrapper: KscreenConfig::instance called after the first use - ignoring
2025-02-14T16:15:22.975489+01:00 kaus kwin_wayland_wrapper: DesktopGridConfig::instance called after the first use - ignoring
2025-02-14T16:15:23.144882+01:00 kaus org_kde_powerdevil: Initializing "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
2025-02-14T16:15:23.187486+01:00 kaus plasmashell: Initializing "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
2025-02-14T16:15:23.202846+01:00 kaus plasmashell: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
2025-02-14T16:15:23.202882+01:00 kaus plasmashell: Checking screens: available: (QScreen(0x5fedb2715a40, name="DP-3")) redundant: QHash() fake: QSet(QScreen(0x7058b000b3b0, name="")) all: (QScreen(0x7058b000b3b0, name=""), QScreen(0x5fedb2715a40, name="DP-3"))
2025-02-14T16:15:23.241293+01:00 kaus kded5: xsettingsd: Reloading configuration
2025-02-14T16:15:23.241339+01:00 kaus kded5: xsettingsd: Loaded 12 settings from /home/mario/.config/xsettingsd/xsettingsd.conf
2025-02-14T16:15:23.372171+01:00 kaus kwin_wayland_wrapper: OpenGL vendor string: Intel
2025-02-14T16:15:23.372240+01:00 kaus kwin_wayland_wrapper: OpenGL renderer string: Mesa Intel(R) UHD Graphics 630 (CFL GT2)
2025-02-14T16:15:23.372272+01:00 kaus kwin_wayland_wrapper: OpenGL version string: 4.6 (Core Profile) Mesa 24.2.8-1ubuntu1~24.04.1
2025-02-14T16:15:23.372302+01:00 kaus kwin_wayland_wrapper: OpenGL shading language version string: 4.60
2025-02-14T16:15:23.372333+01:00 kaus kwin_wayland_wrapper: Driver: Intel
2025-02-14T16:15:23.372393+01:00 kaus kwin_wayland_wrapper: GPU class: Coffee Lake
2025-02-14T16:15:23.372425+01:00 kaus kwin_wayland_wrapper: OpenGL version: 4.6
2025-02-14T16:15:23.372460+01:00 kaus kwin_wayland_wrapper: GLSL version: 4.60
2025-02-14T16:15:23.372498+01:00 kaus kwin_wayland_wrapper: Mesa version: 24.2.8
2025-02-14T16:15:23.372537+01:00 kaus kwin_wayland_wrapper: X server version: 1.23.2
2025-02-14T16:15:23.372572+01:00 kaus kwin_wayland_wrapper: Linux kernel version: 6.8
2025-02-14T16:15:23.372624+01:00 kaus kwin_wayland_wrapper: Requires strict binding: no
2025-02-14T16:15:23.372653+01:00 kaus kwin_wayland_wrapper: GLSL shaders: yes
2025-02-14T16:15:23.372686+01:00 kaus kwin_wayland_wrapper: Texture NPOT support: yes
2025-02-14T16:15:23.372717+01:00 kaus kwin_wayland_wrapper: Virtual Machine: no
2025-02-14T16:15:23.384230+01:00 kaus kwin_wayland_wrapper: BlurConfig::instance called after the first use - ignoring
2025-02-14T16:15:23.386218+01:00 kaus kwin_wayland_wrapper: ZoomConfig::instance called after the first use - ignoring
2025-02-14T16:15:23.386909+01:00 kaus kwin_wayland_wrapper: WindowViewConfig::instance called after the first use - ignoring
2025-02-14T16:15:23.387691+01:00 kaus kwin_wayland_wrapper: SlidingPopupsConfig::instance called after the first use - ignoring
2025-02-14T16:15:23.387765+01:00 kaus kwin_wayland_wrapper: SlideConfig::instance called after the first use - ignoring
2025-02-14T16:15:23.387968+01:00 kaus kwin_wayland_wrapper: OverviewConfig::instance called after the first use - ignoring
2025-02-14T16:15:23.388367+01:00 kaus kwin_wayland_wrapper: KscreenConfig::instance called after the first use - ignoring
2025-02-14T16:15:23.388886+01:00 kaus kwin_wayland_wrapper: DesktopGridConfig::instance called after the first use - ignoring
2025-02-14T16:15:23.489964+01:00 kaus plasmashell: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
from which we can see that kactivitymanager, for some unspecified reason, decides that it must create a fake Qt screen to avoid it crashing. And this happens several times in the course of a few seconds, until the situation stabilizes, and there are no more related activities in *syslog*.
Another important detail is added by a capture of the *dbus* connections:
date > cap.txt; kscreen-doctor --dpms off; dbus-monitor --profile >> cap.txt
and the content of the capture file, *cap.txt*, is:
Fri Feb 14 04:08:49 PM CET 2025
#type timestamp serial sender destination path interface member
# in_reply_to
sig 1739545729.278759 2 org.freedesktop.DBus :1.68 /org/freedesktop/DBus org.freedesktop.DBus NameAcquired
sig 1739545729.278766 4 org.freedesktop.DBus :1.68 /org/freedesktop/DBus org.freedesktop.DBus NameLost
mc 1739545730.964295 280 :1.41 :1.49 /org/freedesktop/portal/desktop org.freedesktop.impl.portal.Background GetAppState
mr 1739545730.965055 239 :1.49 :1.41 280
mc 1739545730.966093 281 :1.41 :1.43 /org/freedesktop/impl/portal/PermissionStore org.freedesktop.impl.portal.PermissionStore Lookup
err 1739545730.966962 71 :1.43 :1.41 281
mc 1739545735.968323 282 :1.41 :1.49 /org/freedesktop/portal/desktop org.freedesktop.impl.portal.Background GetAppState
mr 1739545735.969096 240 :1.49 :1.41 282
mc 1739545735.970145 283 :1.41 :1.43 /org/freedesktop/impl/portal/PermissionStore org.freedesktop.impl.portal.PermissionStore Lookup
err 1739545735.970998 72 :1.43 :1.41 283
sig 1739545740.179599 187 :1.26 /kwinrc org.kde.kconfig.notify ConfigChanged
mc 1739545740.180923 389 :1.21 org.freedesktop.DBus /org/freedesktop/DBus org.freedesktop.DBus AddMatch
The initial time of the *dbus* capture, 1739545729, corresponds to Friday, February 14, 2025 4:08:49 PM GMT+01:00, which is also the output of the *date* command immediately before the command that turns off the monitor. We see that about *11* seconds after the turning off *kwin* sends out a signal that the configuration has changed, which presumably is the consequence of *kded5* having created a fake Qt screen. But what exactly triggers this funny behavior?
The amusing thing is that the very same configuration works flawlessly in an X11 session, it is broken only in a Wayland session. But despite this, it is not clear to me at all whether this is a Wayland or a KDE bug. I googled *qt.qpa.wayland: Creating a fake screen in order for Qt not to crash*, which leads to a meager two references, the most relevant of which states:
> The issue is most likey in wayland or the DE as they are not closing the portal,
(whatever the portal may be). But here too, no consensus was reached as to the real culprit.
Can anyone help? I am at a loss, thank you.
MariusMatutiae
(4384 rep)
Feb 12, 2025, 04:24 PM
• Last activity: Feb 20, 2025, 11:50 PM
4
votes
2
answers
1916
views
Gnome does not wake up the monitor anymore on keypress
Since around the middle of October 2020, my Arch Linux machines don't wake up the monitor anymore when I press any key in the Gnome login screen. However the machine itself is woken up, as I see my keypresses as password entries or am even locked if I press enter due to too many login attempts once...
Since around the middle of October 2020, my Arch Linux machines don't wake up the monitor anymore when I press any key in the Gnome login screen. However the machine itself is woken up, as I see my keypresses as password entries or am even locked if I press enter due to too many login attempts once I wake the monitor up by switching to another console via CTRL+ALT+Fx and back.
What has changed and how can I restore the original functionality?
P.S.: The problem has resurfaced with another machine in February of 2025, I will first try the "IgnoreLid=true" as it is a desktop PC and will try the workaround next if that doesn't help.
Konrad Höffner
(1028 rep)
Oct 31, 2020, 05:36 PM
• Last activity: Feb 18, 2025, 10:39 AM
10
votes
2
answers
3645
views
What keeps waking up my screen?
I have screen energy saving enabled, but my monitors never turn off automatically - even when the screen is locked. I can -briefly- manually turn them off using `xset dpms force off`, but in a couple of seconds both of my monitors turn on again, without any interaction from me. Is there a way to fin...
I have screen energy saving enabled, but my monitors never turn off automatically - even when the screen is locked. I can -briefly- manually turn them off using
xset dpms force off
, but in a couple of seconds both of my monitors turn on again, without any interaction from me.
Is there a way to find out why this keeps happening? Can a running application do this, and if so, how would I identify the culprit?
OS is Debian 10 64-bit with KDE 5.
jaymmer - Reinstate Monica
(835 rep)
Aug 26, 2021, 12:21 PM
• Last activity: Aug 18, 2023, 01:24 PM
2
votes
4
answers
2876
views
Xserver sets monitor to sleep after 10 minutes
My installation, Ubuntu server 14.04 with just xorg and firefox installed. The server boots up and immediatly starts firefox with the disired webpage in fullscreen mode. After 10 minutes my monitor goes to sleep. How can i disable the sleep function of the monitor?
My installation,
Ubuntu server 14.04 with just xorg and firefox installed.
The server boots up and immediatly starts firefox with the disired webpage in fullscreen mode.
After 10 minutes my monitor goes to sleep.
How can i disable the sleep function of the monitor?
thomasd35
(23 rep)
Sep 24, 2015, 01:26 PM
• Last activity: Jul 23, 2023, 01:03 AM
0
votes
0
answers
537
views
Monitors wake up immediately after energy saving and windows switches to the left-most monitor
I'm going to explain in better detail. I have two monitors: [VGA] [HDMI] HDMI (right monitor) should be the primary monitor, while the VGA the secondary monitor. [![Display Configuration][1]][1] [1]: https://i.sstatic.net/eIISI.png I have energy saving and lock screen enabled, the issue is that when...
I'm going to explain in better detail.
I have two monitors:
[VGA] [HDMI]
HDMI (right monitor) should be the primary monitor, while the VGA the secondary monitor.
I have energy saving and lock screen enabled, the issue is that when energy saving kicks in and monitors go to sleep, they immediately wake up and stay on. Also all the windows and cursor move to the left-most monitor (where primary is not checked).
I observed this using Ubuntu (XFCE and KDE).
I also tried Regolith, similar issue happened when monitors went to sleep, but there each second a new virtual desktop was created endlessly, instead of switching programs windows.
Also as you can notice in the screenshot "An output has been removed. Settings have been reloaded". This message is showed after the monitor wakes up immediately after sleep.
**What I tried**:
- Partially resolved the wake up disabling Kscreen2 on KDE, but it
is not an ideal solution.
- udevadm control --stop, this prevents the wake up and windows switching, but it's even a worse solution.
I want also to add that during boot the following message is showed:
ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GP17.VGA.LCD._BCM.AFN7]
System Info:
**uname**:
- Linux finch-desktop 5.15.0-67-generic #74-Ubuntu SMP Wed Feb 22 14:14:39 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
**inxi**:

System:
Host: finch-desktop Kernel: 5.15.0-67-generic x86_64 bits: 64 compiler: gcc
v: 11.3.0 Desktop: KDE Plasma 5.24.7
Distro: Ubuntu 22.04.2 LTS (Jammy Jellyfish)
Machine:
Type: Desktop Mobo: ASRock model: A320M-HDV R4.0
serial: UEFI: American Megatrends v: P7.20
date: 04/27/2022
CPU:
Info: 6-core model: AMD Ryzen 5 5600G with Radeon Graphics bits: 64
type: MT MCP arch: Zen 3 rev: 0 cache: L1: 384 KiB L2: 3 MiB L3: 16 MiB
Speed (MHz): avg: 2863 high: 4450 min/max: 1400/4464 boost: enabled
cores: 1: 2384 2: 2400 3: 2396 4: 2400 5: 2400 6: 2999 7: 2401 8: 3559
9: 4450 10: 3560 11: 2415 12: 2998 bogomips: 93601
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
Device-1: AMD Cezanne driver: amdgpu v: 5.18.13 bus-ID: 06:00.0
Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: amdgpu,ati
unloaded: fbdev,modesetting,vesa gpu: amdgpu resolution: 1: 1920x1080~60Hz
2: 1920x1080~60Hz
OpenGL: renderer: RENOIR (renoir LLVM 15.0.3 DRM 3.48 5.15.0-67-generic)
v: 4.6 Mesa 22.3.0-devel direct render: Yes
Audio:
Device-1: AMD Renoir Radeon High Definition Audio driver: snd_hda_intel
v: kernel bus-ID: 06:00.1
Device-2: AMD Family 17h HD Audio vendor: ASRock driver: snd_hda_intel
v: kernel bus-ID: 06:00.6
Device-3: Logitech Headset H340 type: USB
driver: hid-generic,snd-usb-audio,usbhid bus-ID: 1-2:2
Sound Server-1: ALSA v: k5.15.0-67-generic running: yes
Sound Server-2: PulseAudio v: 15.99.1 running: yes
Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: ASRock driver: r8169 v: kernel port: f000 bus-ID: 05:00.0
IF: enp5s0 state: up speed: 100 Mbps duplex: full mac: a8:a1:59:5b:4d:4b
IF-ID-1: docker0 state: down mac: 02:42:f8:4c:05:70
IF-ID-2: ham0 state: unknown speed: 10 Mbps duplex: full
mac: 7a:79:19:3e:f8:72
Drives:
Local Storage: total: 5.01 TiB used: 737.2 GiB (14.4%)
ID-1: /dev/sda vendor: Western Digital model: WD5002ABYS-02B1B0
size: 465.76 GiB
ID-2: /dev/sdb vendor: Crucial model: CT500MX500SSD1 size: 465.76 GiB
ID-3: /dev/sdc vendor: Toshiba model: DT01ACA050 size: 465.76 GiB
ID-4: /dev/sdd type: USB vendor: Kingston model: DataTraveler 3.0
size: 7.2 GiB
ID-5: /dev/sdf type: USB vendor: Toshiba model: EXTERNAL USB
size: 3.64 TiB
Partition:
ID-1: / size: 456.89 GiB used: 165.52 GiB (36.2%) fs: ext4 dev: /dev/sdb2
ID-2: /boot/efi size: 512 MiB used: 6.1 MiB (1.2%) fs: vfat
dev: /dev/sda2
Swap:
ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) file: /swapfile
Sensors:
System Temperatures: cpu: N/A mobo: N/A gpu: amdgpu temp: 28.0 C
Fan Speeds (RPM): N/A
Info:
Processes: 383 Uptime: 46m Memory: 10.57 GiB used: 4.2 GiB (39.7%)
Init: systemd runlevel: 5 Compilers: gcc: 11.3.0 Packages: 2278 Shell: Bash
v: 5.1.16 inxi: 3.3.13
**lspci**:
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne Root Complex
00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge
00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge
00:02.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge
00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge
00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus
00:08.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 51)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 0
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 1
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 2
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 3
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 4
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 5
00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 6
00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 7
01:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] Device 43bc (rev 02)
01:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] Device 43b8 (rev 02)
01:00.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43b3 (rev 02)
02:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02)
02:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02)
02:07.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02)
05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
06:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne (rev c9)
06:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Radeon High Definition Audio Controller
06:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) Platform Security Processor
06:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne USB 3.1
06:00.4 USB controller: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne USB 3.1
06:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller
07:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 81)
07:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 81)
**udevadm monitor logs when the issue happens**:
KERNEL[626.770830] change /devices/pci0000:00/0000:00:08.1/0000:06:00.0/drm/card0 (drm)
ACTION=change
DEVPATH=/devices/pci0000:00/0000:00:08.1/0000:06:00.0/drm/card0
SUBSYSTEM=drm
HOTPLUG=1
DEVNAME=/dev/dri/card0
DEVTYPE=drm_minor
SEQNUM=4457
MAJOR=226
MINOR=0
UDEV [626.777794] change /devices/pci0000:00/0000:00:08.1/0000:06:00.0/drm/card0 (drm)
ACTION=change
DEVPATH=/devices/pci0000:00/0000:00:08.1/0000:06:00.0/drm/card0
SUBSYSTEM=drm
HOTPLUG=1
DEVNAME=/dev/dri/card0
DEVTYPE=drm_minor
SEQNUM=4457
USEC_INITIALIZED=4036211
ID_PATH=pci-0000:06:00.0
ID_PATH_TAG=pci-0000_06_00_0
ID_FOR_SEAT=drm-pci-0000_06_00_0
MAJOR=226
MINOR=0
DEVLINKS=/dev/dri/by-path/pci-0000:06:00.0-card
TAGS=:snap_barrier_barriers:snap_remmina_remmina:seat:snap_barrier_barrierc:uaccess:snap_barrier_barrier:snap_chromium_chromium:snap_telegram-desktop_telegram-desktop:snap_firefox_geckodriver:snap_chromium_chromedriver:master-of-seat:snap_firefox_firefox:
CURRENT_TAGS=:snap_barrier_barrier:master-of-seat:snap_firefox_geckodriver:snap_firefox_firefox:snap_chromium_chromedriver:uaccess:snap_barrier_barrierc:snap_barrier_barriers:snap_telegram-desktop_telegram-desktop:seat:snap_remmina_remmina:snap_chromium_chromium:
KERNEL[627.349125] change /devices/pci0000:00/0000:00:08.1/0000:06:00.0/drm/card0 (drm)
ACTION=change
DEVPATH=/devices/pci0000:00/0000:00:08.1/0000:06:00.0/drm/card0
SUBSYSTEM=drm
HOTPLUG=1
DEVNAME=/dev/dri/card0
DEVTYPE=drm_minor
SEQNUM=4458
MAJOR=226
MINOR=0
UDEV [627.355763] change /devices/pci0000:00/0000:00:08.1/0000:06:00.0/drm/card0 (drm)
ACTION=change
DEVPATH=/devices/pci0000:00/0000:00:08.1/0000:06:00.0/drm/card0
SUBSYSTEM=drm
HOTPLUG=1
DEVNAME=/dev/dri/card0
DEVTYPE=drm_minor
SEQNUM=4458
USEC_INITIALIZED=4036211
ID_PATH=pci-0000:06:00.0
ID_PATH_TAG=pci-0000_06_00_0
ID_FOR_SEAT=drm-pci-0000_06_00_0
MAJOR=226
MINOR=0
DEVLINKS=/dev/dri/by-path/pci-0000:06:00.0-card
TAGS=:master-of-seat:snap_barrier_barrier:snap_barrier_barrierc:snap_chromium_chromedriver:snap_remmina_remmina:uaccess:snap_chromium_chromium:snap_barrier_barriers:snap_telegram-desktop_telegram-desktop:snap_firefox_firefox:snap_firefox_geckodriver:seat:
CURRENT_TAGS=:snap_remmina_remmina:snap_chromium_chromedriver:snap_firefox_geckodriver:snap_telegram-desktop_telegram-desktop:snap_firefox_firefox:snap_barrier_barrier:master-of-seat:snap_chromium_chromium:uaccess:snap_barrier_barrierc:seat:snap_barrier_barriers:
Thank you for reading.
**Edit**:
- Tried Fedora KDE, same issue
- Solus KDE, same issue
- Solus Budgie, same issue
hy8484
(1 rep)
Mar 23, 2023, 09:37 AM
• Last activity: Mar 23, 2023, 03:26 PM
1
votes
1
answers
1134
views
Disable energy saving settings completely? HDMI signal lost (DPMS and screensaver already disabled)
On my MX Linux XFCE environment I have the problem that after a certain time without interaction after power on the HDMI signal is lost and can only be retrieved with pressing a keyboard key. I would that the HDMI signal or display never switched off. I have already deactivated DPMS and the screensa...
On my MX Linux XFCE environment I have the problem that after a certain time without interaction after power on the HDMI signal is lost and can only be retrieved with pressing a keyboard key. I would that the HDMI signal or display never switched off. I have already deactivated DPMS and the screensaver. Apparently this is not enough. Do you have any ideas about the possible cause? I'm using a nvidia optimus card if this information is relevant.
$ xset -q
...
Keyboard Control:
auto repeat: on key click percent: 0 LED mask: 00000000
XKB indicators:
00: Caps Lock: off 01: Num Lock: off 02: Scroll Lock: off
03: Compose: off 04: Kana: off 05: Sleep: off
06: Suspend: off 07: Mute: off 08: Misc: off
09: Mail: off 10: Charging: off 11: Shift Lock: off
12: Group 2: off 13: Mouse Keys: off
auto repeat delay: 500 repeat rate: 20
auto repeating keys: 00ffffffdffffbbf
fadfffefffedffff
9fffffffffffffff
fff7ffffffffffff
bell percent: 50 bell pitch: 400 bell duration: 100
Pointer Control:
acceleration: 22/5 threshold: 4
Screen Saver:
prefer blanking: yes allow exposures: yes
timeout: 0 cycle: 600
Colors:
default colormap: 0x22 BlackPixel: 0x0 WhitePixel: 0xffffff
Font Path:
/usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/75dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,/usr/share/fonts/X11/75dpi,built-ins
DPMS (Energy Star):
Standby: 600 Suspend: 600 Off: 600
DPMS is Disabled
$ xdg-screensaver status
disabled
Mike
(121 rep)
Oct 21, 2020, 06:09 PM
• Last activity: Oct 22, 2020, 08:44 PM
0
votes
1
answers
1159
views
Intel i915 and xbacklight: No outputs have backlight property
When I run `xbacklight` I get xbacklight No outputs have backlight property I've seen other posts mentions this but I do have a `/sys/class/backlight/intel_backlight`. I can write to the file and this works perfectly fine echo 1000 > /sys/class/backlight/intel_backlight/brightness # (dim) echo 4000...
When I run
xbacklight
I get
xbacklight
No outputs have backlight property
I've seen other posts mentions this but I do have a /sys/class/backlight/intel_backlight
. I can write to the file and this works perfectly fine
echo 1000 > /sys/class/backlight/intel_backlight/brightness # (dim)
echo 4000 > /sys/class/backlight/intel_backlight/brightness # (bright)
I'm using the Intel i915 video driver.
Evan Carroll
(34663 rep)
Apr 27, 2019, 01:26 AM
• Last activity: Dec 23, 2019, 03:54 AM
6
votes
1
answers
3816
views
Is there a better way than this to force monitor blank/off?
Intending to switch off the display/monitor/screen instantly (and only be reenabled upon keypress) I resort to this solution: * a `/bin/blankvt` script: #!/bin/sh echo 1 > /sys/devices/pci0000:00/0000:00:02.0/graphics/fb0/blank read keypress chvt 2 * a `/bin/blank` script: #!/bin/sh openvt -s -f -c...
Intending to switch off the display/monitor/screen instantly (and only be reenabled upon keypress) I resort to this solution:
* a
/bin/blankvt
script:
#!/bin/sh
echo 1 > /sys/devices/pci0000:00/0000:00:02.0/graphics/fb0/blank
read keypress
chvt 2
* a /bin/blank
script:
#!/bin/sh
openvt -s -f -c 40 /bin/blankvt
Having setup this I can simply call blank
on the command line and the
screen will go off and energy is saved. Great!
While this solution works right now, it appears hackish and brittle and what I seek is the correct way to achieve the same effect.
Typing blank
at the shell prompt should result in the screen to be turned off.
My question hence: how can I switch of the monitor "*correctly*"?
**Background/Motivation**
I am not connected to the electrical grid, conserving energy is paramount to me. I need to have the laptop/PC do some calculations but would desire to turn off the superflous energy consumption by the display (which seems a non neglectible consumer anyway).
Best if I could achieve this within:
- GNOME Shell 3.32.2.
- Linux 5.xx
humanityANDpeace
(15092 rep)
Jul 11, 2019, 02:01 PM
• Last activity: Jul 11, 2019, 02:34 PM
1
votes
1
answers
1979
views
Gnome3 - set screen energy settings from command line (script)
Is there a way to access, set gnome system-settings from the command-line? I'm specifically interested in a way to set: settings -> energy -> screen off = never settings -> energy -> screen off = (N) minue(s) I would like to access this settings from a bash script, so I could set screen-off to `neve...
Is there a way to access, set gnome system-settings from the command-line?
I'm specifically interested in a way to set:
settings -> energy -> screen off = never
settings -> energy -> screen off = (N) minue(s)
I would like to access this settings from a bash script, so I could set screen-off to
never
when the script starts and back to (N) minue(s)
before the script exits.
I hope my question is clear, since I just translated the menu hierarchy from a German-GUI.
I tried to find a setting with gsettings
but could not really get my way through.
nath
(6094 rep)
Dec 20, 2017, 11:59 PM
• Last activity: Dec 24, 2017, 05:30 AM
3
votes
2
answers
2660
views
Forcing the screen to go blank
I found [this answer][1] to make my screen go blank with `xset dpms force off`. But most of the times it only works for a brief moment and the screen comes back. I never managed to get this to work an second try or a second time if it worked the first time. Is there a trick to this that I missed? [1...
I found this answer to make my screen go blank with
xset dpms force off
.
But most of the times it only works for a brief moment and the screen comes back. I never managed to get this to work an second try or a second time if it worked the first time.
Is there a trick to this that I missed?
Lindsey
(31 rep)
Nov 22, 2016, 10:22 AM
• Last activity: Nov 22, 2016, 10:58 PM
0
votes
2
answers
2748
views
How can I reduce my Laptop's power consumption when running Linux?
I just installed Linux on a laptop of mine (it's Lubuntu 15.04 on a Lenovo X201, Core i5 M540, 2GB mem). I'm currently seeing 21580 mW power draw with a couple of apps open (Firefox with a few tabs and Ghostery, and LibreOffice Writer). I haven't tweaked the system in any way, and am using the stock...
I just installed Linux on a laptop of mine (it's Lubuntu 15.04 on a Lenovo X201, Core i5 M540, 2GB mem). I'm currently seeing 21580 mW power draw with a couple of apps open (Firefox with a few tabs and Ghostery, and LibreOffice Writer). I haven't tweaked the system in any way, and am using the stock kernel; this means ~3h or so of battery life with my model and my current battery.
What should I / can I do to reduce the power draw? I'd rather get generally-useful advice rather than something specific to the distro or apps I'm using just now (but distro-specific advice is also relevant).
Notes:
- I am willing to turn off some hardware functionality, as long as it's very easy for me to turn it back on when I need to.
einpoklum
(10753 rep)
Jun 18, 2015, 09:42 PM
• Last activity: Jun 19, 2015, 07:51 AM
4
votes
1
answers
4810
views
Disabling screen blanking in GNOME 3
We are using a Debian 7 machine with the default GNOME 3 installation to display content on an information display. This display needs to remain on until the connected computer is switched off. However, GNOME 3 switches the display off after a few minutes. I can't seem to find a way to control this...
We are using a Debian 7 machine with the default GNOME 3 installation to display content on an information display. This display needs to remain on until the connected computer is switched off. However, GNOME 3 switches the display off after a few minutes.
I can't seem to find a way to control this behaviour in either the system settings tools nor using dconf-editor. There is a prominent Google hit suggesting to change the
org.gnome.settings-daemon.plugins.power sleep-display-ac
org.gnome.settings-daemon.plugins.power sleep-display-battery
org.gnome.desktop.session idle-delay
keys, but this did not change anything.
So, how does one control and disable screen blanking in GNOME 3?
jstarek
(1742 rep)
Jun 8, 2014, 04:00 PM
• Last activity: Jun 22, 2014, 12:16 PM
1
votes
0
answers
535
views
"Screen Energy Saving" (in KDE) - how to trigger command when entering and exiting such mode?
I have two commands: * one I'd like to execute when computer enters "Screen Energy Saving" mode, * another when it exists this state. How to trigger those commands depending on "Screen Energy Saving" ? (I use KDE 4.13.0, and above is feature of KDE's "Power Management")
I have two commands:
* one I'd like to execute when computer enters "Screen Energy Saving" mode,
* another when it exists this state.
How to trigger those commands depending on "Screen Energy Saving" ?
(I use KDE 4.13.0, and above is feature of KDE's "Power Management")
Grzegorz Wierzowiecki
(14740 rep)
May 12, 2014, 09:55 PM
Showing page 1 of 13 total questions