[kde] [Bug 395044] New: Networking system settings module crash on applying new settings when switching to different settings view

[Marcus Harrison]

https://bugs.kde.org/show_bug.cgi?id=395044

            Bug ID: 395044
           Summary: Networking system settings module crash on applying
                    new settings when switching to different settings view
           Product: kde
           Version: unspecified
          Platform: unspecified
                OS: Linux
            Status: UNCONFIRMED
          Keywords: drkonqi
          Severity: crash
          Priority: NOR
         Component: general
          Assignee: unassigned-bugs at kde.org
          Reporter: marcus at harrisonland.co.uk
  Target Milestone: ---

Application: kcmshell5 (5.12.5)

Qt Version: 5.10.0
Frameworks Version: 5.46.0
Operating System: Linux 4.13.0-43-generic x86_64
Distribution: KDE neon User Edition 5.12

-- Information about the crash:
- What I was doing when the application crashed:

- Opened the Networking system settings module from the Plasma widget
- Made modifications to a network
- Clicked to change to a different network
- On the pop-up asking to save my changes, I chose to save changes
The crash happened before the other network's settings panel displayed and
after the dialogue window closed.

-- 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 0x7fa4d0f148c0 (LWP 21891))]

Thread 3 (Thread 0x7fa4ac405700 (LWP 21897)):
#0  0x00007fa4d08f027d in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x00007fa4c86d76f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fa4c8693e74 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fa4c8694330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007fa4c869449c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007fa4cdd785db in QEventDispatcherGlib::processEvents
(this=0x7fa4a40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#6  0x00007fa4cdd1f65a in QEventLoop::exec (this=this at entry=0x7fa4ac404ce0,
flags=..., flags at entry=...) at kernel/qeventloop.cpp:212
#7  0x00007fa4cdb3f554 in QThread::exec (this=this at entry=0xb83010) at
thread/qthread.cpp:522
#8  0x00007fa4cc648a35 in QQmlThreadPrivate::run (this=0xb83010) at
qml/ftw/qqmlthread.cpp:147
#9  0x00007fa4cdb446eb in QThreadPrivate::start (arg=0xb83010) at
thread/qthread_unix.cpp:376
#10 0x00007fa4ca5836ba in start_thread (arg=0x7fa4ac405700) at
pthread_create.c:333
#11 0x00007fa4d090041d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7fa4b48aa700 (LWP 21893)):
#0  0x00007fa4d08f027d in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x00007fa4c86d76f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fa4c8693e74 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fa4c8694330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007fa4c869449c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007fa4cdd785db in QEventDispatcherGlib::processEvents
(this=0x7fa4b00008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#6  0x00007fa4cdd1f65a in QEventLoop::exec (this=this at entry=0x7fa4b48a9cd0,
flags=..., flags at entry=...) at kernel/qeventloop.cpp:212
#7  0x00007fa4cdb3f554 in QThread::exec (this=<optimized out>) at
thread/qthread.cpp:522
#8  0x00007fa4ce19b2c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#9  0x00007fa4cdb446eb in QThreadPrivate::start (arg=0x7fa4ce40fd60) at
thread/qthread_unix.cpp:376
#10 0x00007fa4ca5836ba in start_thread (arg=0x7fa4b48aa700) at
pthread_create.c:333
#11 0x00007fa4d090041d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7fa4d0f148c0 (LWP 21891)):
[KCrash Handler]
#6  0x00007fa4cdd4deb2 in QObjectPrivate::isSignalConnected
(checkDeclarative=false, signal_index=35, this=<optimized out>) at
kernel/qobject_p.h:260
#7  QMetaObject::activate (sender=0x1023c20, signalOffset=<optimized out>,
local_signal_index=<optimized out>, argv=argv at entry=0x7fff9cfe4830) at
kernel/qobject.cpp:3647
#8  0x00007fa4cc59c705 in QQmlVMEMetaObject::activate
(this=this at entry=0x106eec0, object=<optimized out>, index=index at entry=52,
args=args at entry=0x7fff9cfe4830) at qml/qqmlvmemetaobject.cpp:1243
#9  0x00007fa4cc59e9a4 in QQmlVMEMetaObject::metaCall (this=0x106eec0,
o=<optimized out>, c=QMetaObject::InvokeMetaMethod, _id=52, a=0x7fff9cfe4830)
at qml/qqmlvmemetaobject.cpp:921
#10 0x00007fa4cc5fabf9 in QQmlObjectOrGadget::metacall
(this=this at entry=0x7fff9cfe4ba0, type=type at entry=QMetaObject::InvokeMetaMethod,
index=index at entry=52, argv=<optimized out>) at qml/qqmlpropertycache.cpp:1732
#11 0x00007fa4cc5775bd in CallMethod (object=..., index=<optimized out>,
returnType=<optimized out>, argCount=<optimized out>, argTypes=<optimized out>,
engine=engine at entry=0xa5a320, callArgs=0x7fa4ab3c63b8,
callType=QMetaObject::InvokeMetaMethod) at jsruntime/qv4qobjectwrapper.cpp:1158
#12 0x00007fa4cc578c8d in CallPrecise (object=..., data=...,
engine=engine at entry=0xa5a320, callArgs=callArgs at entry=0x7fa4ab3c63b8,
callType=callType at entry=QMetaObject::InvokeMetaMethod) at
jsruntime/qv4qobjectwrapper.cpp:1420
#13 0x00007fa4cc579ed0 in QV4::QObjectMethod::callInternal (this=<optimized
out>, callData=0x7fa4ab3c63b8, scope=...) at
jsruntime/qv4qobjectwrapper.cpp:1966
#14 0x00007fa4cc58f6be in QV4::Object::call (d=0x7fa4ab3c63b8, scope=...,
this=<optimized out>) at jsruntime/qv4object_p.h:445
#15 QV4::Runtime::method_callActivationProperty (engine=<optimized out>,
nameIndex=<optimized out>, callData=0x7fa4ab3c63b8) at
jsruntime/qv4runtime.cpp:1052
#16 0x00007fa4bc02aa8d in ?? ()
#17 0x0000000000000000 in ?? ()

Reported using DrKonqi

-- 
You are receiving this mail because:
You are the assignee for the bug.