Review Request 118977: KSMServer: Do not autostart files

[Rohan Garg]

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/118977/#review61099
-----------------------------------------------------------


I applied it locally here and krunner still starts up twice.

- Rohan Garg


On June 27, 2014, 8:29 p.m., Vishesh Handa wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/118977/
> -----------------------------------------------------------
> 
> (Updated June 27, 2014, 8:29 p.m.)
> 
> 
> Review request for Plasma.
> 
> 
> Bugs: 335878
>     https://bugs.kde.org/show_bug.cgi?id=335878
> 
> 
> Repository: plasma-workspace
> 
> 
> Description
> -------
> 
>     KSMServer: Do not autostart files
> 
>     Currently KLauncher is responsible for starting all of the autostart
>     files. It intelligently starts only the files which should be started in
>     the KDE environment.
> 
>     Once this is done, KLauncher then decides to also start all the files
>     in the autostart folder, but does that without checking which should be
>     started. I'm not sure why both KSMServer and KLauncher are overlaping
>     and doing the same thing. But it seems that KLauncher is the correct
>     place to do this. Specially since ksmserver uses kioclient5 in order to
>     start the applications.
> 
>     BUG: 335878
> 
> 
> Diffs
> -----
> 
>   ksmserver/server.h 3d19118 
>   ksmserver/startup.cpp 11cc968 
> 
> Diff: https://git.reviewboard.kde.org/r/118977/diff/
> 
> 
> Testing
> -------
> 
> Applications are now only started once.
> 
> 
> Thanks,
> 
> Vishesh Handa
> 
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20140627/90aa988d/attachment-0001.html>