SUMMARY Lattedock crashes when the application launcher is present and the icon is clicked twice. Output of `latte-dock -d` ``` [debug 6:57:12.994994] - syncGeometry() ended... [warning 6:57:46.0505] - Non-toplevel surfaces can't request window states [warning 6:57:46.088088] - Delivering update request through fallback timer, may not be in sync with display [warning 6:57:46.205205] - Delivering update request through fallback timer, may not be in sync with display [warning 6:57:46.421421] - Non-toplevel surfaces can't request window states [warning 6:57:46.725725] - Non-toplevel surfaces can't request window states [warning 6:57:47.484484] - Wayland does not support QWindow::requestActivate() KCrash: Attempting to start /usr/bin/latte-dock directly KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = latte-dock path = /usr/bin pid = 7978 KCrash: Arguments: /usr/bin/latte-dock --replace -d KCrash: Attempting to start /usr/lib/drkonqi directly [warning 6:57:48.916916] - QSocketNotifier: Invalid socket 6 and type 'Read', disabling... [warning 6:57:48.916916] - QSocketNotifier: Invalid socket 23 and type 'Read', disabling... ``` STEPS TO REPRODUCE 1. Put default KDE Launcher in latte-dock 2. Click twice on the launcher icon 3. click anywhere outside like on the desktop 4. -> Crash OBSERVED RESULT latte-dock crashes and restarts EXPECTED RESULT latte-dock should not crash SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.16.1 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.4 ADDITIONAL INFORMATION
For wayland issues you must check out if this is valid in git version
That's good to now. Just checked against the git version and it crashes too.
1. What is the crash report for Latte git version 2. Plasma panel does it crash with the same steps?
for me it crashes but without triggering kcrash I dont know why... I get: wl_display@1: error 0: invalid object 2311 [critical 17:36:27.428428] - The Wayland connection experienced a fatal error (Μη έγκυρη παράμετρος) qErrnoWarning ?libQt5WaylandClient.so.5? QtWaylandClient::QWaylandDisplay::flushRequests QMetaObject::activate QEventDispatcherGlib::processEvents QEventLoop::exec QCoreApplication::exec main which is totally upstream...
Tried getting a stack trace by running latte via gdb. I hope this is correct, as I'm not at all familiar with native development. This is the trace: Thread 15 "QSGRenderThread" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffad3db700 (LWP 25621)] 0x00007ffff4c95e94 in wl_proxy_marshal_constructor () from /usr/lib/libwayland-client.so.0 (gdb) bt #0 0x00007ffff4c95e94 in wl_proxy_marshal_constructor () at /usr/lib/libwayland-client.so.0 #1 0x00007ffff09b319b in QtWaylandClient::QWaylandWindow::handleUpdate() () at /usr/lib/libQt5WaylandClient.so.5 #2 0x00007fffedf33d78 in () at /usr/lib/qt/plugins/wayland-graphics-integration-client/libqt-plugin-wayland-egl.so #3 0x00007ffff6263142 in QOpenGLContext::swapBuffers(QSurface*) () at /usr/lib/libQt5Gui.so.5 #4 0x00007ffff77fd82e in () at /usr/lib/libQt5Quick.so.5 #5 0x00007ffff78016f8 in () at /usr/lib/libQt5Quick.so.5 #6 0x00007ffff5b2ebf0 in () at /usr/lib/libQt5Core.so.5 #7 0x00007ffff49b257f in start_thread () at /usr/lib/libpthread.so.0 #8 0x00007ffff5660f13 in clone () at /usr/lib/libc.so.6
totally Qt and wayland issue
I can confirm this bug with the default panel. There, the segfault hits plasmashell.
The same crash in Qt. *** This bug has been marked as a duplicate of bug 409050 ***