ngraham added a comment.
In D22121#491723 <https://phabricator.kde.org/D22121#491723>, @msdobrescu wrote: > In D22121#491369 <https://phabricator.kde.org/D22121#491369>, @ngraham wrote: > > > Huh, in a VM everything works for me too. I wonder if there's some subtle issue with the fact that I'm running a custom-compiled Plasma at a different path on bare metal. > > > Hi, I have followed this one, the new version, step by step: https://community.kde.org/Get_Involved/development#Plasma > Before, some custom script was necessary, but did not work and all my crashes, I have experienced and told you about, were due to that. Could be some environment variable that pointed to something from the main install. > I recommend to perform a full cleanup, follow again the testing setup, rebuild all the deps (kdesrc-build plasma-desktop plasma-workspace plasma-framework plasma-nm plasma-pa plasma-thunderbolt plasma-vault plasma-workspace-wallpapers kdeplasma-addons kwin systemsettings kscreen breeze discover kinfocenter --include-dependencies ~ and maybe add ~ --refresh-build), then test and see if it works. This was the way I've got rid of the errors that should not come in the first place, before developing and correcting it for real. Yes, that's how I do it. In fact, I'm one who wrote that part of the documentation. :) REPOSITORY R120 Plasma Workspace REVISION DETAIL https://phabricator.kde.org/D22121 To: davidre, #plasma Cc: davidedmundson, msdobrescu, ngraham, filipf, plasma-devel, LeGast00n, jraleigh, fbampaloukas, GB_2, ragreen, Pitel, ZrenBot, himcesjf, lesliezhai, ali-mohamed, jensreuterberg, abetts, sebas, apol, mart
