You are not logged in.
In System Settings>Appearence>Global Theme everytime I try to download a new theme it prompts for a password the crashes. When I restart the application under Global Themes it shows the theme is installed. However if I click on Get New Global Themes the themes still show install next to them like they were not installed correctly. If I click install then the window crashes again. Here is the crash log.
Application: System Settings (systemsettings5), signal: Segmentation fault
[KCrash Handler]
#4 0x00007f2cfefe4859 in QDir::fromNativeSeparators(QString const&) () at /usr/lib/libQt5Core.so.5
#5 0x00007f2cfeff8907 in QFileInfo::QFileInfo(QString const&) () at /usr/lib/libQt5Core.so.5
#6 0x00007f2cade21ed7 in () at /usr/lib/qt/plugins/kcms/kcm_lookandfeel.so
#7 0x00007f2cade1fa0b in () at /usr/lib/qt/plugins/kcms/kcm_lookandfeel.so
#8 0x00007f2cfdf5fc9e in () at /usr/lib/libQt5Qml.so.5
#9 0x00007f2cfde3b121 in () at /usr/lib/libQt5Qml.so.5
#10 0x00007f2cfde3cf6b in QV4::QObjectMethod::callInternal(QV4::Value const*, QV4::Value const*, int) const () at /usr/lib/libQt5Qml.so.5
#11 0x00007f2cfde5a0c0 in () at /usr/lib/libQt5Qml.so.5
#12 0x00007f2cfde5cdbf in () at /usr/lib/libQt5Qml.so.5
#13 0x00007f2cfddef0df in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () at /usr/lib/libQt5Qml.so.5
#14 0x00007f2cfdf7af36 in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) () at /usr/lib/libQt5Qml.so.5
#15 0x00007f2cfdf2b53d in QQmlBoundSignalExpression::evaluate(void**) () at /usr/lib/libQt5Qml.so.5
#16 0x00007f2cfdf2c799 in () at /usr/lib/libQt5Qml.so.5
#17 0x00007f2cfdf5f755 in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () at /usr/lib/libQt5Qml.so.5
#18 0x00007f2cff109308 in () at /usr/lib/libQt5Core.so.5
#19 0x00007f2caddee771 in () at /usr/lib/qt/qml/org/kde/newstuff/libnewstuffqmlplugin.so
#20 0x00007f2caddf6d4b in () at /usr/lib/qt/qml/org/kde/newstuff/libnewstuffqmlplugin.so
#21 0x00007f2cff1097ab in () at /usr/lib/libQt5Core.so.5
#22 0x00007f2cadd411c7 in KNSCore::Engine::signalEntryEvent(KNSCore::EntryInternal const&, KNSCore::EntryInternal::EntryEvent) () at /usr/lib/libKF5NewStuffCore.so.5
#23 0x00007f2cff1097ab in () at /usr/lib/libQt5Core.so.5
#24 0x00007f2cadd40483 in KNSCore::Installation::signalEntryChanged(KNSCore::EntryInternal const&) () at /usr/lib/libKF5NewStuffCore.so.5
#25 0x00007f2cadd6edd0 in () at /usr/lib/libKF5NewStuffCore.so.5
#26 0x00007f2cff1097ab in () at /usr/lib/libQt5Core.so.5
#27 0x00007f2cff3d00dd in KJob::result(KJob*, KJob::QPrivateSignal) () at /usr/lib/libKF5CoreAddons.so.5
#28 0x00007f2cff3d15cc in KJob::finishJob(bool) () at /usr/lib/libKF5CoreAddons.so.5
#29 0x00007f2cff0ff54f in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5
#30 0x00007f2cffcc3d62 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5
#31 0x00007f2cff0d23fa in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5
#32 0x00007f2cff0d54f9 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5
#33 0x00007f2cff12b9f4 in () at /usr/lib/libQt5Core.so.5
#34 0x00007f2cfcc874dc in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0
#35 0x00007f2cfccdb749 in () at /usr/lib/libglib-2.0.so.0
#36 0x00007f2cfcc84bc1 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
#37 0x00007f2cff12b026 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#38 0x00007f2cff0d0d6c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#39 0x00007f2cff0d92d4 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5
#40 0x0000556b02e98954 in ()
#41 0x00007f2cfea5eb25 in __libc_start_main () at /usr/lib/libc.so.6
#42 0x0000556b02e996be in ()
[Inferior 1 (process 3212) detached]A quick search online for this particular problem suggests deleting the .config folder under the user directory, or creating a new user. Both of those options are overkill in my opinion.
Does anyone know the exact file/folder to delete instead?
Last edited by pacman41 (2021-10-29 12:12:46)
Offline
See https://bugs.kde.org/show_bug.cgi?id=439797
When you say "this particular problem" do you mean a systemsettings crash in this KCM, or this specific backtrace? Because crashes can be caused by lots of different issues and there's no guarantee that a workaround for one of them will work for another one.
Online
See https://bugs.kde.org/show_bug.cgi?id=439797
When you say "this particular problem" do you mean a systemsettings crash in this KCM, or this specific backtrace? Because crashes can be caused by lots of different issues and there's no guarantee that a workaround for one of them will work for another one.
Sorry quick search for "(systemsettings5), signal: Segmentation fault" yielded those results
Offline