Bug 375210 - System Settings Module generates crash notification when closing normally
Summary: System Settings Module generates crash notification when closing normally
Status: RESOLVED DUPLICATE of bug 374990
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2017-01-18 02:38 UTC by GJ
Modified: 2017-01-31 23:25 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description GJ 2017-01-18 02:38:24 UTC
Application: kcmshell5 (5.8.95)

Qt Version: 5.8.0
Frameworks Version: 5.30.0
Operating System: Linux 4.8.13-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
Closing System Settings module by clicking OK or Cancel.  Whether or not changes have been made while the module was open does not matter.

The crash can be reproduced every time.

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

Thread 3 (Thread 0x7fabe2ff9700 (LWP 9544)):
#0  0x00007fabfea5e48d in poll () from /usr/lib/libc.so.6
#1  0x00007fabf6c66786 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x00007fabf6c6689c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#3  0x00007fabfc1393eb in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#4  0x00007fabfc0e2c1a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#5  0x00007fabfbf049f3 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x00007fabfdae80c5 in ?? () from /usr/lib/libQt5DBus.so.5
#7  0x00007fabfbf09658 in ?? () from /usr/lib/libQt5Core.so.5
#8  0x00007fabf8e82454 in start_thread () from /usr/lib/libpthread.so.0
#9  0x00007fabfea677df in clone () from /usr/lib/libc.so.6

Thread 2 (Thread 0x7fabeb68c700 (LWP 9543)):
#0  0x00007fabfea5e48d in poll () from /usr/lib/libc.so.6
#1  0x00007fabf92a78e0 in ?? () from /usr/lib/libxcb.so.1
#2  0x00007fabf92a9679 in xcb_wait_for_event () from /usr/lib/libxcb.so.1
#3  0x00007fabedbf0239 in ?? () from /usr/lib/libQt5XcbQpa.so.5
#4  0x00007fabfbf09658 in ?? () from /usr/lib/libQt5Core.so.5
#5  0x00007fabf8e82454 in start_thread () from /usr/lib/libpthread.so.0
#6  0x00007fabfea677df in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7fabff054580 (LWP 9542)):
[KCrash Handler]
#6  0x00000000018e3d30 in ?? ()
#7  0x00007fabfce02e95 in QWidget::destroy(bool, bool) () from /usr/lib/libQt5Widgets.so.5
#8  0x00007fabfcdc6eb0 in QApplication::~QApplication() () from /usr/lib/libQt5Widgets.so.5
#9  0x00007fabfed25025 in kdemain () from /usr/lib/libkdeinit5_kcmshell5.so
#10 0x00007fabfe99f291 in __libc_start_main () from /usr/lib/libc.so.6
#11 0x000000000040066a in _start ()

Reported using DrKonqi
Comment 1 Christoph Feck 2017-01-18 20:37:26 UTC
Which systemsettings module did you select?
Comment 2 Christoph Feck 2017-01-25 00:21:39 UTC
No reply, assuming it is a duplicate of bug 373628.

If you have new information, please add a comment.
Comment 3 GJ 2017-01-28 12:43:44 UTC
It was the Connection Editor (the beta?) version in the 'KDE unstable' repo (Arch - Antergos).  I have since downgraded to use the standard repo and the problem is not evident using v5.8.5 of the Connection Editor.
Comment 4 Christoph Feck 2017-01-31 23:25:51 UTC
Thanks for the update. See bug 374990.

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