Bit by bit my plasma profile is getting corrupted, so it is getting
allmost unusable by now.
I have been searching duckduckgo for ways to reset plasma to its
defaults, but nothing worked adequately so far.
I found an item in askubuntu about this, but in the discussion different opinions (and plasma versions) are given to remove this or that.

I checked my files and folders and found either the ones mentioned in the
item above, do not exist or one like kdeglobals exists more than once.

I also found the advice to change the Plasma theme, but that didn't
improve things either.

Anyone has a suggestion which really applies to the Mageia configs???

TIA

Herman Viaene

--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: Aioe.org NNTP Server (2:250/1@fidonet)

On Wed, 2 Sep 2020 11:51:06 +0000 (UTC), Herman wrote:

Bit by bit my plasma profile is getting corrupted, so it is getting
allmost unusable by now.
I have been searching duckduckgo for ways to reset plasma to its
defaults, but nothing worked adequately so far.
I found an item in askubuntu about this, but in the discussion different opinions (and plasma versions) are given to remove this or that.

I checked my files and folders and found either the ones mentioned in the item above, do not exist or one like kdeglobals exists more than once.

I also found the advice to change the Plasma theme, but that didn't
improve things either.

Years ago, kde3/4 I found changing theme can screw up the account more so.

Anyone has a suggestion which really applies to the Mageia configs???

Explicit instruction would depend on application(s) that are dinked up.

Making your type of cleanup can be problematic because you are logged
in and the "save desktop feature on logout" could just help you farther
into the ditch.

Your Plasma/kde apps store data/configuration in different locations.

General brute force reset is as follows:
log out of your account.
Use a test account, say, junk, to log in, click up a terminal,
su - root.
Or if you can, log straight into root.

You then cd to your screwed up account and use mv to save
..config, .cache, and .kde to something like
mv .kde .kde_bkup

Once you completed that, you logout of junk/root. and log into your account.

When you log into your account, it will recreate .config, .cache, and .kde

You then need to go through all desktop settings to set desired values.
I highly recommend UnChecking the Save Session upon Exit/Logout.

After making all desired desktop/kde settings, log out/in.

Now, you get to go back through your apps to change their
configuration settings.

After that you can move any application data from the _bkup directories into the new directory.

Never hurts to have a separate backup prior to this kind of
open heart surgery.


--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 2020-09-02, Herman <[email protected]d> wrote:

Bit by bit my plasma profile is getting corrupted, so it is getting
allmost unusable by now.

I think you need to give more detail. Is it your desktop that is
"getting corrupted"? What does getting corrupted mean? What more exactly
is the problem.

I have been searching duckduckgo for ways to reset plasma to its
defaults, but nothing worked adequately so far.

You could always erase .config (or rather move it away to
..config.Sep2-2020) and let plasma bring in a new one.
Or do that with .kde4

I found an item in askubuntu about this, but in the discussion different opinions (and plasma versions) are given to remove this or that.

I checked my files and folders and found either the ones mentioned in the item above, do not exist or one like kdeglobals exists more than once.

Since you do not tell us what "files or folders" you are talking about
it is really had to give advice.

I also found the advice to change the Plasma theme, but that didn't
improve things either.

Anyone has a suggestion which really applies to the Mageia configs???

The key suggestion is that you give us more information as what the
problem is.

TIA

Herman Viaene

--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On Wed, 02 Sep 2020 19:51:54 +0000, William Unruh wrote:

On 2020-09-02, Herman <[email protected]d> wrote:

Bit by bit my plasma profile is getting corrupted, so it is getting
allmost unusable by now.

I think you need to give more detail. Is it your desktop that is
"getting corrupted"? What does getting corrupted mean? What more exactly
is the problem.

To answer both of you in one go:
The desktop starts up and looks OK, but things like:
the clock does not advance unless I open or close some window
menu opens but most of the time I have to select some application twice
before it opens - and then it opens only once
I can right-click on the desktop and select "Leave", but it takes at
least one minute before any reaction shows, then I can shutdown.

Xfce works OK, so I presume there's nothing wrong with the underlying X- settings.

BUT

After I wrote the OP, I thought of Bit's well known advice tp try another user. That's one I made last week for another purpose and the same
problems appear there, so it seems system-wide rather then user-bound.
That's even worse!!!


Herman

I have been searching duckduckgo for ways to reset plasma to its
defaults, but nothing worked adequately so far.

You could always erase .config (or rather move it away to
.config.Sep2-2020) and let plasma bring in a new one.
Or do that with .kde4

I found an item in askubuntu about this, but in the discussion
different opinions (and plasma versions) are given to remove this or
that.

I checked my files and folders and found either the ones mentioned in
the item above, do not exist or one like kdeglobals exists more than
once.

Since you do not tell us what "files or folders" you are talking about
it is really had to give advice.

I also found the advice to change the Plasma theme, but that didn't
improve things either.

Anyone has a suggestion which really applies to the Mageia configs???

The key suggestion is that you give us more information as what the
problem is.

TIA

Herman Viaene

--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: Aioe.org NNTP Server (2:250/1@fidonet)

On Thu, 3 Sep 2020 08:36:52 +0000 (UTC), Herman wrote:

After I wrote the OP, I thought of Bit's well known advice tp try another user. That's one I made last week for another purpose and the same
problems appear there, so it seems system-wide rather then user-bound.
That's even worse!!!

Yeah, that does not look good at first glance.

I suggest wiping that test account and verify the problem is system wide.

Since I use junk as my test account, I would do:

su - root
rsync --delete -aAHSXxv /etc/skel/ /home/junk


--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On Thu, 03 Sep 2020 03:54:33 -0500, Bit Twister wrote:

On Thu, 3 Sep 2020 08:36:52 +0000 (UTC), Herman wrote:

After I wrote the OP, I thought of Bit's well known advice tp try
another user. That's one I made last week for another purpose and the
same problems appear there, so it seems system-wide rather then
user-bound. That's even worse!!!

Yeah, that does not look good at first glance.

I suggest wiping that test account and verify the problem is system
wide.

Since I use junk as my test account, I would do:

su - root rsync --delete -aAHSXxv /etc/skel/ /home/junk

Left the existing users as they are, created a brand new one, and got the
same problems.
Then something came to my mind: this is an NVidia machine, and it has
been running nouveau since some time ago there were problems with NVidia's driver.
But since then there have been (I think) at least two new kernels, so I
gave the NVidia driver another go. After reboot, there are much less
strange things happening. I'm not yet convinced it is 100% OK, but a lot better.

Tx for your effort.

Herman

--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: Aioe.org NNTP Server (2:250/1@fidonet)