the system settings does not open after I have changed the style of the windows, is it possible to enter safe mode with the default theme settings? for me to change that. And I have another question, how do I open system settings from the terminal?
1 Like
Welcome to the forum! 
Um, there is to the best of my knowledge no such thing as “safe mode” like you get in Microsoft Windows. GNU/Linux is an entirely different operating system. 
nohup systemsettings5 > /dev/null 2>&1 &
sorry, i’m a beginner. I used the command on the terminal, but it didn’t open. I just changed the style of the apps in the application style option and this is happening. funny that all applications are working normally, except the system settings.
is there another way to change styles other than system settings?
Well, starting System Settings from the command line would normally produce output, but the command I gave you suppresses that. Try this instead…: 
systemsettings5
Not for window decorations, no. But since you haven’t told us what exactly you did, we also have no idea what you may have corrupted along the way. What you could eventually do is delete the following files ─ make a backup copy first…:
~/.config/kwin*~/.local/share/kwin/scripts/*~/.cache/kwin/qmlcache/*
But that is all if your problem is with the window decorations. If it’s with another aspect of the theming, then we’re going to have to look elsewhere. 
I used systemsettings5 and that was the result, does it say anything?
theme “Numix-Circle” not found.
Invalid Context= “Legacy” line for icon theme: “/usr/share/icons/Adwaita/8x8/legacy/”
Invalid Context= “Legacy” line for icon theme: “/usr/share/icons/Adwaita/16x16/legacy/”
Invalid Context= “UI” line for icon theme: “/usr/share/icons/Adwaita/16x16/ui/”
Invalid Context= “Legacy” line for icon theme: “/usr/share/icons/Adwaita/22x22/legacy/”
Invalid Context= “Legacy” line for icon theme: “/usr/share/icons/Adwaita/24x24/legacy/”
Invalid Context= “UI” line for icon theme: “/usr/share/icons/Adwaita/24x24/ui/”
Invalid Context= “Legacy” line for icon theme: “/usr/share/icons/Adwaita/32x32/legacy/”
Invalid Context= “UI” line for icon theme: “/usr/share/icons/Adwaita/32x32/ui/”
Invalid Context= “Legacy” line for icon theme: “/usr/share/icons/Adwaita/48x48/legacy/”
Invalid Context= “UI” line for icon theme: “/usr/share/icons/Adwaita/48x48/ui/”
Invalid Context= “Legacy” line for icon theme: “/usr/share/icons/Adwaita/64x64/legacy/”
Invalid Context= “UI” line for icon theme: “/usr/share/icons/Adwaita/64x64/ui/”
Invalid Context= “Legacy” line for icon theme: “/usr/share/icons/Adwaita/96x96/legacy/”
Invalid Context= “UI” line for icon theme: “/usr/share/icons/Adwaita/96x96/ui/”
Invalid Context= “Legacy” line for icon theme: “/usr/share/icons/Adwaita/256x256/legacy/”
Invalid Context= “Legacy” line for icon theme: “/usr/share/icons/Adwaita/512x512/legacy/”
Invalid Context= “Legacy” line for icon theme: “/usr/share/icons/Adwaita/scalable/legacy/”
Invalid Context= “UI” line for icon theme: “/usr/share/icons/Adwaita/scalable/ui/”
Cyclic dependency detected between “file:///usr/lib/qt/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml” and “file:///usr/lib/qt/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml”
Icon theme “Numix-Circle” not found.
Invalid Context= “Legacy” line for icon theme: “/usr/share/icons/Adwaita/8x8/legacy/”
Invalid Context= “Legacy” line for icon theme: “/usr/share/icons/Adwaita/16x16/legacy/”
Invalid Context= “UI” line for icon theme: “/usr/share/icons/Adwaita/16x16/ui/”
Invalid Context= “Legacy” line for icon theme: “/usr/share/icons/Adwaita/22x22/legacy/”
Invalid Context= “Legacy” line for icon theme: “/usr/share/icons/Adwaita/24x24/legacy/”
Invalid Context= “UI” line for icon theme: “/usr/share/icons/Adwaita/24x24/ui/”
Invalid Context= “Legacy” line for icon theme: “/usr/share/icons/Adwaita/32x32/legacy/”
Invalid Context= “UI” line for icon theme: “/usr/share/icons/Adwaita/32x32/ui/”
Invalid Context= “Legacy” line for icon theme: “/usr/share/icons/Adwaita/48x48/legacy/”
Invalid Context= “UI” line for icon theme: “/usr/share/icons/Adwaita/48x48/ui/”
Invalid Context= “Legacy” line for icon theme: “/usr/share/icons/Adwaita/64x64/legacy/”
Invalid Context= “UI” line for icon theme: “/usr/share/icons/Adwaita/64x64/ui/”
Invalid Context= “Legacy” line for icon theme: “/usr/share/icons/Adwaita/96x96/legacy/”
Invalid Context= “UI” line for icon theme: “/usr/share/icons/Adwaita/96x96/ui/”
Invalid Context= “Legacy” line for icon theme: “/usr/share/icons/Adwaita/256x256/legacy/”
Invalid Context= “Legacy” line for icon theme: “/usr/share/icons/Adwaita/512x512/legacy/”
Invalid Context= “Legacy” line for icon theme: “/usr/share/icons/Adwaita/scalable/legacy/”
Invalid Context= “UI” line for icon theme: “/usr/share/icons/Adwaita/scalable/ui/”
file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/SubCategoryPage.qml:141:9: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo() { … }
file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/SubCategoryPage.qml:131:9: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo() { … }
file:///usr/lib/qt/qml/org/kde/kirigami.2/private/RefreshableScrollView.qml:143:13: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo() { … }
file:///usr/lib/qt/qml/org/kde/kirigami.2/private/RefreshableScrollView.qml:143:13: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo() { … }
Cyclic dependency detected between “file:///usr/lib/qt/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml” and “file:///usr/lib/qt/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml”
QQmlEngine::setContextForObject(): Object already has a QQmlContext
qt.qpa.xcb: QXcbConnection: XCB error: 5 (BadAtom), sequence: 618, resource id: 0, major code: 20 (GetProperty), minor code: 0
Segmentation failure (core image recorded)
I think I’m going to reinstall the system, I already wanted to clean it up. Thank you for your help.
Got the same problem as this guy, i changed my window decoration in the customization section of the System Settings and now it doesn’t open, i’d like to know a way to fix this without needing to resort to reinstalling the system
This is what shows up when i run the systemsettings5 command
systemsettings5
Icon theme "Breeze-Noir-Black-Blue" not found.
Cyclic dependency detected between "file:///usr/lib/qt/qml/org/kde/kirigami.2/styles/org.kde.desktop.pl
asma/Units.qml" and "file:///usr/lib/qt/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml"
Icon theme "Breeze-Noir-Black-Blue" not found.
file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/SubCategoryPage.qml:14
1:9: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this synta
x instead: function onFoo(<arguments>) { ... }
file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/SubCategoryPage.qml:13
1:9: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this synta
x instead: function onFoo(<arguments>) { ... }
file:///usr/lib/qt/qml/org/kde/kirigami.2/private/RefreshableScrollView.qml:143:13: QML Connections: Im
plicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFo
o(<arguments>) { ... }
file:///usr/lib/qt/qml/org/kde/kirigami.2/private/RefreshableScrollView.qml:143:13: QML Connections: Im
plicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFo
o(<arguments>) { ... }
Cyclic dependency detected between "file:///usr/lib/qt/qml/org/kde/kirigami.2/styles/org.kde.desktop.pl
asma/Units.qml" and "file:///usr/lib/qt/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml"
QQmlEngine::setContextForObject(): Object already has a QQmlContext
qt.qpa.xcb: QXcbConnection: XCB error: 5 (BadAtom), sequence: 614, resource id: 0, major code: 20 (GetP
roperty), minor code: 0
Falha de segmentação (imagem do núcleo gravada)I too am having similar issues of not being able to change themes or start systemsettings5. Its crashing my plasmashell as well.
If I try and run systemssettings5 from bash:
Cyclic dependency detected between "file:///usr/lib/qt/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml" and "file:///usr/lib/qt/qml/org/kde/kirigami.2/styles/org.kde.des
ktop.plasma/Units.qml"
file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/SubCategoryPage.qml:141:9: QML Connections: Implicitly defined onFoo properties in Connections are depr
ecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/SubCategoryPage.qml:131:9: QML Connections: Implicitly defined onFoo properties in Connections are depr
ecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/lib/qt/qml/org/kde/kirigami.2/private/RefreshableScrollView.qml:143:13: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax
instead: function onFoo(<arguments>) { ... }
file:///usr/lib/qt/qml/org/kde/kirigami.2/private/RefreshableScrollView.qml:143:13: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax
instead: function onFoo(<arguments>) { ... }
Cyclic dependency detected between "file:///usr/lib/qt/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml" and "file:///usr/lib/qt/qml/org/kde/kirigami.2/styles/org.kde.des
ktop.plasma/Units.qml"
QQmlEngine::setContextForObject(): Object already has a QQmlContext
qt.qpa.xcb: QXcbConnection: XCB error: 5 (BadAtom), sequence: 635, resource id: 0, major code: 20 (GetProperty), minor code: 0
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = systemsettings5 path = /usr/bin pid = 47769
KCrash: Arguments: /usr/bin/systemsettings5
KCrash: Attempting to start /usr/lib/drkonqi
qt.qpa.xcb: QXcbConnection: XCB error: 5 (BadAtom), sequence: 500, resource id: 0, major code: 20 (GetProperty), minor code: 0
[1]+ Stopped systemsettings5
the core dumps:
Process 35996 (systemsettings5) of user 1000 dumped core.
Stack trace of thread 35996:
#0 0x00007f43d0142d90 _ZNK7QObject10objectNameEv (libQt5Core.so.5 + 0x2ddd90)
#1 0x00007f43d17ca208 _ZNK9chameleon14ChameleonStyle11drawControlEN6QStyle14ControlElementEPK12QStyleOptionP8QPainterPK7QWidget (lib>
#2 0x00007f43d17c45ad _ZNK9chameleon14ChameleonStyle18drawComplexControlEN6QStyle14ComplexControlEPK19QStyleOptionComplexP8QPainterP>
#3 0x00007f43b91e0760 n/a (libqqc2desktopstyleplugin.so + 0x15760)
#4 0x00007f43b91e1791 n/a (libqqc2desktopstyleplugin.so + 0x16791)
#5 0x00007f43cf5a70c6 _ZN19QQuickWindowPrivate11polishItemsEv (libQt5Quick.so.5 + 0x2560c6)
#6 0x00007f43cf62f3c0 _ZN19QQuickRenderControl11polishItemsEv (libQt5Quick.so.5 + 0x2de3c0)
#7 0x00007f43cf8c9e48 n/a (libQt5QuickWidgets.so.5 + 0x9e48)
#8 0x00007f43d0ca859e _ZN7QWidget5eventEP6QEvent (libQt5Widgets.so.5 + 0x19c59e)
#9 0x00007f43d0c66752 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x15a752)
#10 0x00007f43d0118cda _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b3cda)
#11 0x00007f43d0c9f810 _ZN14QWidgetPrivate30sendPendingMoveAndResizeEventsEbb (libQt5Widgets.so.5 + 0x193810)
#12 0x00007f43d0ca42f4 _ZN14QWidgetPrivate11show_helperEv (libQt5Widgets.so.5 + 0x1982f4)
#13 0x00007f43d0ca764d _ZN14QWidgetPrivate10setVisibleEb (libQt5Widgets.so.5 + 0x19b64d)
#14 0x00007f43d0ca4273 _ZN14QWidgetPrivate12showChildrenEb (libQt5Widgets.so.5 + 0x198273)
#15 0x00007f43d0ca4312 _ZN14QWidgetPrivate11show_helperEv (libQt5Widgets.so.5 + 0x198312)
#16 0x00007f43d0ca428a _ZN14QWidgetPrivate12showChildrenEb (libQt5Widgets.so.5 + 0x19828a)
#17 0x00007f43d0ca4312 _ZN14QWidgetPrivate11show_helperEv (libQt5Widgets.so.5 + 0x198312)
#18 0x00007f43d0ca764d _ZN14QWidgetPrivate10setVisibleEb (libQt5Widgets.so.5 + 0x19b64d)
#19 0x00007f43d0ca4273 _ZN14QWidgetPrivate12showChildrenEb (libQt5Widgets.so.5 + 0x198273)
#20 0x00007f43d0ca4312 _ZN14QWidgetPrivate11show_helperEv (libQt5Widgets.so.5 + 0x198312)
#21 0x00007f43d0ca764d _ZN14QWidgetPrivate10setVisibleEb (libQt5Widgets.so.5 + 0x19b64d)
#22 0x0000560f5bf090ab n/a (systemsettings5 + 0x100ab)
#23 0x0000560f5bf0aac6 n/a (systemsettings5 + 0x11ac6)
#24 0x00007f43d01457e2 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2e07e2)
#25 0x00007f43d1702f6a _ZN13KXmlGuiWindow5eventEP6QEvent (libKF5XmlGui.so.5 + 0x91f6a)
#26 0x00007f43d0c66752 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x15a752)
#27 0x00007f43d0118cda _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b3cda)
#28 0x00007f43d011b7d3 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5 + 0x2b67d3)
#29 0x00007f43d0172304 n/a (libQt5Core.so.5 + 0x30d304)
#30 0x00007f43cde06bfc g_main_context_dispatch (libglib-2.0.so.0 + 0x52bfc)
#31 0x00007f43cde581f9 n/a (libglib-2.0.so.0 + 0xa41f9)
#32 0x00007f43cde05421 g_main_context_iteration (libglib-2.0.so.0 + 0x51421)
#33 0x00007f43d0171941 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x30c94>
#34 0x00007f43d011765c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b265c)
#35 0x00007f43d011faf4 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2baaf4)
#36 0x0000560f5bf05806 n/a (systemsettings5 + 0xc806)
#37 0x00007f43cfae7152 __libc_start_main (libc.so.6 + 0x28152)
#38 0x0000560f5bf064ae _start (systemsettings5 + 0xd4ae)
Stack trace of thread 35998:
#0 0x00007f43cfbb446f __poll (libc.so.6 + 0xf546f)
#1 0x00007f43ce81e63b n/a (libxcb.so.1 + 0xc63b)
#2 0x00007f43ce82037b xcb_wait_for_event (libxcb.so.1 + 0xe37b)
#3 0x00007f43cb305f61 n/a (libQt5XcbQpa.so.5 + 0x5df61)
#4 0x00007f43cff32e8f n/a (libQt5Core.so.5 + 0xcde8f)
#5 0x00007f43ce85f3e9 start_thread (libpthread.so.0 + 0x93e9)
#6 0x00007f43cfbbf293 __clone (libc.so.6 + 0x100293)
Stack trace of thread 36002:
#0 0x00007f43ce8659c8 pthread_cond_timedwait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf9c8)
#1 0x00007f43cff39058 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt5Core.so.5 + 0xd4058)
#2 0x00007f43cff36fc4 n/a (libQt5Core.so.5 + 0xd1fc4)
#3 0x00007f43cff32e8f n/a (libQt5Core.so.5 + 0xcde8f)
#4 0x00007f43ce85f3e9 start_thread (libpthread.so.0 + 0x93e9)
#5 0x00007f43cfbbf293 __clone (libc.so.6 + 0x100293)
Stack trace of thread 35999:
#0 0x00007f43cfbb446f __poll (libc.so.6 + 0xf546f)
#1 0x00007f43cde58188 n/a (libglib-2.0.so.0 + 0xa4188)
#2 0x00007f43cde05421 g_main_context_iteration (libglib-2.0.so.0 + 0x51421)
#3 0x00007f43d0171941 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x30c94>
#4 0x00007f43d011765c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b265c)
#5 0x00007f43cff31ca2 _ZN7QThread4execEv (libQt5Core.so.5 + 0xccca2)
#6 0x00007f43d03ce098 n/a (libQt5DBus.so.5 + 0x17098)
#7 0x00007f43cff32e8f n/a (libQt5Core.so.5 + 0xcde8f)
#8 0x00007f43ce85f3e9 start_thread (libpthread.so.0 + 0x93e9)
#9 0x00007f43cfbbf293 __clone (libc.so.6 + 0x100293)
Stack trace of thread 36003:
#0 0x00007f43ce8659c8 pthread_cond_timedwait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf9c8)
#1 0x00007f43cff39058 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt5Core.so.5 + 0xd4058)
#2 0x00007f43cff36fc4 n/a (libQt5Core.so.5 + 0xd1fc4)
#3 0x00007f43cff32e8f n/a (libQt5Core.so.5 + 0xcde8f)
#4 0x00007f43ce85f3e9 start_thread (libpthread.so.0 + 0x93e9)
#5 0x00007f43cfbbf293 __clone (libc.so.6 + 0x100293)
I had similar issues, so that only some of the systemsettings parts (e.g., systemd) worked fine, but clicking on the workspace, windows, display, etc. options would crash systemsettings.
The clue to fixing it was that running ss5 via a different user worked fine, pointing to a problem in the .config files. (Starting ss5 via terminal showed errors that were similar in the crashing and working users–not helpful.)
Restoring a backup of ~.config/ fixed the issue. Setting global theme, plasma, application style, and window decorations to some combination of breath or breeze brought the bug back. Restoring backup and setting the global theme, plasma & application style, and window decorations to oxygen worked fine. Some part of breathn or breeze or some other plasma style was causing the problem.
You can download a icon theme as xxx.tar.xz from “gnome-look” website , and run System Setting from command line:
systemsettings5 /path/to/downloadedtheme.tar.xz.
This will replace the missing pack for once and allow you to enter the panel to modify manually.
Just had the same issue. . . .won’t initialize after changing the theme. . . .this is garbage. . . . time for another OS ‘shell’ . . . guess I’ll see if gnome crashes. . . . .
Rich 
Same issue as threxel. The sad part is this is a fresh install, all I’ve done is update apps once. I didn’t even change the theme!
$ systemsettings5
Cyclic dependency detected between "file:///usr/lib/qt/qml/org/kde/kirigami.
2/styles/org.kde.desktop.plasma/Units.qml" and "file:///usr/lib/qt/qml/org/k
de/kirigami.2/styles/org.kde.desktop.plasma/Units.qml"
file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/content
s/ui/SubCategoryPage.qml:142:9: QML Connections: Implicitly defined onFoo pr
operties in Connections are deprecated. Use this syntax instead: function on
Foo(<arguments>) { ... }
file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/content
s/ui/SubCategoryPage.qml:132:9: QML Connections: Implicitly defined onFoo pr
operties in Connections are deprecated. Use this syntax instead: function on
Foo(<arguments>) { ... }
file:///usr/lib/qt/qml/org/kde/kirigami.2/private/RefreshableScrollView.qml:
137:13: QML Connections: Implicitly defined onFoo properties in Connections
are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/lib/qt/qml/org/kde/kirigami.2/private/RefreshableScrollView.qml:
137:13: QML Connections: Implicitly defined onFoo properties in Connections
are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
Cyclic dependency detected between "file:///usr/lib/qt/qml/org/kde/kirigami.
2/styles/org.kde.desktop.plasma/Units.qml" and "file:///usr/lib/qt/qml/org/k
de/kirigami.2/styles/org.kde.desktop.plasma/Units.qml"
QQmlEngine::setContextForObject(): Object already has a QQmlContext
Failed to create OpenGL context for format QSurfaceFormat(version 2.0, optio
ns QFlags<QSurfaceFormat::FormatOption>(ResetNotification), depthBufferSize
24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize
-1, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuf
fer, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile
QSurfaceFormat::NoProfile)
Aborted (core dumped)
By the way, running systemsettings5 on a downloaded theme produced a similar error.
*edit: reboot helped but I worry for other noobies.
$shutdown -r now
Hi,guys. I had the same issue and now found the answer from reddit/r/ManjaroLinux/comments/hl9oox/i_broke_kde5_settings_with_a_theme/ .
just run systemsettings5 --style=Breeze in the konsole，then the system settings open, now you can change the global theme back and apply.
the “-style” can’t be found in the output of systemsettings5 --help-all, but it works.
hope it help you.
6 Likes
I have the same problem , but this all started when i installed “xfce” desktop in manjaro kde . in the installation it said ‘’‘the manjaro-settings-manager is conflicting between xfce settings manager, do you want to remove manjaro settings manager’’’. and then i clicked yes , and after that xfce and kde both run fluidly but i cant access the settings in kde. If i run systemsettings5 in the terminal it gives ----- ‘’’’ systemsettings5: symbol lookup error: /usr/lib/libsystemsettingsview.so.3: undefined symbol: _ZN14KCModuleLoader10isDefaultsERK12KCModuleInfoRK11QStringList ‘’’.
Now i need help , can anyone help me in this problem, thanks in advance.
Whilst seemingly not “frowned upon” so much here as on other Forums, I’d still generally advise against the practice due to issues/conflicts with configurations as you experienced here.
You might be able to repair the damage by reinstalling those packages which were removed. Hopefully those Xfce settings won’t in practice conflict with the KDE ones but adding more than one DE is not something I’ve tried myself.
It works!!! Thank you!!!
Thanks, solved the problem for me too!
Worked for me. Thank you. A lifesaver. I had changed the application style to Chameleon - I won’t be doing that again!
love you