Description of problem: After I've upgraded from Fedora 28-Xfce to Fedora 29-Xfce I'm not able to wake up screen after it goes blank anymore and I must reboot by pressing the power button. I've never had this kind of issue before. If it could help: I'm using integrated GPU Intel Graphics HD 4000. How reproducible: Wait for the screen to go blank and try waking up by pressing any key or moving the trackpad/mouse.
Anything in system logs? Nothing changed in xfpm specifically (although we build against newer libraries for F29).
I ran the "journalctl" command (hoping it's what you mean with system logs; sorry, I'm quite new to Linux) and I didn't get any log related to this issue, the next log line is "-- Reboot --" (which I had to force with the power button).
When this happens can you try turning off and back on the monitor? It seems like this might be a graphics bug somehow.
I can't get back to the monitor in any way but I found out that just the screen isn't working: I tried, after the screen had gone blank, to open the terminal with keyboard shortcut (screen was still black, I couldn't see anything) and typing "reboot" and it rebooted.
Are you using xscreensaver? (ie, rpm -q xscreensaver-common would show you if it's installed). What kind of graphics card do you have? (lspci should show it)
xscreensaver is not installed. My graphics card is an Intel HD Graphics 4000 (https://ark.intel.com/products/72164/Intel-Core-i5-3230M-Processor-3M-Cache-up-to-3-20-GHz-rPGA). lspci output: 00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) 00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04) 00:16.0 Communication controller: Intel Corporation 7 Series/C216 Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #2 (rev 04) 00:1b.0 Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 7 Series/C216 Chipset Family PCI Express Root Port 1 (rev c4) 00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4) 00:1d.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation HM77 Express Chipset LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04) 00:1f.3 SMBus: Intel Corporation 7 Series/C216 Chipset Family SMBus Controller (rev 04) 02:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetLink BCM57785 Gigabit Ethernet PCIe (rev 10) 02:00.1 SD Host controller: Broadcom Inc. and subsidiaries BCM57765/57785 SDXC/MMC Card Reader (rev 10) 02:00.2 System peripheral: Broadcom Inc. and subsidiaries BCM57765/57785 MS Card Reader (rev 10) 02:00.3 System peripheral: Broadcom Inc. and subsidiaries BCM57765/57785 xD-Picture Card Reader (rev 10) 03:00.0 Network controller: Qualcomm Atheros AR9462 Wireless Network Adapter (rev 01)
The same here, intel i7 and i5 graphics. Ctrl-Alt_F2 and back Alt-F1 wakes up the screen, no reboot needed. This is extremely annoying bug.
Same here on Lenovo ThinkPad X230: 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) xscreensaver is installed. Ctrl-Alt-F2, etc., does work for me, too.
Moving over to kernel/graphics folks for comment...
Issue solved for me: "xset s 0" from command line or add flag to xorg.conf to make it permanent Section ServerFlags Option "BlankTime" "0" EndSection e.g. in /etc/X11/xorg.conf.d/10-user.conf "Standby/Suspend/Off" via VESA DPMS is working fine; no need for screensaver's BlankTime.
Thank you, Radek. That seems to solve the problem for me, too. Just to note that the xorg.conf section name must be quoted: Section "ServerFlags" Option "BlankTime" "0" EndSection
It turns out that setting the BlankTime option does not solve the problem for me. The problem has reoccurred twice since I have started setting it. I verified in the server log that the option is being set: [ 8.112] (**) Option "BlankTime" "0" Could there be another cause of the failure to wake up after the screen goes blank?
We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 29 kernel bugs. Fedora 29 has now been rebased to 4.19.5-300.fc29. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those.
Still experiencing this bug with latest kernel (4.19.5-300.fc29). Still able to get back to the desktop with Ctrl+Alt+F2 and then Ctrl+Alt+F1.
Also still experiencing this with 4.19.5-300.fc29.
(In reply to David Levine from comment #15) > Also still experiencing this with 4.19.5-300.fc29. Can you try adding "fbcon=nodefer" to your kernel commandline and see if that helps ?
fbcon=nodefer does not help with 4.19.5-300 kernel.
(In reply to David Levine from comment #17) > fbcon=nodefer does not help with 4.19.5-300 kernel. Ok, thank you for trying. I was afraid my flickerfree boot work might be the cause of this, but if fbcon=nodefer does not help then that is not the case.
Same problem here: Fedora 29, Xfce, Xorg, Intel Graphics HD, laptop Sometimes (not always): Ctrl-Alt-F2 and Ctrl-Alt-F1 wakes up the screen In this system if you try (with or without xscreensaver): sleep 2; xset dpms force off The screen goes off normally. And the wake up turns on only the backlight (laptop) and the mouse pointer. There is no image. If you know the screen positions, you can type and do mouse clicks. And, again, not always: Ctrl-Alt-F2 and Ctrl-Alt-F1 wakes up the screen. I think this bug is more related with Xorg drivers (Intel, dpms).
Hi, I experience similar issues. Getting these strange errors in journalctl. Switching consoles by Ctrl-Alt-F<X> helps. ``` Mar 22 12:59:47 windmill.users.ipa.redhat.com gsd-color[2744]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/xrandr_LG_Display_gdm_42 Mar 22 13:00:25 windmill.users.ipa.redhat.com google-chrome.desktop[2511]: [4837:4837:0322/130025.067557:ERROR:display_info_provider.cc(195)] Not implemented reached in virtual void extensions::DisplayInfoProvider::UpdateDisplayUnitInfoForPlatform(const display::Display &, extensions::api::system_display::DisplayUnitInfo *) Mar 22 14:32:16 windmill.users.ipa.redhat.com google-chrome.desktop[2511]: [10309:10309:0322/143216.819103:ERROR:display_info_provider.cc(195)] Not implemented reached in virtual void extensions::DisplayInfoProvider::UpdateDisplayUnitInfoForPlatform(const display::Display &, extensions::api::system_display::DisplayUnitInfo *) Mar 25 10:01:50 windmill.users.ipa.redhat.com gnome-shell[2511]: meta_display_get_monitor_geometry: assertion 'monitor >= 0 && monitor < n_logical_monitors' failed Mar 25 10:02:11 windmill.users.ipa.redhat.com gsd-color[2744]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/xrandr_LG_Display_gdm_42 Mar 25 10:02:44 windmill.users.ipa.redhat.com gsd-power[2704]: Error setting property 'PowerSaveMode' on interface org.gnome.Mutter.DisplayConfig: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.Mutter.DisplayConfig was not provided by any .service files (g-dbus-error-quark, 2) Mar 25 10:03:14 windmill.users.ipa.redhat.com gsd-color[2744]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/xrandr_LG_Display_gdm_42 Mar 25 10:36:36 windmill.users.ipa.redhat.com gsd-color[2744]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/xrandr_LG_Display_gdm_42 Mar 25 11:37:44 windmill.users.ipa.redhat.com google-chrome.desktop[15613]: [23916:23916:0325/113744.206468:ERROR:display_info_provider.cc(195)] Not implemented reached in virtual void extensions::DisplayInfoProvider::UpdateDisplayUnitInfoForPlatform(const display::Display &, extensions::api::system_display::DisplayUnitInfo *) Mar 25 12:52:17 windmill.users.ipa.redhat.com gsd-color[2744]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/xrandr_LG_Display_gdm_42 Mar 25 13:02:36 windmill.users.ipa.redhat.com gsd-color[2744]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/xrandr_LG_Display_gdm_42 Mar 25 13:08:05 windmill.users.ipa.redhat.com gsd-color[2744]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/xrandr_LG_Display_gdm_42 ``` ``` ~ > uname -r 5.0.3-200.fc29.x86_64 ~ > cat /etc/fedora-release Fedora release 29 (Twenty Nine) ```
This bug exists also on F30 (tested with my laptop, HP 840 with Intel HD graphics).
Same issue on Dell Precision 5520.
How I resolved my problem: For Intel graphics there is two drives for Xorg: "modesetting" and "intel" A Fedora fresh installation uses the default "modesetting", while a upgrade keeps the old configuration files at "/etc/X11/xorg.conf.d". In my case I had a "intel" drive configured with option "uxa" that is causing the problem (installed by very old Fedora - date 2013 - and working without problems thru multiple updates until fedora 28). There is two solutions: 1) Using the "intel" driver: ---------------------------- Just commenting the "uxa" option. file /etc/X11/xorg.conf.d/20-intel.conf Section "Device" Driver "intel" Identifier "Card0" BusID "PCI:0:2:0" #Option "AccelMethod" "uxa" EndSection 2) Using the default Xorg "modesetting". ---------------------------------------- Just removing the file 20-intel.conf It works, but the ~/.local/share/xorg/Xorg.0.log shows the error: (EE) modeset(0): Failed to get GBM bo for flip to new front. (EE) modeset(0): present flip failed This log file continuously grow, if you use Xorg for 2 days the file can be greater than 5 GB. see: https://bugs.freedesktop.org/show_bug.cgi?id=106908 and: https://gitlab.freedesktop.org/xorg/xserver/issues/68 or: https://bugzilla.redhat.com/show_bug.cgi?id=1645553 For now, while the driver is not corrected, I am using: /etc/X11/xorg.conf.d/20-intel.conf Section "Device" Identifier "Intel" Driver "modesetting" Option "PageFlip" "off" EndSection
Ah ha! Great detective work tracking that down... Can the other folks seeing this check if that is also the cause of their woes?
I'm using the modesetting driver as selected by a fresh f30 xfce spin installation. The issue remained with that installation. I then added /etc/X11/xorg.conf.d/20-intel.conf with contents specified by Jose in comment 23 and verified in the Xorg log that it is read: [ 11.672] (**) modeset(0): Option "PageFlip" "off" However, it did not resolve the issue: I still have to switch consoles to wake up the screen after it goes blank.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 30 kernel bugs. Fedora 30 has now been rebased to 5.2.9-200.fc30. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 31, and are still experiencing this issue, please change the version to Fedora 31. If you experience different issues, please open a new bug report for those.
Issue still present with 5.2.8-200.fc30. (I assume 5.2.9 was a typo.)
Here to report I am experiencing this on Fedora30 as well. For what it's worth, I noticed the problem persists whether the monitor is plugged into my display port on my motherboard (Intel HD Graphics 530) or plugged into my GPU (NVidia GeForce GTX 1080 Ti). Only known solution has been to perform a hard reset on the box. Will try the Ctrl-Alt-F2 and Ctrl-Alt-F1 suggestions to see if this helps.
I am currently getting this on Fedora 31 with Gnome 3.34.0 as well.
Same here, with i5-7200U with embedded GPU, KDE Plasma. Only workaround is to disable screen going to sleep at all.
The issue seems to be resolved for me with Fedora 31. Kernel version is 5.3.7-301.fc31.x86_64.
I'm seeing this problem, too. Every once and a while, my computer won't wake up from sleep. I press a key to wake it up to get to the lock screen, and nothing happens. I have to reset my computer, or Power Off/Power On. Fedora 31 Intel i7 Haswell Linux Kernel 5.3.16-300.fc31.x86_64 AMD Radeon RX 590 Sapphire Nitro Edition 8 GB 32 GB RAM GNOME/Wayland
Note: Killing gdm-wayland-session reestablishes a video signal to each of my monitors, but then I lose my session and have to login again. At least, this rules out a kernel issue, since I'm able to login to my box from another computer.
Is there anything special that I should capture when the problem occurs again, because it will? As long as I can login, I can do some things. I just built a new system, too, with an AMD Ryzen 9 3950x and AMD Radeon RX 5700xt. I'll see whether the problem occurs on this system as well.
I also just purchased a new system with an AMD Ryzen 9 3950x and a Gigabyte RX 5700 XT and am also experiencing this issue. Kernel 5.4.15-200.fc31.x86_64 Gigabyte Radeon™ RX 5700 XT GAMING OC 8G Asrock X570 Taichi motherboard While I'm waiting for a new monitor I'm using an old Dell monitor and a DVI to HDMI adapter. My new monitor is expected this week and I'll be using DisplayPort then. I'll update my experience after I have some experience with it.
So far, I haven't never seen the problem on my new system -- AMD Ryzen 9 3950x with AMD Radeon RX 5700xt 8 GB and a single IPS Display Port 4K LG Monitor. Kernel: 5.4.14-200.fc31.x86_64 I haven't seen the problem on my older system recently -- Intel i4770k Haswell with AMD Radeon RX 590 8 GB and dual IPS Display Port 4K LG Monitors -- but about a week or two has to pass before the problem manifests itself. Kernel: 5.4.15-200.fc31.x86_64
Initially I worked around the problem with the old Dell monitor by disabling screen power saving and letting the monitor remain active. That worked but is obviously not the best choice. I received my new Dell S3220DGF with Freesync 2 HDR and have re-enabled screen power saving and have not see the issue after several days. Hope this helps.
Now it's working, I haven't seen the problem for a week. I'm not sure the exact moment in which it came back to normal, anyway, Kernel 5.5.5-200.fc31.x86_64
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 30 kernel bugs. Fedora 30 has now been rebased to 5.5.7-100.fc30. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 31, and are still experiencing this issue, please change the version to Fedora 31. If you experience different issues, please open a new bug report for those.
Resuming from suspend leaves the screen black half of the time ; switching the monitor off, then on, brings it back to life. My system : Linux 5.5.5-200.fc31.x86_64 #1 SMP Wed Feb 19 23:28:07 UTC 2020 x86_64 x86_64 x86_64 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV620 LE [Radeon HD 3450] xorg-x11-drv-ati-19.0.1-3.fc31.x86_64 xscreensaver-base-5.43-5.fc31.x86_64
For me, this issue resulted in being an AMD driver issue that caused a kernel crash. After a few kernel updates, I haven't seen the problem again.
I've seen the problem again on my AMD RX 590 system with Dual 4K IPS monitors, Fedora 31, but I forgot to try powering off and powering on the monitors. That works sometimes. I've seen the problem once on my AMD RX 5700XT system with a single IPS 4K monitor. Also running Fedora 31.
This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '30'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 30 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.