| Summary: | Autostarted applications are run twice | ||
|---|---|---|---|
| Product: | [Plasma] ksmserver | Reporter: | Antonio Rojas <arojas> |
| Component: | general | Assignee: | Vishesh Handa <me> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | bhush94, me, notmart, simonandric5 |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | http://commits.kde.org/plasma-workspace/f913e251fe66e22606c380a8cc0ddc8c69e3c07d | Version Fixed In: | |
|
Description
Antonio Rojas
2014-06-06 12:33:50 UTC
Git commit 68b27ba6abbce9c8f03a94a065c32d54b13a8c8c by Aleix Pol, on behalf of Vishesh Handa.
Committed on 02/07/2014 at 17:14.
Pushed by apol into branch 'master'.
KSMServer: Do not autostart files
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.
REVIEW: 118977
commit 9529b6d513b73d421c3ac7c81909bf638a4e5817
Author: Vishesh Handa <me@vhanda.in>
Date: Fri Jun 27 17:01:11 2014 +0200
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.
M +0 -2 ksmserver/server.h
M +3 -33 ksmserver/startup.cpp
http://commits.kde.org/plasma-workspace/68b27ba6abbce9c8f03a94a065c32d54b13a8c8c
Git commit 68b27ba6abbce9c8f03a94a065c32d54b13a8c8c by Aleix Pol, on behalf of Vishesh Handa.
Committed on 02/07/2014 at 17:14.
Pushed by apol into branch 'master'.
KSMServer: Do not autostart files
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.
REVIEW: 118977
commit 9529b6d513b73d421c3ac7c81909bf638a4e5817
Author: Vishesh Handa <me@vhanda.in>
Date: Fri Jun 27 17:01:11 2014 +0200
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.
M +0 -2 ksmserver/server.h
M +3 -33 ksmserver/startup.cpp
http://commits.kde.org/plasma-workspace/68b27ba6abbce9c8f03a94a065c32d54b13a8c8c
Git commit 68b27ba6abbce9c8f03a94a065c32d54b13a8c8c by Aleix Pol, on behalf of Vishesh Handa.
Committed on 02/07/2014 at 17:14.
Pushed by apol into branch 'master'.
KSMServer: Do not autostart files
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.
REVIEW: 118977
commit 9529b6d513b73d421c3ac7c81909bf638a4e5817
Author: Vishesh Handa <me@vhanda.in>
Date: Fri Jun 27 17:01:11 2014 +0200
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.
M +0 -2 ksmserver/server.h
M +3 -33 ksmserver/startup.cpp
http://commits.kde.org/plasma-workspace/68b27ba6abbce9c8f03a94a065c32d54b13a8c8c
This is still valid in a fresh git checkout (rev 9e761d3). Actually the patch doesn't seem to be applied? Git commit f913e251fe66e22606c380a8cc0ddc8c69e3c07d by Vishesh Handa. Committed on 03/07/2014 at 11:06. Pushed by vhanda into branch 'master'. 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. REVIEW: 118977 M +0 -2 ksmserver/server.h M +3 -33 ksmserver/startup.cpp http://commits.kde.org/plasma-workspace/f913e251fe66e22606c380a8cc0ddc8c69e3c07d |