I also have this issue sometimes.

Same crash as in bug 385633.

Lets resolve it the other way around; bug 385628 was reported first, and already confirmed.

Reverting status.

*** Bug 387103 has been marked as a duplicate of this bug. ***

Created attachment 110043 [details]
New crash information added by DrKonqi

konsole (18.03.70) using Qt 5.10.0

- What I was doing when the application crashed:

- Open Konsole
- Start an SSH session
- Close the Konsole window, while the SSH session is still running
- Select "Close Current Tab" from dialog
- Konsole crashes

-- Backtrace (Reduced):
#6  0x00007f2e4d404bc9 in wl_map_insert_at (map=<optimized out>, flags=flags@entry=0, i=<optimized out>, data=<optimized out>) at /var/tmp/portage/dev-libs/wayland-1.13.0/work/wayland-1.13.0/src/wayland-util.c:249
#7  0x00007f2e4d400ebe in proxy_destroy (proxy=0x55a522cf9760) at /var/tmp/portage/dev-libs/wayland-1.13.0/work/wayland-1.13.0/src/wayland-client.c:411
#8  wl_proxy_destroy (proxy=proxy@entry=0x55a522cf9760) at /var/tmp/portage/dev-libs/wayland-1.13.0/work/wayland-1.13.0/src/wayland-client.c:442
#9  0x00007f2e4c014267 in org_kde_plasma_window_destroy (org_kde_plasma_window=0x55a522cf9760) at /var/tmp/portage/kde-frameworks/kwayland-9999/work/kwayland-9999_build/src/client/wayland-plasma-window-management-client-protocol.h:634
#10 KWayland::Client::WaylandPointer<org_kde_plasma_window, org_kde_plasma_window_destroy>::release (this=0x55a522cf2d40, this=0x55a522cf2d40) at /var/tmp/portage/kde-frameworks/kwayland-9999/work/kwayland-9999/src/client/wayland_pointer_p.h:53

Created attachment 110625 [details]
New crash information added by DrKonqi

konsole (17.12.2) using Qt 5.10.0

- What I was doing when the application crashed:
I closed two windows of konsole and crash handler reported konsole had not exited cleanely.

- Custom settings of the application:
I have "Run all konsole windows in a single process" checked. So this crash is triggered when I close the last konsole window.

-- Backtrace (Reduced):
#6  0x00007fc9444af7e7 in wl_proxy_destroy () from /usr/lib/libwayland-client.so.0
#7  0x00007fc942e042e9 in KWayland::Client::PlasmaWindow::release() () from /usr/lib/libKF5WaylandClient.so.5
#8  0x00007fc942e0430b in KWayland::Client::PlasmaWindow::~PlasmaWindow() () from /usr/lib/libKF5WaylandClient.so.5
#9  0x00007fc942e0440a in KWayland::Client::PlasmaWindow::~PlasmaWindow() () from /usr/lib/libKF5WaylandClient.so.5
#10 0x00007fc952232bbd in QObjectPrivate::deleteChildren() () from /usr/lib/libQt5Core.so.5

I get the same crash whenever I close Latte under wayland, do we know if this is the app fault or kwayland one?

Application: Latte Dock (latte-dock), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f99891988c0 (LWP 7943))]

Thread 1 (Thread 0x7f99891988c0 (LWP 7943)):
[KCrash Handler]
#4  0x00007f998096e5b9 in ?? () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0
#5  0x00007f998096a7be in wl_proxy_destroy () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0
#6  0x00007f99882ddbd7 in KWayland::Client::PlasmaWindow::release() () from /usr/lib/x86_64-linux-gnu/libKF5WaylandClient.so.5
#7  0x00007f99882ddbfa in KWayland::Client::PlasmaWindow::~PlasmaWindow() () from /usr/lib/x86_64-linux-gnu/libKF5WaylandClient.so.5
#8  0x00007f99882ddce9 in KWayland::Client::PlasmaWindow::~PlasmaWindow() () from /usr/lib/x86_64-linux-gnu/libKF5WaylandClient.so.5
#9  0x00007f998397df73 in QObjectPrivate::deleteChildren() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007f9983987e94 in QObject::~QObject() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x00007f99882de289 in KWayland::Client::PlasmaWindowManagement::~PlasmaWindowManagement() () from /usr/lib/x86_64-linux-gnu/libKF5WaylandClient.so.5
#12 0x00007f998397df73 in QObjectPrivate::deleteChildren() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x00007f9983987e94 in QObject::~QObject() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x00007f99642126a3 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/org.kde.kwindowsystem.platforms/KF5WindowSystemKWaylandPlugin.so
#15 0x00007f9982a96ff8 in __run_exit_handlers (status=0, listp=0x7f9982e215f8 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82
#16 0x00007f9982a97045 in __GI_exit (status=<optimized out>) at exit.c:104
#17 0x00007f9982a7d837 in __libc_start_main (main=0x43cdd0 <main>, argc=2, argv=0x7ffe94c6fdb8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffe94c6fda8) at ../csu/libc-start.c:325
#18 0x000000000043ece9 in _start ()

It's Qt & Wayland (somewhere in the stack). It's a lottery whether the application is going to crash. :(

> It's Qt & Wayland (somewhere in the stack). It's a lottery whether the application is going to crash. :(

for Latte is happening always on exit... :(

> It's Qt & Wayland (somewhere in the stack). It's a lottery whether the application is going to crash. :(

I tracked that down for Latte and also the Activity Pager. For Latte has nothing to do with Qt & Wayland. It is a faulty use of PlasmaWindowManagement.
infos can be found here: https://bugs.kde.org/show_bug.cgi?id=391263

I dont know of course if this is also the case for kate, does kate internally use PlasmaWindowManagement somehow?

Discussing it with David (few months ago) suggested the issue to be in QtWayland, which all applications use.

Kate for example doesn't use any of this KWayland::Client and also gets the crash.

> Discussing it with David (few months ago) suggested the issue to be in QtWayland, which all applications use.

I see... It might be of different origin, btw for Latte I fixed the mentioned crash when exiting the application.

This crash is produced always with konsole when konsole has 2 or more tabs open and the user closes that window.

Hmm, I don't see this as an Kate issue.
Somebody else must decide if KWayland, the integration or Qt, I am not familiar enough with that stuff.

*** This bug has been marked as a duplicate of bug 390151 ***