[Bug 1174448] New: Black screen after second return from standby
http://bugzilla.opensuse.org/show_bug.cgi?id=1174448 Bug ID: 1174448 Summary: Black screen after second return from standby Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs@opensuse.org Reporter: juergen-fuhrmann@web.de QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Hi, after returning from standby the second time, the plasma unlock screen turns black and unlocking becomes impossible. System is alive though (Ctrl-Alt F1 console works, same picture after trying to return via Ctrl-Alt-F7). How to repeat: - Start system with kde plasma workspace, log in - Enter standby (e.g. via desktop menu) - Start system after standby, unlock - Enter standby (e.g. via desktop menu) - Start system, try to unlock. Laptop is a Dell Precision 5740 with NVidia Quadro T1000. Jürgen -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1174448
http://bugzilla.opensuse.org/show_bug.cgi?id=1174448#c1
--- Comment #1 from Jürgen Fuhrmann
http://bugzilla.opensuse.org/show_bug.cgi?id=1174448
http://bugzilla.opensuse.org/show_bug.cgi?id=1174448#c2
Fabian Vogt
http://bugzilla.opensuse.org/show_bug.cgi?id=1174448
http://bugzilla.opensuse.org/show_bug.cgi?id=1174448#c3
--- Comment #3 from Jürgen Fuhrmann
http://bugzilla.opensuse.org/show_bug.cgi?id=1174448
http://bugzilla.opensuse.org/show_bug.cgi?id=1174448#c4
--- Comment #4 from Jürgen Fuhrmann
http://bugzilla.opensuse.org/show_bug.cgi?id=1174448
http://bugzilla.opensuse.org/show_bug.cgi?id=1174448#c5
--- Comment #5 from Jürgen Fuhrmann
http://bugzilla.opensuse.org/show_bug.cgi?id=1174448
http://bugzilla.opensuse.org/show_bug.cgi?id=1174448#c6
--- Comment #6 from Fabian Vogt
http://bugzilla.opensuse.org/show_bug.cgi?id=1174448
http://bugzilla.opensuse.org/show_bug.cgi?id=1174448#c7
--- Comment #7 from Jürgen Fuhrmann
http://bugzilla.opensuse.org/show_bug.cgi?id=1174448
http://bugzilla.opensuse.org/show_bug.cgi?id=1174448#c8
--- Comment #8 from Jürgen Fuhrmann
http://bugzilla.opensuse.org/show_bug.cgi?id=1174448
http://bugzilla.opensuse.org/show_bug.cgi?id=1174448#c9
--- Comment #9 from Jürgen Fuhrmann
http://bugzilla.opensuse.org/show_bug.cgi?id=1174448
http://bugzilla.opensuse.org/show_bug.cgi?id=1174448#c10
--- Comment #10 from Fabian Vogt
Created attachment 840013 [details] locker-enosys-testing.txt
Result of strace -e inject=prctl:error=ENOSYS /usr/lib64/libexec/kscreenlocker_greet --testing
This shows the lockscreen and allows to unlock via password.
That means it's most likely the sandbox. To find out which syscall got blocked, please run: strace -Z /usr/lib64/libexec/kscreenlocker_greet --testing -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1174448
http://bugzilla.opensuse.org/show_bug.cgi?id=1174448#c11
--- Comment #11 from Jürgen Fuhrmann
http://bugzilla.opensuse.org/show_bug.cgi?id=1174448
http://bugzilla.opensuse.org/show_bug.cgi?id=1174448#c12
--- Comment #12 from Fabian Vogt
http://bugzilla.opensuse.org/show_bug.cgi?id=1174448
http://bugzilla.opensuse.org/show_bug.cgi?id=1174448#c13
Jürgen Fuhrmann
http://bugzilla.opensuse.org/show_bug.cgi?id=1174448
http://bugzilla.opensuse.org/show_bug.cgi?id=1174448#c14
--- Comment #14 from Jürgen Fuhrmann
http://bugzilla.opensuse.org/show_bug.cgi?id=1174448
http://bugzilla.opensuse.org/show_bug.cgi?id=1174448#c15
Fabian Vogt
Ok after installing the fixed version it seems to work. After reboot I did several standby/unlock cycles - smooth as it used to be.
Will the fix go into the next tumbleweed update ?
The issue is that this is a side effect of an OpenGL issue, most likely with the proprietary driver and probably related to suspending. It's not unlikely that in the case where kscreenlocker fails, other applications also misbehave. However, it seems like there is agreement the sandbox is not worth it (https://invent.kde.org/plasma/kscreenlocker/-/merge_requests/9), so I submitted it and we'll see what the others say: https://build.opensuse.org/request/show/822683
Amazing response! Keep the good work going!
Jürgen
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1174448
http://bugzilla.opensuse.org/show_bug.cgi?id=1174448#c16
Linus Kardell
The issue is that this is a side effect of an OpenGL issue, most likely with the proprietary driver and probably related to suspending. It's not unlikely that in the case where kscreenlocker fails, other applications also misbehave.
I do also get problems kwin compositing after suspend now. It works fine until it restarts, but then OpenGL compositing wont work at all. When running it in a terminal I get: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 180, resource id: 251658247, major code: 20 (GetProperty), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 181, resource id: 251658247, major code: 20 (GetProperty), minor code: 0 QGLXContext: Failed to create dummy context No provider of glXCreateContextAttribsARB found. Requires one of: GLX_ARB_create_context Application::crashHandler() called with signal 6; recent crashes: 1 KCrash: Application 'kwin_x11' crashing... KCrash: Attempting to start /usr/lib64/libexec/drkonqi kwin_core: Compositing is not possible -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1174448
http://bugzilla.opensuse.org/show_bug.cgi?id=1174448#c17
--- Comment #17 from Fabian Vogt
http://bugzilla.opensuse.org/show_bug.cgi?id=1174448
http://bugzilla.opensuse.org/show_bug.cgi?id=1174448#c18
--- Comment #18 from Fabian Vogt
(In reply to Fabian Vogt from comment #15)
The issue is that this is a side effect of an OpenGL issue, most likely with the proprietary driver and probably related to suspending. It's not unlikely that in the case where kscreenlocker fails, other applications also misbehave.
I do also get problems kwin compositing after suspend now. It works fine until it restarts, but then OpenGL compositing wont work at all. When running it in a terminal I get:
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 180, resource id: 251658247, major code: 20 (GetProperty), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 181, resource id: 251658247, major code: 20 (GetProperty), minor code: 0 QGLXContext: Failed to create dummy context No provider of glXCreateContextAttribsARB found. Requires one of: GLX_ARB_create_context Application::crashHandler() called with signal 6; recent crashes: 1 KCrash: Application 'kwin_x11' crashing... KCrash: Attempting to start /usr/lib64/libexec/drkonqi kwin_core: Compositing is not possible
Please open a separate bug report for that, against the Nvidia driver. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1174448
http://bugzilla.opensuse.org/show_bug.cgi?id=1174448#c19
--- Comment #19 from Linus Kardell
http://bugzilla.opensuse.org/show_bug.cgi?id=1174448
Björn Voigt
http://bugzilla.opensuse.org/show_bug.cgi?id=1174448
http://bugzilla.opensuse.org/show_bug.cgi?id=1174448#c20
--- Comment #20 from Stefan Dirsch
http://bugzilla.opensuse.org/show_bug.cgi?id=1174448
http://bugzilla.opensuse.org/show_bug.cgi?id=1174448#c21
Fabian Vogt
http://bugzilla.opensuse.org/show_bug.cgi?id=1174448
http://bugzilla.opensuse.org/show_bug.cgi?id=1174448#c22
--- Comment #22 from Jürgen Fuhrmann
http://bugzilla.opensuse.org/show_bug.cgi?id=1174448
http://bugzilla.opensuse.org/show_bug.cgi?id=1174448#c23
--- Comment #23 from Jürgen Fuhrmann
participants (1)
-
bugzilla_noreply@suse.com