Bug 395044 - Networking system settings module crash on applying new settings when switching to different settings view
Summary: Networking system settings module crash on applying new settings when switchi...
Status: RESOLVED WORKSFORME
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_networkmanagement (show other bugs)
Version: 5.17.4
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Jan Grulich
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2018-06-05 08:41 UTC by Marcus Harrison
Modified: 2022-11-02 05:05 UTC (History)
1 user (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 Marcus Harrison 2018-06-05 08:41:38 UTC
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@entry=0x7fa4ac404ce0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#7  0x00007fa4cdb3f554 in QThread::exec (this=this@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@entry=0x7fa4b48a9cd0, flags=..., flags@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@entry=0x7fff9cfe4830) at kernel/qobject.cpp:3647
#8  0x00007fa4cc59c705 in QQmlVMEMetaObject::activate (this=this@entry=0x106eec0, object=<optimized out>, index=index@entry=52, args=args@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@entry=0x7fff9cfe4ba0, type=type@entry=QMetaObject::InvokeMetaMethod, index=index@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@entry=0xa5a320, callArgs=0x7fa4ab3c63b8, callType=QMetaObject::InvokeMetaMethod) at jsruntime/qv4qobjectwrapper.cpp:1158
#12 0x00007fa4cc578c8d in CallPrecise (object=..., data=..., engine=engine@entry=0xa5a320, callArgs=callArgs@entry=0x7fa4ab3c63b8, callType=callType@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
Comment 1 Justin Zobel 2022-10-03 23:55:08 UTC
Thank you for reporting this crash in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the crash with a recent software version?

If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
Comment 2 Bug Janitor Service 2022-10-18 04:57:45 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2022-11-02 05:05:57 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!