Bug 1718961 - Corrupted background and lockscreen after resume from suspend
Summary: Corrupted background and lockscreen after resume from suspend
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 30
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1742820
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-10 15:56 UTC by afox@redhat.com
Modified: 2022-05-12 17:06 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-05-26 16:37:10 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
First example of corruption (659.43 KB, image/png)
2019-06-10 15:56 UTC, afox@redhat.com
no flags Details
Second example of corruption (1.78 MB, image/jpeg)
2019-06-10 15:57 UTC, afox@redhat.com
no flags Details
Standard background without corruption (165.45 KB, image/jpeg)
2019-06-10 15:59 UTC, afox@redhat.com
no flags Details
Third example of corrupted desktop (742.93 KB, image/jpeg)
2019-06-11 08:45 UTC, afox@redhat.com
no flags Details


Links
System ID Private Priority Status Summary Last Updated
GNOME Gitlab GNOME/gnome-shell/issues/1084 0 None None None 2019-06-21 12:33:00 UTC
Launchpad 1809407 0 None None None 2019-06-21 12:33:33 UTC
Red Hat Bugzilla 1158980 0 unspecified CLOSED Corrupted background and lockscreen after resume from suspend 2021-02-22 00:41:40 UTC

Description afox@redhat.com 2019-06-10 15:56:17 UTC
Created attachment 1579085 [details]
First example of corruption

Description of problem:
After resuming from suspend-to-ram, the gnome-shell lockscreen background, and desktop background is corrupted. 

See attached pictures.

Version-Release number of selected component (if applicable):
gnome-shell 3.32.2-2.fc30

How reproducible:
Always

Steps to Reproduce:
1. Suspend system to RAM. 
2. Resume from suspend.
3. See attached images for corruption that results. 

Actual results:
Corrupted background for gnome-shell wallpaper and lock screen wallpaper.

Expected results:
Normal background should be display without corruption. 

Additional info:
Fedora 30 x86_64 on Lenovo P50 with nVidia Quadro M1000M GPU.
Drivers are from RPM Fusion non-free repo, xorg-x11-drv-nvidia.x86_64 v3:18.74-1.fc30

Comment 1 afox@redhat.com 2019-06-10 15:57:15 UTC
Created attachment 1579086 [details]
Second example of corruption

Comment 2 afox@redhat.com 2019-06-10 15:59:00 UTC
Created attachment 1579087 [details]
Standard background without corruption

Comment 3 afox@redhat.com 2019-06-10 16:06:42 UTC
As per previous bug (linked), ALT+F2 and r restores the wallpapers to normal.
Similar issue appears to be seen in Ubuntu 18.10. 
Root cause appears to be because the Nvidia driver loses/corrupts it's texture memory upon resuming from
suspend. This is a *feature* that is officially documented in OpenGLextension "NV_robustness_video_memory_purge".

Ubuntu bug can be found here:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407

Comment 4 afox@redhat.com 2019-06-11 08:45:25 UTC
Created attachment 1579285 [details]
Third example of corrupted desktop

Comment 5 Charalampos Stratakis 2019-06-21 12:33:01 UTC
I get the same issue on nvidia drivers 430.26

It seems this upstream PR aims to solve the issue: https://gitlab.gnome.org/GNOME/mutter/merge_requests/600

Comment 6 peter 2019-07-01 12:15:25 UTC
Hello,

I also have the problem with my nVidia GeForce GT 630 graphics card. 
Every day ctrl + alt + F2 + r after login.

Regards
Peter

Comment 7 Ben Cotton 2020-04-30 21:20:44 UTC
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.

Comment 8 Ben Cotton 2020-05-26 16:37:10 UTC
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.

Comment 9 Dave Wujcik 2022-05-12 17:06:57 UTC
Just updating, Nvidia seems to have finally located the issue and plans to fix it: https://forums.developer.nvidia.com/t/corrupted-graphics-upon-resume-gnome-41-x-org-495-44-driver/194565/12


Note You need to log in before you can comment on or make changes to this bug.