Open Saviq opened 1 year ago
So it's enough to run confined-shell
a few times, if connected to nvidia-core22
:
2023-04-04 20:43:46 - [main.c:299] Found config * for output OUT-0 ((null))
[2023-04-04 20:43:46.999744] < CRITICAL! > mirserver: terminate_with_current_exception(): ./src/platforms/eglstream-kms/server/display.cpp(274): Throw in function virtual void {anonymous}::DisplayBuffer::
post()
Dynamic exception type: boost::wrapexcept<std::system_error>
std::exception::what: Failed to submit frame from EGLStream for display: Unknown error (0x3353)
[2023-04-04 20:43:46.999862] < - debug - > mirserver: Handling Terminated from pid=34506
ERROR: ./src/platforms/eglstream-kms/server/display.cpp(274): Throw in function virtual void {anonymous}::DisplayBuffer::post()
Dynamic exception type: boost::wrapexcept<std::system_error>
std::exception::what: Failed to submit frame from EGLStream for display: Unknown error (0x3353)
warn: bar/wayland.c:757: 2023-04-04 20:43:47 - unknown global removed: 0x00000003
[main.c:351] Destroying output OUT-0 ((null))
warn: bar/wayland.c:757: unknown global removed: 0x00000002
warn: bar/wayland.c:757: unknown global removed: 0x00000017
warn: bar/wayland.c:757: unknown global removed: 0x00000016
warn: bar/wayland.c:757: unknown global removed: 0x00000015
warn: bar/wayland.c:757: unknown global removed: 0x00000008
warn: bar/wayland.c:757: unknown global removed: 0x00000009
warn: bar/wayland.c:757: unknown global removed: 0x0000000a
warn: bar/wayland.c:757: unknown global removed: 0x0000000b
warn: bar/wayland.c:757: unknown global removed: 0x0000000c
warn: bar/wayland.c:757: unknown global removed: 0x0000000d
warn: bar/wayland.c:757: unknown global removed: 0x0000000e
warn: bar/wayland.c:757: unknown global removed: 0x00000012
warn: bar/wayland.c:757: unknown global removed: 0x00000010
warn: bar/wayland.c:757: unknown global removed: 0x00000014
warn: bar/wayland.c:757: unknown global removed: 0x0000000f
warn: bar/wayland.c:757: unknown global removed: 0x00000013
warn: bar/wayland.c:757: unknown global removed: 0x00000011
warn: bar/wayland.c:757: unknown global removed: 0x00000018
warn: bar/wayland.c:757: unknown global removed: 0x00000007
info: bar/wayland.c:744: OUT-0 disconnected/disabled
warn: bar/wayland.c:757: unknown global removed: 0x00000005
warn: bar/wayland.c:757: unknown global removed: 0x00000004
I was unable to reproduce outside of snap confinement (whether installed or --devmode
) - but snappy-debug doesn't seem to highlight anything interesting (and this doesn't happen every time):
Xwayland aside, we should be handling that exception better in Mir: at worst disconnecting the client. Not terminating.
Originally posted by @AlanGriffiths in https://github.com/MirServer/mir/issues/2871#issuecomment-1476084126