[Bug 1175945] New: After suspend/resume, some UI regions are blacked out
http://bugzilla.opensuse.org/show_bug.cgi?id=1175945 Bug ID: 1175945 Summary: After suspend/resume, some UI regions are blacked out Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs@opensuse.org Reporter: tilman.vogel@web.de QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:79.0) Gecko/20100101 Firefox/79.0 Build Identifier: Some regions in the UI are completely black while other work fine. The black regions also don't react to user-interaction (e.g. clicking blindly), so it's not just a visual issue, it seems. In the specific case, the network property editor connection list is blacked-out. The details on the right for the current connection are still visible but I cannot blindly select a different connection in the blacked-out list. Reproducible: Always Steps to Reproduce: 1. Suspend/resume 2. Open network properties via the Network-Manager applet Actual Results: UI partially blacked-out and non-functional Expected Results: UI visible and functional This is on a Thinkpad 20QN-000EGE with x11-video-nvidiaG05-450.57-38.1.x86_64 Tumbleweed snapshot 20200807 Using suse-prime-0.7.14-1.1.noarch # prime-select get-current Driver configured: intel [bbswitch] NVIDIA card is ON NVIDIA Quadro T1000 Screenshot available. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1175945 http://bugzilla.opensuse.org/show_bug.cgi?id=1175945#c1 --- Comment #1 from Tilman Vogel <tilman.vogel@web.de> --- Created attachment 841205 --> http://bugzilla.opensuse.org/attachment.cgi?id=841205&action=edit Screenshot showing blacked-out region -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1175945 Tilman Vogel <tilman.vogel@web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tilman.vogel@web.de -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1175945 http://bugzilla.opensuse.org/show_bug.cgi?id=1175945#c2 Wolfgang Bauer <wbauer@tmo.at> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wbauer@tmo.at --- Comment #2 from Wolfgang Bauer <wbauer@tmo.at> --- The main problem is that the nvidia driver doesn't properly support suspend/resume... Does it help if you add the following to ~/.config/kdeglobals ? [QtQuickRendererSettings] GraphicsResetNotifications=true The last comments in https://bugs.kde.org/show_bug.cgi?id=364766 suggest that this is still (or again?) necessary with current Qt versions, although it should actually be the default since 5.13 AIUI. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1175945 http://bugzilla.opensuse.org/show_bug.cgi?id=1175945#c3 Wolfgang Bauer <wbauer@tmo.at> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED See Also| |https://bugs.kde.org/show_b | |ug.cgi?id=424592 Resolution|--- |UPSTREAM --- Comment #3 from Wolfgang Bauer <wbauer@tmo.at> --- This seems to be the exact same problem as in https://bugs.kde.org/show_bug.cgi?id=424592, and it's apparently a bug/regression in the nvidia driver. A workaround for systemsettings5 to avoid the problem has been proposed here: https://invent.kde.org/plasma/systemsettings/-/merge_requests/21#note_110373 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1175945 http://bugzilla.opensuse.org/show_bug.cgi?id=1175945#c4 --- Comment #4 from Wolfgang Bauer <wbauer@tmo.at> --- (In reply to Wolfgang Bauer from comment #3)
This seems to be the exact same problem as in https://bugs.kde.org/show_bug.cgi?id=424592, and it's apparently a bug/regression in the nvidia driver. To quote:
Comment 11 David Edmundson 2020-08-21 10:52:29 UTC Created attachment 131075 [details] Test case of the bug at hand Report for the nvidia people: Attached is a test case that creates a context and immediately calls glGetGraphicsResetStatusARB() On boot if I run this as an application I get GL_NO_ERROR and this app will quit and exit. This happens for every time the program is run - as expected. Now with this program *NOT RUNNING* suspend and resume. Every new invocation of the app will print "Graphics reset status! : 37563" This appears to be new with nvidia 450. Subsequent calls appear to be correct, but it still doesn't make sense for us to be told context has been lost when it wasn't lost whilst we were running. Comment 12 Erik Kurzinger 2020-08-25 01:06:20 UTC Dang. Yes, this is indeed a regression in the 450 NVIDIA driver. Thank you for narrowing it down, David. I've identified the root cause and will try to get a fix included in the next minor version. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com