| Summary: | Crash System Settings Module | ||
|---|---|---|---|
| Product: | [Plasma] plasma-nm | Reporter: | JohnMcLaren <mastakjob> |
| Component: | kcm | Assignee: | Jan Grulich <jgrulich> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | jgrulich, mikefarmer02 |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | 5.8.7 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
JohnMcLaren
2017-10-04 17:44:59 UTC
Could you please install all relevant debug symbols (plasma-nm, networkmanager-qt, kcmshell and so on) and provide better backtrace? Hi, Yan. I can not find debug symbols for this packages in my repositories. Can you tell me how I can install it? *** Bug 385613 has been marked as a duplicate of this bug. *** (In reply to JohnMcLaren from comment #2) > Hi, Yan. I can not find debug symbols for this packages in my repositories. > Can you tell me how I can install it? This might help: https://wiki.debian.org/HowToGetABacktrace#Installing_the_debugging_symbols This is the backtrace after installing some debug-symbols: Application: Modul für Systemeinstellungen (kcmshell5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f57f4cde600 (LWP 17312))] Thread 3 (Thread 0x7f57d8548700 (LWP 17314)): #0 0x00007f57f464e66d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x00007f57ec8a3119 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007f57ec8a322c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007f57f1cfa41b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x00007f57f1c9fdba in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x00007f57f1abf3ca in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x00007f57f3966e45 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x00007f57f1ac429d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x00007f57eea77494 in start_thread (arg=0x7f57d8548700) at pthread_create.c:333 #9 0x00007f57f4657abf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 2 (Thread 0x7f57e147d700 (LWP 17313)): #0 0x00007f57f464e66d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x00007f57ef2ec150 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x00007f57ef2edee9 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x00007f57e39def09 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x00007f57f1ac429d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x00007f57eea77494 in start_thread (arg=0x7f57e147d700) at pthread_create.c:333 #6 0x00007f57f4657abf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 1 (Thread 0x7f57f4cde600 (LWP 17312)): [KCrash Handler] #6 0x00005559bac426d0 in ?? () #7 0x00007f57f2cad6c5 in QWidget::destroy (this=0x5559bad99270, destroyWindow=destroyWindow@entry=true, destroySubWindows=destroySubWindows@entry=true) at kernel/qwidget.cpp:12359 #8 0x00007f57f2c79070 in QApplication::~QApplication (this=0x7ffdda0c2690, __in_chrg=<optimized out>) at kernel/qapplication.cpp:819 #9 0x00007f57f4913e02 in kdemain () from /usr/lib/x86_64-linux-gnu/libkdeinit5_kcmshell5.so #10 0x00007f57f458f2e1 in __libc_start_main (main=0x5559b9a13790, argc=2, argv=0x7ffdda0c27c8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffdda0c27b8) at ../csu/libc-start.c:291 #11 0x00005559b9a137ca in _start () The backtrace is still not really helpfull and I'm still unable to reproduce this issue. Is there something I can do to provide a better backtrace? I believe this is no longer a problem. Please re-open if you still can reproduce this issue. |