Screen No Longer Powers Back On After Inactivity

I currently have my screen set to turn off after 5 minutes of inactivity. For the six months I’ve had my Framework 16 this has never been an issue, but starting yesterday I cannot get my screen to power back on after it goes inactive. To be clear, what I mean is that my session locks and the screen shuts off, not that my laptop is suspending itself. I can still see that the screen backlight is on. Pressing the volume keys on the keyboard to adjust my volume still makes sounds, so I don’t suspect that the whole laptop is frozen, only the screen doesn’t seem to want to work. I can press the power button to force the laptop to suspend/go into sleep mode, but when it wakes back up the screen remains black. So far the only fix is to press and hold the power button to force the laptop to power off. Then I can power it back on, log in, and use it normally. I have not had any external display devices connected to the laptop at the time these problems have occurred, nor is there anything near or around the laptop that should be causing any interference. I am currently running Fedora Linux 40 (Workstation Edition) with the latest updates as of today 9/24. I am also running BIOS v3.03 and have been for many months now.

1 Like

(This applies if you use dnf to update; I don’t think it would work if you use the software center method)

If this was caused by the recent updates you can try rolling back to a previous state:

dnf history list |head to get a list of the most recent updates, then

sudo dnf history rollback <a transaction ID from a day or two ago when things worked>

You’ll always be able to update again to current latest with sudo dnf up.

After each of the rollback and up steps, reboot to make sure the correct version of everything is being used in each case.

Edit: If you do find that a dnf transaction is the culprit, dnf history info <ID> will show the packages involved.

Hi dimitris, I appreciate the help. I ran the commands you specified, and this is the result I see when I try to run “sudo dnf history rollback xxx”:

Error: The following problems occurred while running a transaction:
Cannot find rpm nevra “ImageMagick-libs-1:7.1.1.33-1.fc40.x86_64”.
Cannot find rpm nevra “ImageMagick-1:7.1.1.33-1.fc40.x86_64”.
Cannot find rpm nevra “breeze-icon-theme-6.5.0-2.fc40.noarch”.
Cannot find rpm nevra “btrfs-progs-6.10.1-1.fc40.x86_64”.
Cannot find rpm nevra “deltarpm-3.6.4-1.fc40.x86_64”.
Cannot find rpm nevra “firefox-langpacks-130.0-3.fc40.x86_64”.
Cannot find rpm nevra “firefox-130.0-3.fc40.x86_64”.
Cannot find rpm nevra “gamescope-3.15.1-1.fc40.x86_64”.
Cannot find rpm nevra “gst-editing-services-1.24.7-1.fc40.x86_64”.
Cannot find rpm nevra “gstreamer1-plugin-libav-1.24.7-1.fc40.x86_64”.
Cannot find rpm nevra “gstreamer1-plugin-openh264-1.24.7-1.fc40.x86_64”.
Cannot find rpm nevra “gstreamer1-plugins-bad-free-extras-1.24.7-1.fc40.x86_64”.
Cannot find rpm nevra “gstreamer1-plugins-bad-free-fluidsynth-1.24.7-1.fc40.x86_64”.
Cannot find rpm nevra “gstreamer1-plugins-bad-free-libs-1.24.7-1.fc40.x86_64”.
Cannot find rpm nevra “gstreamer1-plugins-bad-free-opencv-1.24.7-1.fc40.x86_64”.
Cannot find rpm nevra “gstreamer1-plugins-bad-free-wildmidi-1.24.7-1.fc40.x86_64”.
Cannot find rpm nevra “gstreamer1-plugins-bad-free-zbar-1.24.7-1.fc40.x86_64”.
Cannot find rpm nevra “gstreamer1-plugins-bad-free-1.24.7-1.fc40.x86_64”.
Cannot find rpm nevra “gstreamer1-plugins-base-1.24.7-1.fc40.i686”.
Cannot find rpm nevra “gstreamer1-plugins-base-1.24.7-1.fc40.x86_64”.
Cannot find rpm nevra “gstreamer1-plugins-good-extras-1.24.7-1.fc40.x86_64”.
Cannot find rpm nevra “gstreamer1-plugins-good-gtk-1.24.7-1.fc40.x86_64”.
Cannot find rpm nevra “gstreamer1-plugins-good-qt-1.24.7-1.fc40.x86_64”.
Cannot find rpm nevra “gstreamer1-plugins-good-qt6-1.24.7-1.fc40.x86_64”.
Cannot find rpm nevra “gstreamer1-plugins-good-1.24.7-1.fc40.i686”.
Cannot find rpm nevra “gstreamer1-plugins-good-1.24.7-1.fc40.x86_64”.
Cannot find rpm nevra “gstreamer1-plugins-ugly-free-1.24.7-1.fc40.x86_64”.
Cannot find rpm nevra “gstreamer1-1.24.7-1.fc40.i686”.
Cannot find rpm nevra “gstreamer1-1.24.7-1.fc40.x86_64”.
Cannot find rpm nevra “ibus-typing-booster-2.25.15-1.fc40.noarch”.
Cannot find rpm nevra “kde-cli-tools-6.1.4-1.fc40.x86_64”.
Cannot find rpm nevra “kdesu-1:6.1.4-1.fc40.x86_64”.
Cannot find rpm nevra “kf6-breeze-icons-6.5.0-2.fc40.x86_64”.
Cannot find rpm nevra “kf6-filesystem-6.5.0-1.fc40.x86_64”.
Cannot find rpm nevra “kf6-karchive-6.5.0-1.fc40.x86_64”.
Cannot find rpm nevra “kf6-kauth-6.5.0-1.fc40.x86_64”.
Cannot find rpm nevra “kf6-kbookmarks-6.5.0-1.fc40.x86_64”.
Cannot find rpm nevra “kf6-kcmutils-6.5.0-1.fc40.x86_64”.
Cannot find rpm nevra “kf6-kcodecs-6.5.0-1.fc40.x86_64”.
Cannot find rpm nevra “kf6-kcolorscheme-6.5.0-1.fc40.x86_64”.
Cannot find rpm nevra “kf6-kcompletion-6.5.0-1.fc40.x86_64”.
Cannot find rpm nevra “kf6-kconfig-6.5.0-1.fc40.x86_64”.
Cannot find rpm nevra “kf6-kconfigwidgets-6.5.0-1.fc40.x86_64”.
Cannot find rpm nevra “kf6-kcontacts-6.5.0-1.fc40.x86_64”.
Cannot find rpm nevra “kf6-kcoreaddons-6.5.0-1.fc40.x86_64”.
Cannot find rpm nevra “kf6-kcrash-6.5.0-1.fc40.x86_64”.
Cannot find rpm nevra “kf6-kdbusaddons-6.5.0-1.fc40.x86_64”.
Cannot find rpm nevra “kf6-kdesu-6.5.0-1.fc40.x86_64”.
Cannot find rpm nevra “kf6-kdnssd-6.5.0-1.fc40.x86_64”.
Cannot find rpm nevra “kf6-kdoctools-6.5.0-1.fc40.x86_64”.
Cannot find rpm nevra “kf6-kglobalaccel-6.5.0-1.fc40.x86_64”.
Cannot find rpm nevra “kf6-kguiaddons-6.5.0-1.fc40.x86_64”.
Cannot find rpm nevra “kf6-ki18n-6.5.0-1.fc40.x86_64”.
Cannot find rpm nevra “kf6-kiconthemes-6.5.0-1.fc40.x86_64”.
Cannot find rpm nevra “kf6-kio-core-libs-6.5.0-1.fc40.x86_64”.
Cannot find rpm nevra “kf6-kio-core-6.5.0-1.fc40.x86_64”.
Cannot find rpm nevra “kf6-kio-doc-6.5.0-1.fc40.noarch”.
Cannot find rpm nevra “kf6-kio-file-widgets-6.5.0-1.fc40.x86_64”.
Cannot find rpm nevra “kf6-kio-gui-6.5.0-1.fc40.x86_64”.
Cannot find rpm nevra “kf6-kio-widgets-libs-6.5.0-1.fc40.x86_64”.
Cannot find rpm nevra “kf6-kio-widgets-6.5.0-1.fc40.x86_64”.
Cannot find rpm nevra “kf6-kirigami-6.5.0-1.fc40.x86_64”.
Cannot find rpm nevra “kf6-kitemviews-6.5.0-1.fc40.x86_64”.
Cannot find rpm nevra “kf6-kjobwidgets-6.5.0-1.fc40.x86_64”.
Cannot find rpm nevra “kf6-knotifications-6.5.0-1.fc40.x86_64”.
Cannot find rpm nevra “kf6-kpackage-6.5.0-1.fc40.x86_64”.
Cannot find rpm nevra “kf6-kparts-6.5.0-1.fc40.x86_64”.
Cannot find rpm nevra “kf6-kpeople-6.5.0-1.fc40.x86_64”.
Cannot find rpm nevra “kf6-kpty-6.5.0-1.fc40.x86_64”.
Cannot find rpm nevra “kf6-kservice-6.5.0-1.fc40.x86_64”.
Cannot find rpm nevra “kf6-kstatusnotifieritem-6.5.0-1.fc40.x86_64”.
Cannot find rpm nevra “kf6-ksvg-6.5.0-1.fc40.x86_64”.
Cannot find rpm nevra “kf6-ktextwidgets-6.5.0-1.fc40.x86_64”.
Cannot find rpm nevra “kf6-kwallet-libs-6.5.0-1.fc40.x86_64”.
Cannot find rpm nevra “kf6-kwallet-6.5.0-1.fc40.x86_64”.
Cannot find rpm nevra “kf6-kwidgetsaddons-6.5.0-1.fc40.x86_64”.
Cannot find rpm nevra “kf6-kwindowsystem-6.5.0-1.fc40.x86_64”.
Cannot find rpm nevra “kf6-kxmlgui-6.5.0-1.fc40.x86_64”.
Cannot find rpm nevra “kf6-modemmanager-qt-6.5.0-1.fc40.x86_64”.
Cannot find rpm nevra “kf6-solid-6.5.0-1.fc40.x86_64”.
Cannot find rpm nevra “kf6-sonnet-hunspell-6.5.0-1.fc40.x86_64”.
Cannot find rpm nevra “kf6-sonnet-6.5.0-1.fc40.x86_64”.
Cannot find rpm nevra “kf6-syntax-highlighting-6.5.0-1.fc40.x86_64”.
Cannot find rpm nevra “kio-extras-24.08.0-1.fc40.x86_64”.
Cannot find rpm nevra “libkworkspace6-6.1.4-2.fc40.x86_64”.
Cannot find rpm nevra “libnetapi-2:4.20.4-1.fc40.x86_64”.
Cannot find rpm nevra “libplasma-6.1.4-1.fc40.x86_64”.
Cannot find rpm nevra “libsmbclient-2:4.20.4-1.fc40.x86_64”.
Cannot find rpm nevra “libwbclient-2:4.20.4-1.fc40.x86_64”.
Cannot find rpm nevra “m17n-db-1.8.7-1.fc40.noarch”.
Cannot find rpm nevra “nspr-4.35.0-28.fc40.i686”.
Cannot find rpm nevra “nspr-4.35.0-28.fc40.x86_64”.
Cannot find rpm nevra “nss-softokn-freebl-3.103.0-1.fc40.i686”.
Cannot find rpm nevra “nss-softokn-freebl-3.103.0-1.fc40.x86_64”.
Cannot find rpm nevra “nss-softokn-3.103.0-1.fc40.i686”.
Cannot find rpm nevra “nss-softokn-3.103.0-1.fc40.x86_64”.
Cannot find rpm nevra “nss-sysinit-3.103.0-1.fc40.x86_64”.
Cannot find rpm nevra “nss-util-3.103.0-1.fc40.i686”.
Cannot find rpm nevra “nss-util-3.103.0-1.fc40.x86_64”.
Cannot find rpm nevra “nss-3.103.0-1.fc40.i686”.
Cannot find rpm nevra “nss-3.103.0-1.fc40.x86_64”.
Cannot find rpm nevra “pipewire-alsa-1.0.7-2.fc40.i686”.
Cannot find rpm nevra “pipewire-alsa-1.0.7-2.fc40.x86_64”.
Cannot find rpm nevra “pipewire-gstreamer-1.0.7-2.fc40.x86_64”.
Cannot find rpm nevra “pipewire-libs-1.0.7-2.fc40.i686”.
Cannot find rpm nevra “pipewire-libs-1.0.7-2.fc40.x86_64”.
Cannot find rpm nevra “pipewire-pulseaudio-1.0.7-2.fc40.x86_64”.
Cannot find rpm nevra “pipewire-utils-1.0.7-2.fc40.x86_64”.
Cannot find rpm nevra “pipewire-1.0.7-2.fc40.i686”.
Cannot find rpm nevra “pipewire-1.0.7-2.fc40.x86_64”.
Cannot find rpm nevra “plasma-activities-stats-6.1.4-1.fc40.x86_64”.
Cannot find rpm nevra “plasma-activities-6.1.4-1.fc40.x86_64”.
Cannot find rpm nevra “plasma-workspace-common-6.1.4-2.fc40.x86_64”.
Cannot find rpm nevra “plymouth-core-libs-24.004.60-12.fc40.x86_64”.
Cannot find rpm nevra “plymouth-graphics-libs-24.004.60-12.fc40.x86_64”.
Cannot find rpm nevra “plymouth-plugin-label-24.004.60-12.fc40.x86_64”.
Cannot find rpm nevra “plymouth-plugin-two-step-24.004.60-12.fc40.x86_64”.
Cannot find rpm nevra “plymouth-scripts-24.004.60-12.fc40.x86_64”.
Cannot find rpm nevra “plymouth-system-theme-24.004.60-12.fc40.x86_64”.
Cannot find rpm nevra “plymouth-theme-spinner-24.004.60-12.fc40.x86_64”.
Cannot find rpm nevra “plymouth-24.004.60-12.fc40.x86_64”.
Cannot find rpm nevra “samba-client-libs-2:4.20.4-1.fc40.x86_64”.
Cannot find rpm nevra “samba-client-2:4.20.4-1.fc40.x86_64”.
Cannot find rpm nevra “samba-common-libs-2:4.20.4-1.fc40.x86_64”.
Cannot find rpm nevra “samba-common-tools-2:4.20.4-1.fc40.x86_64”.
Cannot find rpm nevra “samba-common-2:4.20.4-1.fc40.noarch”.
Cannot find rpm nevra “samba-dcerpc-2:4.20.4-1.fc40.x86_64”.
Cannot find rpm nevra “samba-ldb-ldap-modules-2:4.20.4-1.fc40.x86_64”.
Cannot find rpm nevra “samba-libs-2:4.20.4-1.fc40.x86_64”.
Cannot find rpm nevra “samba-winbind-clients-2:4.20.4-1.fc40.x86_64”.
Cannot find rpm nevra “samba-winbind-modules-2:4.20.4-1.fc40.x86_64”.
Cannot find rpm nevra “samba-winbind-2:4.20.4-1.fc40.x86_64”.
Cannot find rpm nevra “virtualbox-guest-additions-7.0.20-1.fc40.x86_64”.

I’m not sure this helps with the issue, but the only similarity I found in the above files is that they all contain “fc40” toward the end.

fc40 is just part of the version string for Fedora 40 packages (fc I think for historical reasons back when it was “Fedora Core”).

The “missing” packages are probably because these older versions have aged out of the regular release repo mirrors. Try installing the updates-archive repository:

sudo dnf install fedora-repos-archive

Then try the rollback command again.

Thanks again dimitris. That command helped, but I still have a handful of files that are giving me the same error as before:

Error: The following problems occurred while running a transaction:
Cannot find rpm nevra “gstreamer1-plugins-base-1.24.7-1.fc40.i686”.
Cannot find rpm nevra “gstreamer1-plugins-good-1.24.7-1.fc40.i686”.
Cannot find rpm nevra “gstreamer1-1.24.7-1.fc40.i686”.
Cannot find rpm nevra “nspr-4.35.0-28.fc40.i686”.
Cannot find rpm nevra “nss-softokn-freebl-3.103.0-1.fc40.i686”.
Cannot find rpm nevra “nss-softokn-3.103.0-1.fc40.i686”.
Cannot find rpm nevra “nss-util-3.103.0-1.fc40.i686”.
Cannot find rpm nevra “nss-3.103.0-1.fc40.i686”.
Cannot find rpm nevra “pipewire-alsa-1.0.7-2.fc40.i686”.
Cannot find rpm nevra “pipewire-libs-1.0.7-2.fc40.i686”.
Cannot find rpm nevra “pipewire-1.0.7-2.fc40.i686”.

I suspect that those versions it still can’t “find” are the initial versions from the install image. The fedora-updates-archive repository may not actually contain those because they never went through the full online repository distribution path:

$ dnf info fedora-repos-archive
Last metadata expiration check: 2:15:07 ago on Tue 24 Sep 2024 10:28:28 AM PDT.
Installed Packages
Name         : fedora-repos-archive
Version      : 40
Release      : 2
Architecture : noarch
Size         : 986  
Source       : fedora-repos-40-2.src.rpm
Repository   : @System
From repo    : updates
Summary      : Fedora updates archive package repository
URL          : https://fedoraproject.org/
License      : MIT
Description  : This package provides the repo definition for the updates archive repo.
             : It is a package repository that contains any RPM that has made it to
             : stable in Bodhi and been available in the Fedora updates repo in the past.

I assume you got F40 on this machine with a new install, not an upgrade from F39, right?

There’s probably a way to include the “initial install image packages” for consideration in a dnf transaction somehow, but not sure how atm…

Edit: Now I’m not sure about this theory, e.g. pipewire-1.0.7-2 was in fact part of the update stream here.

More edit: And downgrading to that version seems possible here:

$ sudo dnf --enablerepo updates-archive downgrade pipewire-1.0.7-2.fc40
Place your right index finger on the fingerprint reader
Last metadata expiration check: 0:00:44 ago on Tue 24 Sep 2024 12:57:28 PM PDT.
Dependencies resolved.
===========================================================================================================
 Package                        Architecture      Version                 Repository                  Size
===========================================================================================================
Downgrading:
 pipewire                       x86_64            1.0.7-2.fc40            updates-archive            123 k
 pipewire-alsa                  x86_64            1.0.7-2.fc40            updates-archive             57 k
 pipewire-gstreamer             x86_64            1.0.7-2.fc40            updates-archive             65 k
 pipewire-libs                  x86_64            1.0.7-2.fc40            updates-archive            1.8 M
 pipewire-pulseaudio            x86_64            1.0.7-2.fc40            updates-archive            198 k
 pipewire-utils                 x86_64            1.0.7-2.fc40            updates-archive            335 k

Transaction Summary
===========================================================================================================
Downgrade  6 Packages

Total download size: 2.6 M
Is this ok [y/N]: 
Operation aborted.

Maybe, to reset this troubleshooting, try this: First sudo dnf --refresh up to get back to very latest. Then, since from the list of packages you seem to be using KDE (I use GNOME and can’t reproduce the problem), sudo dnf downgrade just the KDE-specific packages in that list. Basically anything starting with k :slight_smile: to be safe. Make sure to use the versions from the long list you posted, up to and including the fc40.

Then reboot and see if things change/improve.

dimitris, did you mean sudo dnf update --refresh up to get back to very latest? If so, I ran that command and all seemed to go okay. Also I am running Fedora Workstation (uses Gnome and not KDE). I’m not sure why I have so many KDE packages installed. I originally installed Fedora 39 before upgrading to 40 back in April I believe.

OK, that’s good you’re back in a good state (modulo this screen issue).

Let’s set this aside for now, might be dependencies from some application you installed.

Instead of chasing package update history, if this screen issue still reproduces, try this to get some logs: Trigger the issue, then look at the system journal to see if anything interesting is reported (like processes crashing) during that time. For example if you did the leave system idle - screen blanks - try to wake up - no response cycle starting 10 minutes ago, then:

  • wait a few seconds

  • journalctl --since '12 minutes ago'

    or, if you had to force a reboot:

  • after the reboot, journalctl -b -1 to get all of the previous boot’s logs and see what’s interesting towards the end of the log.

should cover the relevant time span.

BTW before forcing a reboot, try first to switch to a text console and log in from there to get the log: Ctrl - Alt - F3 (or F4)

Although unless the kernel has crashed, the journal should still be intact after a reboot too.

1 Like

Thank you again for your help. So CTRL + Alt + F3 and then switching back to F2 seems to revive my screen so at least I now have that as a workaround for when this occurs. Immediately after the last black screen I ran journalctl --since '12 minutes ago' but I’m not sure I know what to look for, but here are some errors that I saw:

Oct 01 19:16:25 titan systemd[1]: Starting fprintd.service - Fingerprint Authentication Daemon...
Oct 01 19:16:25 titan gsd-power[3230]: Release of light sensors failed: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Not Authorized: Sensor claim not allowed
Oct 01 19:16:27 titan gdm[1921]: GLib: Source ID 123 was not found when attempting to remove it
Oct 01 19:16:27 titan wireplumber[2935]: spa.bluez5.midi: org.bluez.GattManager1.RegisterApplication() failed: GDBus.Error:org.bluez.Error.AlreadyExists: Already Exists
Oct 01 19:16:27 titan gsd-media-keys[3226]: Unable to get default sink
Oct 01 19:16:27 titan gsd-media-keys[3226]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed
Oct 01 19:16:27 titan gsd-media-keys[3226]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed
Oct 01 19:16:27 titan gsd-media-keys[3226]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed
Oct 01 19:16:27 titan gsd-media-keys[3226]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed
Oct 01 19:16:27 titan gsd-media-keys[3226]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed
Oct 01 19:16:27 titan gsd-media-keys[3226]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed
Oct 01 19:16:27 titan gsd-media-keys[3226]: Unable to get default sink
Oct 01 19:16:27 titan gsd-media-keys[3226]: Unable to get default source
Oct 01 19:16:27 titan gsd-media-keys[3226]: gvc_mixer_ui_device_get_id: assertion 'GVC_IS_MIXER_UI_DEVICE (device)' failed
Oct 01 19:16:27 titan gsd-media-keys[3226]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed
Oct 01 19:16:27 titan gsd-media-keys[3226]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed
Oct 01 19:16:27 titan gsd-media-keys[3226]: Sync_devices: Failed to match stream id: 63, description: 'Digital Output (S/PDIF)', origin: 'Hi-Res Audio Digita>
Oct 01 19:16:27 titan gsd-media-keys[3226]: Unable to get default sink
Oct 01 19:16:27 titan gsd-media-keys[3226]: gvc_mixer_ui_device_get_id: assertion 'GVC_IS_MIXER_UI_DEVICE (device)' failed
Oct 01 19:16:34 titan gnome-shell[2998]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed

I don’t see anything immediately suspicious here, that last line with the gnome-shell error about meta_window_set_stack_position_no_sync is one I also see in my logs without having this problem.

Can you upload the full log here? You might have to do it as an upload, not an inline text, due to size.

One other thing I just remembered, look for entries of program crashes in the Problem Reporting (aka abrt) application. Maybe clear any existing problems there, force the issue again, and see if it reports anything new after getting back into the session.

This is a little surprising to me. What are the settings for:

Settings → Power → Screen Blank
Settings → Power → Automatic Suspend
Settings → Privacy & Security → (Blank Screen Delay, Automatic Screen Lock, Automatic Screen Lock Delay)

Settings → Power → Screen Blank
5 minutes
Settings → Power → Automatic Suspend
When on battery power
Delay: 15 Minutes
Plugged In: N/A
Settings → Privacy & Security → (Blank Screen Delay, Automatic Screen Lock, Automatic Screen Lock Delay)
Blank Screen Delay: 5 minutes
Automatic Screen Lock: enabled
Automatic Screen Lock Delay: Screen Turns Off
Lock Screen Notifications: enabled

As for uploading the full journalctl file from yesterday, it looks like the only authorized file formats for upload here are either image file formats or CAD file formats. I can just post it here unless there is another site you’d want me to upload it to?

The settings look essentially identical to mine - I use 15 instead of 5 minutes and no automatic suspend.

BTW I somehow had managed to miss that you’re on a FW16 whereas mine is a FW13 AMD.

Anyway: For the logs, maybe try an upload service like pastebin and post the URL here? There might be some quasi-private information in there (wireless LAN names, Bluetooth/WLAN MAC addresses, that type of thing) so you might want to edit those out before posting.

I am seeing this intermittently on a FW16. Will try flipping from power-options service back to ppd and see if I have a recurrence. I have not figured out how to trigger it, so will just have to wait for it to happen, or not happen.

Edit to add - arch, gnome, dGPU installed.

1 Like

Dimitris, here is a pastebin containing logs for the last time this error occurred earlier today.

Also small update, when my screen went black earlier I was NOT able to press CTRL + ALT + F3 to revive it like last time. I had to press and hold the power button to forcefully shut my laptop down to get things working again.

All this:

Oct 03 11:45:38 titan kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data

suggests something is indeed going on in the graphics stack. If you search for DMCUB there are some other threads that also reference this in graphics-related problems (not exactly the same error message based on my quick search).

I’d suggest a bug report in the upstream graphics driver repository/bugtracker. Also quick cc to @Mario_Limonciello from AMD here in case there’s something else to try/suggest.

Whaddayaknow, just happened to me. Upstream issue here.

As unfortunate as it is that you encountered this issue, I have to admit I’m glad it’s not just me. Have you had any more black screens since the first one? Searching for that error online has also returned results from others going back to early July of this year.

I want to say I’ve had similar “black screen on wakeup” events, but I haven’t kept any notes/into.

I also don’t usually walk away from an unlocked screen so I may be giving this too few chances to occur.

How reliably do you reproduce this?

So far, not reliably at all. There are times when it seems to do this immediately once the screen goes dark and locks due to inactivity, other times (like now) it won’t give me any issues for days on end.