Reproduction: 1) Open kicker 2) click on any icon (for example: dolphin or kate) 3) Repeat if not crashed supportInformation: https://paste.kde.org/pem1pnp3h
If this is reproducible, please add the backtrace for the crash. For more information, please see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
It is reproducible every time, but I can't get useful backtrace. All I can get is Application: Plasma (plasmashell), signal: Segmentation fault I have already installed plasma-workspace-dbgsym, but looks like it missing debug symbols for /usr/bin/plasmashell
Please show the incomplete backtrace. With some luck, we can identify a duplicate or even the cause for the issue.
I have got only one line: Application: Plasma (plasmashell), signal: Segmentation fault Do you know how I can get missing debug symbols? Or, may be someone else can help reproduce it to get useful backtrace? I have successfully reproduced it on another machine with the same setup - kubuntu 17.10 + kubuntu backports ppa
(In reply to sergei.chernikov from comment #2) > I have already installed plasma-workspace-dbgsym, but looks like it missing > debug symbols for /usr/bin/plasmashell drkonqi is useless in 99% of the cases. https://bugs.kde.org/show_bug.cgi?id=386049
(In reply to Dr. Chapatin from comment #5) > drkonqi is useless in 99% of the cases. > https://bugs.kde.org/show_bug.cgi?id=386049 https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1701788 I think there is a problem with plasma-workspace-dbg. drkonqi works well for any other package
(In reply to sergei.chernikov from comment #6) > (In reply to Dr. Chapatin from comment #5) > > drkonqi is useless in 99% of the cases. > > https://bugs.kde.org/show_bug.cgi?id=386049 > > drkonqi works well for any other package not for me on neon dev unstable. I need use gdb to generate backtrace of crashes in several apps manually.
(In reply to Christoph Feck from comment #1) > If this is reproducible, please add the backtrace for the crash. For more > information, please see > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports I have finally been able to get a backtrace: https://paste.kde.org/pqobkqatq
Thread 19 "QSGRenderThread" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fa90abc0700 (LWP 1851)] wl_proxy_create_wrapper (proxy=0x0) at ../src/wayland-client.c:2038 2038 ../src/wayland-client.c: No such file or directory. (gdb) thread apply all backtrace Thread 19 (Thread 0x7fa90abc0700 (LWP 1851)): #0 wl_proxy_create_wrapper (proxy=0x0) at ../src/wayland-client.c:2038 #1 0x00007fa9e2c5c9f1 in ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #2 0x00007fa9e2c49d17 in ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #3 0x00007fa9e30d9f4d in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/wayland-graphics-integration-client/libwayland-egl.so #4 0x00007fa9e30d84c5 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/wayland-graphics-integration-client/libwayland-egl.so #5 0x00007faa02f15286 in QOpenGLContext::makeCurrent(QSurface*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #6 0x00007faa06221004 in QSGRenderThread::invalidateOpenGL (this=this@entry=0x557eb86d52a0, window= 0x557eb85922e0, inDestructor=<optimized out>, fallback=0x0) at scenegraph/qsgthreadedrenderloop.cpp:487 *** This bug has been marked as a duplicate of bug 381630 ***