Screen goes blank after 30s after Fedora 41 upgrade

Hi everyone,
after an upgrade from Fedora 40 Workstation to Fedora 41 Workstation, the screen goes blank after 30 seconds of inactivity.
On GNOME power settings the screen timeout is setted to 5 minutes.
I temporarily fixed this using the “caffeine” extension.

Bye

You’re not the only one.

Could you let the screen go blank and then run journalctl --no-pager --no-host --since=-1m, and post the output.

Sure, here’s the output:

➜   LC_ALL=C journalctl --no-pager --no-host --since=-1m
Nov 27 11:44:08 tailscaled[1739]: portmapper: failed to get PCP mapping: PCP is implemented but not enabled in the router
Nov 27 11:44:09 tailscaled[1739]: portmapper: failed to get PCP mapping: PCP is implemented but not enabled in the router
Nov 27 11:44:34 tailscaled[1739]: portmapper: failed to get PCP mapping: PCP is implemented but not enabled in the router
Nov 27 11:44:34 tailscaled[1739]: portmapper: failed to get PCP mapping: PCP is implemented but not enabled in the router
Nov 27 11:44:54 tailscaled[1739]: portmapper: failed to get PCP mapping: PCP is implemented but not enabled in the router
Nov 27 11:44:54 tailscaled[1739]: portmapper: failed to get PCP mapping: PCP is implemented but not enabled in the router
Nov 27 11:44:58 rtkit-daemon[1153]: Successfully made thread 3077 of process 3046 (/usr/bin/gnome-shell) owned by '1000' high priority at nice level 0.
Nov 27 11:44:58 rtkit-daemon[1153]: Successfully made thread 3077 of process 3046 (/usr/bin/gnome-shell) owned by '1000' RT at priority 20.
Nov 27 11:45:01 rtkit-daemon[1153]: Successfully made thread 3077 of process 3046 (/usr/bin/gnome-shell) owned by '1000' high priority at nice level 0.
Nov 27 11:45:01 rtkit-daemon[1153]: Successfully made thread 3077 of process 3046 (/usr/bin/gnome-shell) owned by '1000' RT at priority 20.

Are you on Wayland?

What does gsettings list-recursively org.gnome.settings-daemon.plugins.power say?

Yes, I’m on Wayland.

➜   gsettings list-recursively org.gnome.settings-daemon.plugins.power
org.gnome.settings-daemon.plugins.power ambient-enabled true
org.gnome.settings-daemon.plugins.power idle-brightness 30
org.gnome.settings-daemon.plugins.power idle-dim true
org.gnome.settings-daemon.plugins.power power-button-action 'suspend'
org.gnome.settings-daemon.plugins.power power-saver-profile-on-low-battery true
org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 3600
org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type 'nothing'
org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout 900
org.gnome.settings-daemon.plugins.power sleep-inactive-battery-type 'suspend'

I had this after upgrading to Fedora Workstation 41, but it only manifested if I had suspended and resumed my session at least once after booting.

Then I installed Silverblue 41, which as far as I know solved the issue. It recently came back. Like @gnomelover, I too am using the Caffeine extension. Not sure if that could somehow be related.

Same here, I’m aggressively installing twice per day as it’s very annoying to work on. Really hope in some good suggestions!

my output journalctl --no-pager --no-host --since=-1m is:

Jan 17 10:10:36 google-chrome-unstable.desktop[4415]: [01/17/25, 10:10:36:602] info: [CHANNEL-STATUS] (E030G10V24F) Created channel C088XE1UAG6
Jan 17 10:10:36 google-chrome-unstable.desktop[4415]: [01/17/25, 10:10:36:606] info: [RTM] (E030G10V24F) Processed 1 channel_created event(s) in channel(s) [object Object] over 46.20ms
Jan 17 10:10:37 google-chrome-unstable.desktop[4415]: [01/17/25, 10:10:37:380] info: [RTM] Setting a timeout of 99 ms to process more rtm events
Jan 17 10:10:37 google-chrome-unstable.desktop[4415]: [01/17/25, 10:10:37:479] info: [RTM] Waited 99 ms, processing more rtm events now
Jan 17 10:11:17 google-chrome-unstable.desktop[4415]: [01/17/25, 10:11:17:099] info: Store: SET_SYSTEM_IDLE idle
Jan 17 10:11:17 google-chrome-unstable.desktop[4415]: [01/17/25, 10:11:17:109] info: [DESKTOP-SIDE-EFFECT] Update from desktop for keys  ["app"]
Jan 17 10:11:21 gsd-media-keys[3484]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed
Jan 17 10:11:21 gsd-media-keys[3484]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed
Jan 17 10:11:21 gsd-media-keys[3484]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed
Jan 17 10:11:21 gsd-media-keys[3484]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed
Jan 17 10:11:21 gsd-media-keys[3484]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed
Jan 17 10:11:21 gsd-media-keys[3484]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed
Jan 17 10:11:21 gsd-media-keys[3484]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed
Jan 17 10:11:21 gsd-media-keys[3484]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed
Jan 17 10:11:21 gsd-media-keys[3484]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed
Jan 17 10:11:27 google-chrome-unstable.desktop[4415]: [01/17/25, 10:11:27:104] info: Store: SET_SYSTEM_IDLE active
Jan 17 10:11:27 google-chrome-unstable.desktop[4415]: [01/17/25, 10:11:27:111] info: [DESKTOP-SIDE-EFFECT] Update from desktop for keys  ["app"]

And from gsettings:

org.gnome.settings-daemon.plugins.power ambient-enabled true
org.gnome.settings-daemon.plugins.power idle-brightness 30
org.gnome.settings-daemon.plugins.power idle-dim true
org.gnome.settings-daemon.plugins.power power-button-action 'suspend'
org.gnome.settings-daemon.plugins.power power-saver-profile-on-low-battery true
org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 3600
org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type 'nothing'
org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout 900
org.gnome.settings-daemon.plugins.power sleep-inactive-battery-type 'suspend'

For context, this system is running with the nvidia driver. I also run Fedora on the laptop - which is intel based - and had no issues there.

Any help highly appreciated!

1 Like