Once again, imsettings-daemon is getting started and sabotages my desktop. This is happening despite input methods being explicitly turned off in the capplet. Please, we cannot ship something that randomly takes over core infrastructure parts of the desktop and breaks them. Either make it stop or it needs to be nuked.
hmm, or maybe something else killed my settings daemon.
I'd like to clarify: either imsettings-applet or imsettings-xim is invoked anyway regardless of whether IM is turned off, to allow people to switch IM on XIM dynamically. so I'm afraid I don't think it's not a good report to blame it emotionally from the reason it's just there and without certain information. I'm not quite sure what happened there though, I'm keen to investigate that issue if it often happens for you and there are any steps to reproduce it. please let me know if any.
Yeah, sorry. This was a false alarm. I guess I was just not prepared for 3 or more im processes to run even if input methods are disabled.