Bug 313976 - kdeinit4 --no-kded --suicide <program> leaves behind processes
Summary: kdeinit4 --no-kded --suicide <program> leaves behind processes
Status: RESOLVED WORKSFORME
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: kdeinit (show other bugs)
Version: 4.11.5
Platform: Other All
: NOR normal
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-27 14:10 UTC by Christoph Anton Mitterer
Modified: 2023-01-12 05:26 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Christoph Anton Mitterer 2013-01-27 14:10:59 UTC 
Hi.

I’d have expected that when running a KDE programm (without a normal KDE session) like that:
  kdeinit4 --no-fork --no-kded --suicide digikam & exit
or:
  kdeinit4 --no-kded --suicide digikam
no (KDE) processes are left behind when this program ends.

However I always have these:
5275 ?        S      0:00 kdeinit4: kdeinit4 Running...
5280 ?        S      0:00 kdeinit4: klauncher [kdeinit] --fd=7
left over.

Any ideas?


Cheers,
Chris.

Reproducible: Always
Comment 1 Andrew Crouthamel 2018-11-11 04:30:42 UTC 
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 2 Andrew Crouthamel 2018-11-21 04:40:30 UTC 
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Justin Zobel 2023-01-12 01:58:13 UTC 
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 4 Christoph Anton Mitterer 2023-01-12 05:26:36 UTC 
Well I couldn't really test it anymore, since even when starting digikam alone, there no longer seem to be any kdeinit4 processes.

So I guess this can be closed now.