For instance, if I move the theme Tenuto-Light in and out of the ~/.local/share/aurorea/themes folder, the theme (when it's in the folder) appears to cause instability. But it's not consistent. First try: Executable: systemsettings5 PID: 7946 Signal: Segmentation fault (11) Time: 7/11/15 12:29:45 Second try: Executable: systemsettings5 PID: 7955 Signal: Segmentation fault (11) Time: 7/11/15 12:31:14 Third try: Executable: systemsettings5 PID: 7977 Signal: Segmentation fault (11) Time: 7/11/15 12:32:01 Etc.. Reproducible: Sometimes Steps to Reproduce: 1.) Install Tenuto-Light (and possibly other themes.) 2.) Close System Settings 3.) Re-open System Settings ---> Application Style 4.) Choosing <Window Decorations> causes Segfault Actual Results: Segfault (see above) I notice that even after removing Tenuto-Light, the problem continues. I'm going to attach the offending collection for your experimentation..
I was going to attach the offending folder, but can't. Some combination of the following always produces a segfault: Air-black-remix-green Air-black-remix-red air-oxygen-color Evenos EvolvereLight EvolvereLightPureCircle Flatsquare-Amber Flatsquare-Blue Flatsquare-BlueGree Flatsquare-Cyan Flatsquare-DeepOrange Flatsquare-DeepPurple Flatsquare-Green Flatsquare-Indigo Flatsquare-LightBlue Flatsquare-LightGreen Flatsquare-Lime Flatsquare-Orange Flatsquare-Pink Flatsquare-Purple Flatsquare-Red Flatsquare-Teal Flatsquare-Yellow FormaN Freeze ghost-deco-2_2 perfection PlasmaNext-windowdecortion-ideas Seven-Blue simplicitytl Tenuto-Light-ActiveStrong yosiwhite yousiwhiteN The following does not: EvolvereLight EvolvereLightPureCircle Flatsquare-Amber Flatsquare-Blue Flatsquare-BlueGree Flatsquare-Cyan Flatsquare-DeepOrange Flatsquare-DeepPurple Flatsquare-Green Flatsquare-Indigo Flatsquare-LightBlue Flatsquare-LightGreen Flatsquare-Lime Flatsquare-Orange Flatsquare-Pink Flatsquare-Purple Flatsquare-Red Flatsquare-Teal Flatsquare-Yellow FormaN PlasmaNext-windowdecortion-ideas
One more comment, for what it's worth. With the combination of themes above, I can make systemsettings *always* segfault. Consistently.
I can confirm this behavior. I changed my window decorations to "dust", and now I cannot access this part of the system settings without it crashing. So, I am stuck with "dust" =( . I'm in kubuntu 15.04, so i think it is plasma 5.2 fwiw. As a side note, if anyone knows of a way to change this via a config file or something, please let me know. I would rather not be stuck with this window decoration.
> As a side note, if anyone knows of a way to change this via a config file or > something, please let me know. I would rather not be stuck with this window > decoration. My own method was to remove the contents of the ~/.local/share/aurorea/themes folder. I made a backup copy of it first, then deleted it, then restarted, then added the themes back one by one by copying them from the backup folder (obviously excluding the ones I thought were causing the trouble).
(In reply to PGillespie from comment #4) > > As a side note, if anyone knows of a way to change this via a config file or > > something, please let me know. I would rather not be stuck with this window > > decoration. > > My own method was to remove the contents of the > ~/.local/share/aurorea/themes folder. I made a backup copy of it first, then > deleted it, then restarted, then added the themes back one by one by copying > them from the backup folder (obviously excluding the ones I thought were > causing the trouble. Well, I did this, but it oddly has no effect. The dust theme is still set on the windows, and the system settings still crash when I get to the window decoration screen. This is actually weird because when I tried to just remove the dust folder (and not the whole aurorea folder), I could not even log in. Black screen with a cursor. I had to fix it with midnight commander in a tty. I also tried changing the .config/kwinrc file and point it to breeze, but this also gave me the black screen (I was really hoping that one would work).
Strange. Something doesn't add up. If you removed the theme, then where's it coming from? This is rapidly going beyond my pay scale. However, the first questions that would occur to me is this -- Was it a plasma theme? There are different "Dust" themes and some of them aren't intended to decorate KDE, let alone Plasma. Do you have any other DEs installed besides KDE? It doesn't make sense your install is still booting up Dust when you've "removed" it. As a friend of mine likes to say: You're wrong. It's as if you installed a Gnome theme and KDE is drawing the theme from some other Gnome directory -- but that's sheer speculation.
(In reply to PGillespie from comment #6) > Strange. Something doesn't add up. If you removed the theme, then where's it > coming from? > > This is rapidly going beyond my pay scale. However, the first questions that > would occur to me is this -- Was it a plasma theme? There are different > "Dust" themes and some of them aren't intended to decorate KDE, let alone > Plasma. Do you have any other DEs installed besides KDE? > > It doesn't make sense your install is still booting up Dust when you've > "removed" it. As a friend of mine likes to say: You're wrong. It's as if you > installed a Gnome theme and KDE is drawing the theme from some other Gnome > directory -- but that's sheer speculation. (sorry if i spammed, i tried to reply from my phone to no avail). I don't have any other desktop installed. I installed the dust theme via the get hot new stuff button in the system settings (stupid, stupid). But, I was thinking the same thing as you. It is as if the window decorations need to be refreshed or something.
okay, i did a big no-no and it worked for me. i started the system settings in sudo, and was able to change it (never do this, kids). Restarting the system and all is back to normal. I still had to remove the aurorea themes listed by going into the hot stuff button and "uninstalling them", even though I had already removed the directory. Strange, but problem solved kinda. Thank you!
*** This bug has been marked as a duplicate of bug 344278 ***