Hello all,I started noticing this shortly after applying UP8. mate-settings-daemon has a severe memory leak - close to 1GB/hr. This renders the system almost unusable after a few hours. I can kill the process from Task Manager or terminal, but it comes back immediately and continues to leak memory.Here are some of the system specs:

Mine is doing this too...mate-settings-daemon is also using about 100% CPU (all of one core). It leaks memory as described. Killing it released the memory but the process respawns and starts leaking memory and using 100% CPU again. Does yours use 100% CPU too?

DarkNova wrote:Mine is doing this too...mate-settings-daemon is also using about 100% CPU (all of one core). It leaks memory as described. Killing it released the memory but the process respawns and starts leaking memory and using 100% CPU again. Does yours use 100% CPU too?

every second. I looked at the file /run/user/1000/dconf/user and it was set to have root permissions. I deleted the file, killed mate-settings-daemon, and now, when it respawned, it recreated that file as my user name, and now it doesn't seem to be using much CPU or memory. Not 100% sure it won't come back, or why it happened in the first place, but I'd be interested if you gave that a try and it fixed yours, it might give a clue to the MATE people.

I am also getting this issue after update 8 on my LMDE systemI did the "sudo apt-get remove --purge software-properties-gtk mint-debian-mirrors" before the upgrade and just did again and they are NOT installed.Also followed all the other pre-reqs before installing.

Have to do a kill -9 to stop it, but as in other posts, it respawns. System becomes unusable.

Also, my laptop (Lenovo T520) no longer hibernates when I close the lid. Just locks the screen. It does hibernate with the "hibernate" command, but seems a bit odd in it's resume - bit different than before the update 8I think, but will have to prove later, that the mate-settings-daemon issue occurs after resume from the command hibernation.

j1mw3b wrote:Did the Cinnamon guys do this to make us Mate users switch over???

The problem is not in mate-settings-daemon itself, it's a bug in systemd that sets the wrong permissions for /run/user/1000/dconf, as stated in the previous posts. This issue makes various apps crash or eat 100% CPU.The recent systemd updates should've fixed that. Make sure you've applied all the updates.

I had noted some other comments in other Google forums about disabling (dconf-editor) org.mate.settings-daemonplugins.keyboard (and a11y.keyboard) and that seemed to fix the mate-settings-daemon issue. I have reactivated them now and an now installing the latest updates - including systemd - so will see how that goes,

Bigger issue right now is why my lid close does not hibernate, but pm-hibernate works fine. I see "lid closed" in dmesg, but apparently something is not getting triggered by that event.

Also see there is a new /etc/init.d/acpi/acpi-support and acpi-fakekey that was not in my system before update 8.And a whole bunch of new files in /etc/acpi that was not there before.

Do the developers ever supply a more technical explanation of what and why things were changed?Having been a software developer, we didn't do this, but with open source, maybe???

I got that cpu hog / memory leak problem too / again: I installed some days ago a new machine with LMDE x64 Mate 2014-03RC (sorry, was impatient ) and pulled all the updates since — so it should be current, isn't it? I switched to systemd 204-5linuxmint1 by installing systemd-sysv (which removes sysvinit), then downgraded and pinned mate-power-manager to 1.6.2-1+lmde (see Clem ). But still /run/user/1000/dconf/user is owned by root so that many apps in the Mate Control Center do not work and eat 200% CPU and gigs of RAM until killed.

Hello,I have a problem with Deamon Mate Setting takes 6GB of resources or more, I do not think this is normal, so if you have a solution or tell me why it takes so many resources thank you to answer me, this process often does not respond not. I regularly kill this process