Message: previous - next
Month: February 2014

Re: [trinity-devel] Notes to commit 77aed4a4

From: Darrell <darrella@...>
Date: Mon, 24 Feb 2014 21:07:38 -0600
> I have no objections to killing gamin_server. However, killing kdesktop_lock 
> for active session causes the user logs off - it's not very good. What is the 
> effect of kills dcopserver for active applications I have not tested it.

I am not following your thinking. The new snippet only ensures kdesktop_lock for $USER is not running. Nobody else is affected.

In the case of multiple logins by the same user, I will run some tests.

> Regarding commit 6a571749 / 44b8d19c, I rather surprised that this had an 
> influence. I assumed that the updates is applied only on the earlier version 
> of the configuration, and it will not affect the fresh configuration.

This was strange to me too. The script was supposed to run only against existing profiles and not against new/fresh profiles. For many years going way back to KDE 3.5.0 I have been confused by this behavior. The script was always flawed and always conflicted with the defaults. Now I know why. Oh well, problem solved --- almost 10 years later.