https://bugs.kde.org/show_bug.cgi?id=512448

--- Comment #7 from Brent Spillner <[email protected]> ---
Trace from the newest crash pasted below; it looks like the failures are being
triggered (or at least recognized) within the !sizeWithMargins.isEmpty() &&
!m_waylandEglWindow && create && mSurface QMetaCallEvents branch of
QWaylandEglWindow::updateSurface().  Specifically, the eglCreateWindowSurface()
call at
https://github.com/qt/qtbase/blob/dev/src/plugins/platforms/wayland/plugins/hardwareintegration/wayland-egl/qwaylandeglwindow.cpp#L120
is ultimately triggering QWaylandIntegration::clientBufferIntegration() ->
QWaylandIntegration::Initialize() -> QWaylandDisplay::initEventThread() ->
checkWaylandError(), and then returning a failure code back up the stack.  I
don't know enough about wayland-egl to know what's causing the failure, but
perhaps QMetaCallEvents are being delivered out-of-order from the EGL backend's
perspective?  Are there any good tools for tracing that event queue?

wl_registry#51: error 0: invalid global kde_output_device_v2 (168)
[Thread 0x7fffec80f6c0 (LWP 22651) exited]
warning: queue "mesa egl surface queue" 0x7fff58509540 destroyed while proxies
still attached:
  wp_presentation#43 still attached
qt.qpa.wayland: Could not create EGL surface (EGL error 0x3000)

[Thread 0x7fff567fc6c0 (LWP 28719) exited]
[Thread 0x7fff56ffd6c0 (LWP 28718) exited]
[Thread 0x7fff577fe6c0 (LWP 28717) exited]
[Thread 0x7fff57fff6c0 (LWP 28716) exited]
[Thread 0x7fff6512f6c0 (LWP 28715) exited]
[Thread 0x7fffa2ffd6c0 (LWP 28714) exited]
[Thread 0x7fffbeffd6c0 (LWP 28713) exited]
The Wayland connection experienced a fatal error: Protocol error

Thread 1 "plasmashell" hit Breakpoint 4.1, 0x00007ffff3b76e10 in _exit () from
/lib64/libc.so.6
(gdb) bt
#0  0x00007ffff3b76e10 in _exit () at /lib64/libc.so.6
#1  0x00007ffff56671b7 in QtWaylandClient::QWaylandDisplay::checkWaylandError()
() at /usr/lib64/libQt6WaylandClient.so.6
#2  0x00007ffff445d772 in QObject::event(QEvent*) () at
/usr/lib64/libQt6Core.so.6
#3  0x00007ffff6ef4238 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQt6Widgets.so.6
#4  0x00007ffff43ed898 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib64/libQt6Core.so.6
#5  0x00007ffff43f146e in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib64/libQt6Core.so.6
#6  0x00007ffff477e417 in ??? () at /usr/lib64/libQt6Core.so.6
#7  0x00007ffff2842ad6 in ??? () at /usr/lib64/libglib-2.0.so.0
#8  0x00007ffff2845bdf in ??? () at /usr/lib64/libglib-2.0.so.0
#9  0x00007ffff284630c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#10 0x00007ffff477e5b8 in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
at /usr/lib64/libQt6Core.so.6
#11 0x00007ffff43fc296 in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at
/usr/lib64/libQt6Core.so.6
#12 0x00007ffff43f61ac in QCoreApplication::exec() () at
/usr/lib64/libQt6Core.so.6
#13 0x000000000042e391 in ??? ()
#14 0x00007ffff3ab6d14 in __libc_start_call_main () at /lib64/libc.so.6
#15 0x00007ffff3ab6dc6 in __libc_start_main_impl () at /lib64/libc.so.6
#16 0x000000000042e4a1 in ??? ()

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to