Created attachment 107025 [details] When I run the command for system settings in terminator Every time System Settings > Workspace Theme > Desktop Theme is opened, it immediately follows in a crash. On Arch KDE, used sudo pacman -S plasma to download. Actual Results: The entire System Settings application crashed. Expected Results: System Settings opens the Desktop Theme gui in the application. Build Date & Platform: KDE 5.10.4 (Kernel:4.12.3-1-ARCH) 64-bit Installed the Breeze theme. Ended up reinstalling Plasma with pacaur -S plasma. Bug still occurred. When I tried running the systemsettings5 application in the terminal... (see attachment) (Don't poke fun at my usr pls kthx)
When you get this crash, a crash dialog window should appear. Please add the backtrace from the "Developer Information" tab to this ticket. You might need to install 'gdb' before this works.
Created attachment 107040 [details] Backtrace from crash
(In reply to Christoph Feck from comment #1) > When you get this crash, a crash dialog window should appear. Please add the > backtrace from the "Developer Information" tab to this ticket. You might > need to install 'gdb' before this works. Sorry, I completley forgot about it :/ The bug reporter applet described it as a "useless" back trace, so I didn't think to include it. I apologize
Well, I should have read comment #0 a bit more properly... The error is: org.kde.kcoreaddons: Error loading plugin "kcm_desktoptheme" "The shared library was not found." This means there is a problem with your packages. Please report this to the bug tracker of your distribution.
(In reply to Christoph Feck from comment #4) > Well, I should have read comment #0 a bit more properly... > > The error is: > > org.kde.kcoreaddons: Error loading plugin "kcm_desktoptheme" "The shared > library was not found." > > This means there is a problem with your packages. Please report this to the > bug tracker of your distribution. Thanks :) I really dont see how the Arch repository could screw that up, but I'll take it to them. I'm just glad its not a bug with KDE its self!