On Tuesday 19 of November 2013 14:21:16 Marc Chamberlin wrote:
On 11/18/2013 07:03 PM, šumski wrote:
On Monday 18 of November 2013 10:21:04 Marc Chamberlin wrote:
Here is the contents of my activitymanagerrc file shown below. Unfortunately diff did not show any changes being made to the file after I made changes to the backgrounds and added a couple of widgets to one of my desktops.
Those kind of changes are not written to that file. Anyway, points to test: a) clean user
Thanks Sumski and Felix for your replies. Creating a clean user, setting up the desktops and widgets, rebooting works for that user. So it is something that is in my home directory, which as I mentioned is on its own partition and was mounted under openSuSE12.3. So the problem apparently is that there is something incompatible with KDE that was created in an earlier version. I dunno if it is worth it to try an pursue this problem to determine exactly what failed, but I am willing to help if there is a desire for me to do so. At least this should give me a path to get my system working again, I will just backup what is necessary, delete my user account and recreate/restore it.
OK, that leaves it to possible crash/KAMD race condition at logout/in. As settings are indeed saved, it rules out the permission problems.
b) "main user" + kquitapp plasma-desktop && kstart plasma-desktop after executing those changes
Doing this did restore my desktops OK, and I did not lose any of my widgets or desktop configurations. However I did get a whole lot of what appears to be error messages and warnings. I can post them if requested to do so... No need ;-) That's mostly just plasma being verbose :-)
c) chmod -x /usr/bin/kactivitymanagerd outside the session (note that would create vanilla setup, but just to see is the issue indeed with KAMD), login, try to change stuff, etc..
I am not sure what you mean by "outside the session" so did not try this. Thanks again for all the help! Marc... I mean when you're logged out, and without KDE session and any application running. (So, ideally, either on boot, before login, or, logging out, and doing suggested command)