Bug 446713 - Settings app error or crash when getting more theming components.
Summary: Settings app error or crash when getting more theming components.
Status: RESOLVED DUPLICATE of bug 439797
Alias: None
Product: systemsettings
Classification: Applications
Component: general (show other bugs)
Version: 5.23.4
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-12-09 07:19 UTC by Walter Lesaulnier
Modified: 2022-01-10 16:21 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 Walter Lesaulnier 2021-12-09 07:19:42 UTC
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Install global theme or theming component from settings app "get more"
2. 
3. 

OBSERVED RESULT
slow download thru settings app, sometimes error, sometimes settings app crash - seems to be proportional to download size

EXPECTED RESULT
Install global theme or theming component

SOFTWARE/OS VERSIONS
I distro hop a lot and this behavior happens in many different distros with the Plasma desktop environment- same problem whether the distro is on bare metal or a guest in Virtualbox

ADDITIONAL INFORMATION
This may be a specific connection error problem when the settings app downloads from KDE servers. I have had this issue in many different distros with Plasma for years on multiple different desktop PCs. I have a fairly old Arris router with my Spectrum internet which may be involved. Possibly an issue between the network manager and KDE servers that only occurs within the settings app. Internet connection works perfectly everywhere in the OS except when installing new theming from KDE.org from the settings app. Oddly, this issue does not happen in Fedora Workstation with the KDE/ Plasma desktop.
I am a newbie, so please be patient with my lack of proper bug reporting skills.
Comment 1 Nate Graham 2021-12-09 19:27:55 UTC
As the note at the top says:

> NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
> See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

:)
Comment 2 Walter Lesaulnier 2021-12-10 15:29:46 UTC
Application: System Settings (systemsettings5), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr<char []> = {get() = <optimized out>}
[KCrash Handler]
#6  0x00007f6e9201e799 in QDir::fromNativeSeparators(QString const&) () at io/qdir.cpp:930
#7  0x00007f6e92032325 in QFileInfoPrivate::QFileInfoPrivate (file=..., this=0x5621e1c406d0) at /usr/include/c++/11/bits/atomic_base.h:338
#8  QFileInfo::QFileInfo (this=this@entry=0x7ffc78df7b80, file=...) at io/qfileinfo.cpp:347
#9  0x00007f6e744711d4 in operator() (__closure=<synthetic pointer>) at /usr/src/debug/plasma5-workspace-5.23.4-1.1.x86_64/kcms/lookandfeel/kcm.cpp:117
#10 KCMLookandFeel::knsEntryChanged (wrapper=<optimized out>, this=0x5621db8a5670) at /usr/src/debug/plasma5-workspace-5.23.4-1.1.x86_64/kcms/lookandfeel/kcm.cpp:126
#11 KCMLookandFeel::knsEntryChanged (wrapper=<optimized out>, this=0x5621db8a5670) at /usr/src/debug/plasma5-workspace-5.23.4-1.1.x86_64/kcms/lookandfeel/kcm.cpp:110
#12 KCMLookandFeel::qt_static_metacall (_o=0x5621db8a5670, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at /usr/src/debug/plasma5-workspace-5.23.4-1.1.x86_64/build/kcms/lookandfeel/kcm_lookandfeel_static_autogen/EWIEGA46WW/moc_kcm.cpp:128
#13 0x00007f6e744713ab in KCMLookandFeel::qt_metacall (this=0x5621db8a5670, _c=QMetaObject::InvokeMetaMethod, _id=5, _a=0x7ffc78df7d70) at /usr/src/debug/plasma5-workspace-5.23.4-1.1.x86_64/build/kcms/lookandfeel/kcm_lookandfeel_static_autogen/EWIEGA46WW/moc_kcm.cpp:214
#14 0x00007f6e90f5a04d in QQmlObjectOrGadget::metacall (this=this@entry=0x7ffc78df8000, type=type@entry=QMetaObject::InvokeMetaMethod, index=<optimized out>, index@entry=43, argv=<optimized out>) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.2.x86_64/src/qml/qml/qqmlobjectorgadget.cpp:51
#15 0x00007f6e90e39120 in CallMethod (callType=<optimized out>, callArgs=0xffffffff, engine=<optimized out>, argTypes=<optimized out>, argCount=<optimized out>, returnType=<optimized out>, index=<optimized out>, object=...) at /usr/include/qt5/QtCore/qvarlengtharray.h:190
#16 CallPrecise (object=..., data=..., engine=engine@entry=0x5621da66ed70, callArgs=callArgs@entry=0x7f6e586015b8, callType=callType@entry=QMetaObject::InvokeMetaMethod) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.2.x86_64/src/qml/jsruntime/qv4qobjectwrapper.cpp:1569
#17 0x00007f6e90e3af0b in CallOverloaded (callType=<optimized out>, propertyCache=<optimized out>, callArgs=<optimized out>, engine=<optimized out>, data=..., object=...) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.2.x86_64/src/qml/jsruntime/qv4qobjectwrapper.cpp:1645
#18 QV4::QObjectMethod::callInternal (this=<optimized out>, thisObject=<optimized out>, argv=<optimized out>, argc=<optimized out>) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.2.x86_64/src/qml/jsruntime/qv4qobjectwrapper.cpp:2133
#19 0x00007f6e90e57b53 in QV4::FunctionObject::call (argc=<optimized out>, argv=<optimized out>, thisObject=<optimized out>, this=<optimized out>) at ../../include/QtQml/5.15.2/QtQml/private/../../../../../../src/qml/jsruntime/qv4functionobject_p.h:202
#20 QV4::Moth::VME::interpret (frame=0x7ffc78df82c0, engine=0x5621da66ed70, code=0x7f6e58601568 "@\333\336\062n\177") at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.2.x86_64/src/qml/jsruntime/qv4vme_moth.cpp:754
#21 0x00007f6e90e5a7e7 in QV4::Moth::VME::exec (frame=frame@entry=0x7ffc78df82c0, engine=engine@entry=0x5621da66ed70) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.2.x86_64/src/qml/jsruntime/qv4vme_moth.cpp:463
#22 0x00007f6e90dedc6e in QV4::Function::call (this=this@entry=0x5621da1f5cb0, thisObject=<optimized out>, argv=argv@entry=0x7f6e58601510, argc=<optimized out>, context=<optimized out>) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.2.x86_64/src/qml/jsruntime/qv4function.cpp:69
#23 0x00007f6e90f74c05 in QQmlJavaScriptExpression::evaluate (this=this@entry=0x5621de342e40, callData=callData@entry=0x7f6e586014e0, isUndefined=isUndefined@entry=0x0) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.2.x86_64/src/qml/qml/qqmljavascriptexpression.cpp:212
#24 0x00007f6e90f2665b in QQmlBoundSignalExpression::evaluate (this=<optimized out>, a=<optimized out>) at ../../include/QtQml/5.15.2/QtQml/private/../../../../../../src/qml/jsruntime/qv4jscall_p.h:95
#25 0x00007f6e90f27848 in QQmlBoundSignal_callback (e=0x5621de342ed0, a=0x7ffc78df9f20) at ../../include/QtQml/5.15.2/QtQml/private/../../../../../../src/qml/qml/qqmlboundsignalexpressionpointer_p.h:69
#26 0x00007f6e90f59af5 in QQmlNotifier::emitNotify (endpoint=<optimized out>, a=0x7ffc78df9f20) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.2.x86_64/src/qml/qml/qqmlnotifier.cpp:104
#27 0x00007f6e9213eba8 in doActivate<false> (sender=0x5621deca0870, signal_index=18, argv=0x7ffc78df9f20) at kernel/qobject.cpp:3778
#28 0x00007f6e9213850f in QMetaObject::activate (sender=<optimized out>, m=m@entry=0x7f6e7411dac0 <Engine::staticMetaObject>, local_signal_index=local_signal_index@entry=15, argv=argv@entry=0x7ffc78df9f20) at kernel/qobject.cpp:3946
#29 0x00007f6e7410a7ac in Engine::entryEvent (_t2=Engine::StatusChangedEvent, _t1=0x7f6e8800f0a0, this=<optimized out>) at /usr/src/debug/knewstuff-5.88.0-1.1.x86_64/build/src/qtquick/newstuffqmlplugin_autogen/EWIEGA46WW/moc_quickengine.cpp:600
#30 operator() (event=KNSCore::EntryInternal::StatusChangedEvent, entry=..., __closure=0x5621deccd8e0) at /usr/src/debug/knewstuff-5.88.0-1.1.x86_64/src/qtquick/quickengine.cpp:144
#31 QtPrivate::FunctorCall<QtPrivate::IndexesList<0, 1>, QtPrivate::List<const KNSCore::EntryInternal&, KNSCore::EntryInternal::EntryEvent>, void, Engine::setConfigFile(const QString&)::<lambda(const KNSCore::EntryInternal&, KNSCore::EntryInternal::EntryEvent)> >::call (arg=<optimized out>, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:146
#32 QtPrivate::Functor<Engine::setConfigFile(const QString&)::<lambda(const KNSCore::EntryInternal&, KNSCore::EntryInternal::EntryEvent)>, 2>::call<QtPrivate::List<KNSCore::EntryInternal const&, KNSCore::EntryInternal::EntryEvent>, void> (arg=<optimized out>, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:256
#33 QtPrivate::QFunctorSlotObject<Engine::setConfigFile(const QString&)::<lambda(const KNSCore::EntryInternal&, KNSCore::EntryInternal::EntryEvent)>, 2, QtPrivate::List<const KNSCore::EntryInternal&, KNSCore::EntryInternal::EntryEvent>, void>::impl (which=<optimized out>, r=<optimized out>, ret=<optimized out>, a=<optimized out>, this_=0x5621deccd8d0) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:443
#34 QtPrivate::QFunctorSlotObject<Engine::setConfigFile(const QString&)::<lambda(const KNSCore::EntryInternal&, KNSCore::EntryInternal::EntryEvent)>, 2, QtPrivate::List<const KNSCore::EntryInternal&, KNSCore::EntryInternal::EntryEvent>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=<optimized out>, this_=0x5621deccd8d0, r=<optimized out>, a=<optimized out>, ret=<optimized out>) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:436
#35 0x00007f6e9213f043 in QtPrivate::QSlotObjectBase::call (a=0x7ffc78dfa060, r=0x5621deca0870, this=0x5621deccd8d0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#36 doActivate<false> (sender=0x5621decccb50, signal_index=27, argv=0x7ffc78dfa060) at kernel/qobject.cpp:3886
#37 0x00007f6e9213850f in QMetaObject::activate (sender=<optimized out>, m=m@entry=0x7f6e7444f220 <KNSCore::Engine::staticMetaObject>, local_signal_index=local_signal_index@entry=24, argv=argv@entry=0x7ffc78dfa060) at kernel/qobject.cpp:3946
#38 0x00007f6e743ec3e6 in KNSCore::Engine::signalEntryEvent (this=<optimized out>, _t1=..., _t2=<optimized out>) at /usr/src/debug/knewstuff-5.88.0-1.1.x86_64/build/src/core/KF5NewStuffCore_autogen/EWIEGA46WW/moc_engine.cpp:794
#39 0x00007f6e9213f043 in QtPrivate::QSlotObjectBase::call (a=0x7ffc78dfa160, r=0x5621decccb50, this=0x5621e03b28b0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#40 doActivate<false> (sender=0x5621decccc50, signal_index=3, argv=0x7ffc78dfa160) at kernel/qobject.cpp:3886
#41 0x00007f6e9213850f in QMetaObject::activate (sender=<optimized out>, m=m@entry=0x7f6e7444f160 <KNSCore::Installation::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffc78dfa160) at kernel/qobject.cpp:3946
#42 0x00007f6e743ec502 in KNSCore::Installation::signalEntryChanged (this=<optimized out>, _t1=...) at /usr/src/debug/knewstuff-5.88.0-1.1.x86_64/build/src/core/KF5NewStuffCore_autogen/EWIEGA46WW/moc_installation.cpp:269
#43 0x00007f6e744102bd in operator() (__closure=0x5621dec08c40, job=0x7ffc78dfa1a8) at /usr/src/debug/knewstuff-5.88.0-1.1.x86_64/src/core/installation.cpp:501
#44 0x00007f6e9213f043 in QtPrivate::QSlotObjectBase::call (a=0x7ffc78dfa330, r=0x5621decccc50, this=0x5621dec08c30) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#45 doActivate<false> (sender=0x5621ddb75670, signal_index=6, argv=0x7ffc78dfa330) at kernel/qobject.cpp:3886
#46 0x00007f6e9213850f in QMetaObject::activate (sender=sender@entry=0x5621ddb75670, m=<optimized out>, local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7ffc78dfa330) at kernel/qobject.cpp:3946
#47 0x00007f6e92439c7c in KJob::result (this=this@entry=0x5621ddb75670, _t1=<optimized out>, _t1@entry=0x5621ddb75670, _t2=...) at /usr/src/debug/kcoreaddons-5.88.0-1.1.x86_64/build/src/lib/KF5CoreAddons_autogen/include/moc_kjob.cpp:633
#48 0x00007f6e9243e01b in KJob::finishJob (this=0x5621ddb75670, emitResult=<optimized out>) at /usr/src/debug/kcoreaddons-5.88.0-1.1.x86_64/src/lib/jobs/kjob.cpp:98
#49 0x00007f6e92134fee in QObject::event (this=0x5621ddb75670, e=0x7f6e3c014250) at kernel/qobject.cpp:1314
#50 0x00007f6e92db9a7f in QApplicationPrivate::notify_helper (this=<optimized out>, receiver=0x5621ddb75670, e=0x7f6e3c014250) at kernel/qapplication.cpp:3632
#51 0x00007f6e921089fa in QCoreApplication::notifyInternal2 (receiver=0x5621ddb75670, event=0x7f6e3c014250) at kernel/qcoreapplication.cpp:1064
#52 0x00007f6e9210ba47 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x5621d9dbe480) at kernel/qcoreapplication.cpp:1821
#53 0x00007f6e92160853 in postEventSourceDispatch (s=s@entry=0x5621d9ed9df0) at kernel/qeventdispatcher_glib.cpp:277
#54 0x00007f6e8fc69d4f in g_main_dispatch (context=0x7f6e88005000) at ../glib/gmain.c:3381
#55 g_main_context_dispatch (context=0x7f6e88005000) at ../glib/gmain.c:4099
#56 0x00007f6e8fc6a0d8 in g_main_context_iterate (context=context@entry=0x7f6e88005000, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../glib/gmain.c:4175
#57 0x00007f6e8fc6a18f in g_main_context_iteration (context=0x7f6e88005000, may_block=1) at ../glib/gmain.c:4240
#58 0x00007f6e9215fed4 in QEventDispatcherGlib::processEvents (this=0x5621d9ee1ec0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#59 0x00007f6e921073fb in QEventLoop::exec (this=this@entry=0x7ffc78dfa740, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69
#60 0x00007f6e9210f6e0 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121
#61 0x00007f6e9265b18c in QGuiApplication::exec () at kernel/qguiapplication.cpp:1867
#62 0x00007f6e92db99f5 in QApplication::exec () at kernel/qapplication.cpp:2824
#63 0x00005621d910110b in main (argc=<optimized out>, argv=0x7ffc78dfa860) at /usr/src/debug/systemsettings5-5.23.4-1.1.x86_64/app/main.cpp:208
[Inferior 1 (process 1845) detached]
Comment 3 Bug Janitor Service 2021-12-25 04:34:56 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 4 Bug Janitor Service 2022-01-09 04:35:21 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!
Comment 5 Walter Lesaulnier 2022-01-09 04:51:42 UTC
(In reply to Bug Janitor Service from comment #4)
> 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!

I thought I supplied the requested info in my reply on 2021-12-10 15:29:46 UTC.
PLEASE simplify and automate bug reporting. Not everyone that uses Linux is an IT professional with lots of education and experience in/ with Linux. An automated error reporting pop-up after an error/ crash would be WONDERFUL.
Comment 6 Nate Graham 2022-01-10 16:21:54 UTC
Ah, you forgot to change the status back to REPORTED after adding the backtrace.

Either way thanks for the backtrace. Looks like this is a duplicate of Bug 439797439797

> An automated error reporting pop-up after an error/ crash would be WONDERFUL.
We have one of those. I'm surprised it didn't appear here.

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