From kde-frameworks-devel  Tue Aug 19 19:48:04 2014
From: David Faure <faure () kde ! org>
Date: Tue, 19 Aug 2014 19:48:04 +0000
To: kde-frameworks-devel
Subject: Re: What to do with autostart scripts? (kinit / ksmserver problem)
Message-Id: <2538376.Xod61RG0Ku () asterix>
X-MARC-Message: https://marc.info/?l=kde-frameworks-devel&m=140847770127336

On Wednesday 09 July 2014 14:24:37 Luca Beltrame wrote:
> Hello,
> 
> commit f913e251fe66e22606c380a8cc0ddc8c69e3c07d in plasma-workspace removed
> autostart support in ksmserver because it caused .desktop files to be
> autostarted twice (one for kinit, and one for ksmserver).
> 
> I just noticed that it causes a regression in behavior from 4.x times, as
> user scripts (like adding ssh-agents etc.) are no longer run (because kinit
> only runs .desktop files).
> 
> So, this needs to be either communicated to the users or handled differently
> (yes, I don't want to wade through possible complaints in the forums ;)
> 
> My high (uniformed) level opinion on the possible scenarios:
> 
> - Re-enable autostart for everything but desktop files in ksmserver;
> - Add support for scripts in kinit (does it even make sense?);
> - Drop autostart scripts, tell users to make .desktop files
> 
> What do the gurus say on this?

I'd pick option 1 - do it all in ksmserver.

-- 
David Faure, faure@kde.org, http://www.davidfaure.fr
Working on KDE Frameworks 5

_______________________________________________
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel