Bug 385370 - Crash System Settings Module
Summary: Crash System Settings Module
Status: RESOLVED WORKSFORME
Alias: None
Product: plasma-nm
Classification: Plasma
Component: kcm (show other bugs)
Version: 5.8.7
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Jan Grulich
URL:
Keywords: drkonqi
: 385613 (view as bug list)
Depends on:
Blocks:
 
Reported: 2017-10-04 17:44 UTC by JohnMcLaren
Modified: 2019-07-10 12:08 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description JohnMcLaren 2017-10-04 17:44:59 UTC
Application: kcmshell5 (5.8.7)

Qt Version: 5.9.1
Frameworks Version: 5.37.0
Operating System: Linux 4.12.0-kali2-amd64 x86_64
Distribution: Kali GNU/Linux Rolling

-- Information about the crash:
- What I was doing when the application crashed:
Connections - System Settings Module
1. Check tab "General configuration" for "Wired connection 1"
2. Set option "Automatically connect to VPN when using this connection"
3. Select VPN from list
4. Press Ok and we have message about crash programm.

The crash can be reproduced every time.

-- Backtrace:
Application: System Settings Module (kcmshell5), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fe03ccb6e00 (LWP 6971))]

Thread 2 (Thread 0x7fe021438700 (LWP 6973)):
#0  0x00007fe034844fcd in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x00007fe03484522c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fe039cc841b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x00007fe039c6ddba in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x00007fe039a8d3ca in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007fe03b934e45 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#6  0x00007fe039a9229d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007fe036a45494 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#8  0x00007fe03c625abf in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 1 (Thread 0x7fe03ccb6e00 (LWP 6971)):
[KCrash Handler]
#6  0x00007fe03a127940 in typeinfo for QDynamicMetaObjectData () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007fe03ac7b6c5 in QWidget::destroy(bool, bool) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#8  0x00007fe03ac47070 in QApplication::~QApplication() () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#9  0x00007fe03c8e1e02 in kdemain () from /usr/lib/x86_64-linux-gnu/libkdeinit5_kcmshell5.so
#10 0x00007fe03c55d2e1 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
#11 0x000055c8840787ca in _start ()

Reported using DrKonqi
Comment 1 Jan Grulich 2017-10-05 05:03:12 UTC
Could you please install all relevant debug symbols (plasma-nm, networkmanager-qt, kcmshell and so on) and provide better backtrace?
Comment 2 JohnMcLaren 2017-10-06 18:49:38 UTC
Hi, Yan. I can not find debug symbols for this packages in my repositories. Can you tell me how I can install it?
Comment 3 Christoph Feck 2017-10-11 16:34:08 UTC
*** Bug 385613 has been marked as a duplicate of this bug. ***
Comment 4 mikefarmer02 2017-10-12 17:52:39 UTC
(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
Comment 5 mikefarmer02 2017-10-12 18:52:41 UTC
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 ()
Comment 6 Jan Grulich 2017-10-23 08:28:14 UTC
The backtrace is still not really helpfull and I'm still unable to reproduce this issue.
Comment 7 mikefarmer02 2017-11-02 20:24:36 UTC
Is there something I can do to provide a better backtrace?
Comment 8 Jan Grulich 2019-07-10 12:08:33 UTC
I believe this is no longer a problem. Please re-open if you still can reproduce this issue.