[Bug 173633] New: launching a KDE 4 apps out of a KDE 4 session spawns lots of (useless?) processes

[fullmetalcoder]

http://bugs.kde.org/show_bug.cgi?id=173633

           Summary: launching a KDE 4 apps out of a KDE 4 session spawns
                    lots of (useless?) processes
           Product: kde
           Version: unspecified
          Platform: Compiled Sources
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: unassigned-bugs at kde.org
        ReportedBy: fullmetalcoder at hotmail.fr


Version:            (using Devel)
Compiler:          GCC 4.2.4 
OS:                Linux
Installed from:    Compiled sources

I have reported an issues about PowerDevil default behavior in another bug but
while I tested this issue and thanks to the explanation of a dev I discovered
that launching a KDE 4 app without actually starting a full session causes a
lot of daemons/services to be launched.

For instance I started Amarok from my command line (within a KDE 3 session) and
it caused kded, ksycoca, powerdevil (and probably other stuff as well but those
were easier to spot due to the way they flooded my command line or altered my
brightness settings (powerdevil)).

What's obviously wrong is that some daemons/services do NOT need to be launched
everytime a KDE 4 application is started. kded, ksycoca and some others make
sense but if things like powerdevil are automatically started out of a full
session then there are probably many others and this is just plain wrong for
two main reasons :
 * some of these may interact in unwanted ways with the running desktop
environment (as it happened for me with PowerDevil)
 * every such daemon/service it is an utter waste of system resources because
the launched application does not require it

My use case may not seem relevant but please consider that there are many
people that often use a couple of KDE 3 applications from another DE (Amarok
and K3B are good examples) and this behavior is likely to remain for their KDE
4 equivalent (and might even increase considering the opinion some long-time
KDE 3 users have about KDE 4).


-- 
Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.