153582 – kde processes do not exit after application termination

Bug 153582 - kde processes do not exit after application termination

Summary: kde processes do not exit after application termination

Status:	RESOLVED WORKSFORME

Alias:	None

Product:	kde
Classification:	I don't know
Component:	general (show other bugs)
Version:	unspecified
Platform:	Compiled Sources Linux

Importance:	NOR normal
Target Milestone:	---
Assignee:	Unassigned bugs mailing-list

URL:
Keywords:	needs_verification

Depends on:
Blocks:

Reported:	2007-12-06 20:56 UTC by kavol
Modified:	2020-10-29 04:33 UTC (History)
CC List:	4 users (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 kavol 2007-12-06 20:56:33 UTC

Version:            (using KDE Devel)
Installed from:    Compiled sources
Compiler:          gcc version 4.1.2 (Gentoo 4.1.2 p1.0.1) 
OS:                Linux

when running a single application - konqueror in my testcase - some necessary KDE stuff is run on the application startup

however, these processes keep running long after the application is closed (I closed konqueror right after starting it) - see below

kika@kika ~ $ date
Čt pro  6 20:34:42 CET 2007
kika@kika ~ $ ps -ef | grep kika
kika      6588  5919  0 19:10 pts/8    00:00:00 su - kika
kika      6631  6588  0 19:10 pts/8    00:00:00 -su
kika      6740     1  0 19:11 pts/8    00:00:00 dbus-launch --autolaunch fe04eb11720411ca689a520045b5f200 --binary-syntax
kika      6741     1  0 19:11 ?        00:00:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
kika      6752     1  0 19:11 ?        00:00:00 kdeinit4: kdeinit4 Running...
kika      6754  6752  0 19:11 ?        00:00:00 klauncher
kika      6765     1  0 19:11 ?        00:00:00 kded4
kika      6769     1  0 19:11 ?        00:00:00 /usr/libexec/gam_server
kika      6843  6631  0 20:34 pts/8    00:00:00 ps -ef
kika      6844  6631  0 20:34 pts/8    00:00:00 grep --colour=auto kika

they do not disappear even after completely logging out the user:

kika home # date
Čt pro  6 20:52:27 CET 2007
kika home # ps -ef | grep kika
kika      6740     1  0 19:11 ?        00:00:00 dbus-launch --autolaunch fe04eb11720411ca689a520045b5f200 --binary-syntax
kika      6741     1  0 19:11 ?        00:00:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
kika      6752     1  0 19:11 ?        00:00:00 kdeinit4: kdeinit4 Running...
kika      6754  6752  0 19:11 ?        00:00:00 klauncher
kika      6765     1  0 19:11 ?        00:00:00 kded4
kika      6769     1  0 19:11 ?        00:00:00 /usr/libexec/gam_server
root     15569 19785  0 20:52 pts/5    00:00:00 grep --colour=auto kika

I guess it is intended to let them run for some time to speed-up the next KDE application startup, but tenths of seconds, minutes at most, would be more realistic - not hours or "forever"

I have found one similar case, bug 82998, but I guess it has nothing common from the system point of view

Comment 1 Médéric Boquien 2008-11-08 22:16:53 UTC

Hello,

This problem should have been fixed some time ago. Can you try with the latest KDE version and report if this bug is still present for you?

Thanks.

Comment 2 kavol 2008-11-24 16:08:13 UTC

(In reply to comment #1)
> This problem should have been fixed some time ago. Can you try with the
> latest KDE version and report if this bug is still present for you?

I have some troubles compiling and running the newer version

I'll report back ASAP (let's say Dec 7 at latest)

Comment 3 FiNeX 2008-11-24 16:55:14 UTC

Many thanks Kavol, we'll wait your feedback :-)

Comment 4 kavol 2008-12-06 18:43:10 UTC

unfortunately, I still observe this behaviour with KDE 4.1.80

I started the test logged in as user "test" with no processes belonging to the user "kavol" running:

test@kika ~ $ date; ps -ef | grep kavol                                       
So pro  6 17:43:15 CET 2008                                                   
test      8436  8085  0 17:43 pts/0    00:00:00 grep --colour=auto kavol

in another konsole tab, I used su to become user "kavol":

test@kika ~ $ date; ps -ef | grep kavol
So pro  6 17:43:24 CET 2008                                             
kavol     8437  8308  0 17:43 pts/2    00:00:00 su - kavol
kavol     8441  8437  3 17:43 pts/2    00:00:00 -su
test      8448  8085  0 17:43 pts/0    00:00:00 grep --colour=auto kavol

as user "kavol", I launched konqueror:

test@kika ~ $ date; ps -ef | grep kavol
So pro  6 17:43:49 CET 2008                                             
kavol     8437  8308  0 17:43 pts/2    00:00:00 su - kavol
kavol     8441  8437  0 17:43 pts/2    00:00:00 -su
kavol     8449  8441 17 17:43 pts/2    00:00:03 konqueror
kavol     8453     1  0 17:43 pts/2    00:00:00 dbus-launch --autolaunch fe04eb11720411ca689a520045b5f221 --binary-syntax --close-stderr
kavol     8454     1  0 17:43 ?        00:00:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
kavol     8457     1  1 17:43 ?        00:00:00 kdeinit4: kdeinit4 Running...
kavol     8458  8457  0 17:43 ?        00:00:00 klauncher
kavol     8461     1  5 17:43 ?        00:00:00 kded4
kavol     8465     1  0 17:43 ?        00:00:00 /usr/libexec/gam_server
kavol     8469  8457  0 17:43 ?        00:00:00 kdeinit4: kio_file [kdeinit] file local:/tmp/ksocket-kavol/klauncherMT8458.slave-socket local:/tmp/ksocket-kavol/konquerorab8449.slave-socket
kavol     8470  8457  0 17:43 ?        00:00:00 kdeinit4: kio_file [kdeinit] file local:/tmp/ksocket-kavol/klauncherMT8458.slave-socket local:/tmp/ksocket-kavol/konquerorDs8449.slave-socket
kavol     8472  8457  0 17:43 ?        00:00:00 kdeinit4: kio_file [kdeinit] file local:/tmp/ksocket-kavol/klauncherMT8458.slave-socket local:/tmp/ksocket-kavol/konquerorvr8449.slave-socket
kavol     8474  8457  0 17:43 ?        00:00:00 kdeinit4: kio_file [kdeinit] file local:/tmp/ksocket-kavol/klauncherMT8458.slave-socket local:/tmp/ksocket-kavol/konquerorlx8449.slave-socket
test      8479  8085  0 17:43 pts/0    00:00:00 grep --colour=auto kavol

then I closed the konqueror window:

test@kika ~ $ date; ps -ef | grep kavol                                 
So pro  6 17:44:06 CET 2008                                             
kavol     8437  8308  0 17:43 pts/2    00:00:00 su - kavol
kavol     8441  8437  0 17:43 pts/2    00:00:00 -su
kavol     8453     1  0 17:43 pts/2    00:00:00 dbus-launch --autolaunch fe04eb11720411ca689a520045b5f221 --binary-syntax --close-stderr
kavol     8454     1  0 17:43 ?        00:00:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
kavol     8457     1  0 17:43 ?        00:00:00 kdeinit4: kdeinit4 Running...
kavol     8458  8457  0 17:43 ?        00:00:00 klauncher
kavol     8461     1  2 17:43 ?        00:00:00 kded4
kavol     8465     1  0 17:43 ?        00:00:00 /usr/libexec/gam_server
kavol     8469  8457  0 17:43 ?        00:00:00 kdeinit4: kio_file [kdeinit] file local:/tmp/ksocket-kavol/klauncherMT8458.slave-socket local:/tmp/ksocket-kavol/konquerorab8449.slave-socket
kavol     8470  8457  0 17:43 ?        00:00:00 kdeinit4: kio_file [kdeinit] file local:/tmp/ksocket-kavol/klauncherMT8458.slave-socket local:/tmp/ksocket-kavol/konquerorDs8449.slave-socket
kavol     8472  8457  0 17:43 ?        00:00:00 kdeinit4: kio_file [kdeinit] file local:/tmp/ksocket-kavol/klauncherMT8458.slave-socket local:/tmp/ksocket-kavol/konquerorvr8449.slave-socket
kavol     8474  8457  0 17:43 ?        00:00:00 kdeinit4: kio_file [kdeinit] file local:/tmp/ksocket-kavol/klauncherMT8458.slave-socket local:/tmp/ksocket-kavol/konquerorlx8449.slave-socket
test      8482  8085  0 17:44 pts/0    00:00:00 grep --colour=auto kavol

then I logged out user "kavol":

test@kika ~ $ date; ps -ef | grep kavol
So pro  6 17:44:46 CET 2008
kavol     8453     1  0 17:43 pts/2    00:00:00 dbus-launch --autolaunch fe04eb11720411ca689a520045b5f221 --binary-syntax --close-stderr
kavol     8454     1  0 17:43 ?        00:00:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
kavol     8457     1  0 17:43 ?        00:00:00 kdeinit4: kdeinit4 Running...
kavol     8458  8457  0 17:43 ?        00:00:00 klauncher
kavol     8461     1  0 17:43 ?        00:00:00 kded4
kavol     8465     1  0 17:43 ?        00:00:00 /usr/libexec/gam_server
kavol     8469  8457  0 17:43 ?        00:00:00 kdeinit4: kio_file [kdeinit] file local:/tmp/ksocket-kavol/klauncherMT8458.slave-socket local:/tmp/ksocket-kavol/konquerorab8449.slave-socket
test      8486  8085  0 17:44 pts/0    00:00:00 grep --colour=auto kavol

after some minutes, the processes are still running:

test@kika ~ $ date; ps -ef | grep kavol
So pro  6 17:47:01 CET 2008
kavol     8453     1  0 17:43 pts/2    00:00:00 dbus-launch --autolaunch fe04eb11720411ca689a520045b5f221 --binary-syntax --close-stderr
kavol     8454     1  0 17:43 ?        00:00:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
kavol     8457     1  0 17:43 ?        00:00:00 kdeinit4: kdeinit4 Running...
kavol     8458  8457  0 17:43 ?        00:00:00 klauncher
kavol     8461     1  0 17:43 ?        00:00:00 kded4
kavol     8465     1  0 17:43 ?        00:00:00 /usr/libexec/gam_server
kavol     8469  8457  0 17:43 ?        00:00:00 kdeinit4: kio_file [kdeinit] file local:/tmp/ksocket-kavol/klauncherMT8458.slave-socket local:/tmp/ksocket-kavol/konquerorab8449.slave-socket
test      8494  8085  0 17:47 pts/0    00:00:00 grep --colour=auto kavol

and even after 45 minutes ...

test@kika ~ $ date; ps -ef | grep kavol
So pro  6 18:30:00 CET 2008
kavol     8453     1  0 17:43 pts/2    00:00:00 dbus-launch --autolaunch fe04eb11720411ca689a520045b5f221 --binary-syntax --close-stderr
kavol     8454     1  0 17:43 ?        00:00:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
kavol     8457     1  0 17:43 ?        00:00:00 kdeinit4: kdeinit4 Running...
kavol     8458  8457  0 17:43 ?        00:00:00 klauncher
kavol     8461     1  0 17:43 ?        00:00:00 kded4
kavol     8465     1  0 17:43 ?        00:00:00 /usr/libexec/gam_server
kavol     8469  8457  0 17:43 ?        00:00:00 kdeinit4: kio_file [kdeinit] file local:/tmp/ksocket-kavol/klauncherMT8458.slave-socket local:/tmp/ksocket-kavol/konquerorab8449.slave-socket
test      8675  8085  0 18:30 pts/0    00:00:00 grep --colour=auto kavol


p.s. and after logging out the user "test", akonadi keeps running ...

kavol@kika ~ $ ps -ef | grep test
test      8021     1  0 17:09 ?        00:00:00 /usr/bin/akonadi_control
test      8023  8021  0 17:09 ?        00:00:00 akonadiserver
test      8025  8023  0 17:09 ?        00:00:13 /usr/sbin/mysqld --defaults-file=/home/test/.local/share/akonadi//mysql.conf --datadir=/home/test/.local/share/akonadi/db_data/ --socket=/home/test/.local/share/akonadi/db_misc/mysql.socket
kavol     9063  8999  0 18:41 pts/0    00:00:00 grep --colour=auto test

Comment 5 Dario Andres 2009-05-01 14:16:03 UTC

Any news on this ?
Thanks

Comment 6 kavol 2009-05-11 13:40:55 UTC

(In reply to comment #5)
> Any news on this ?
> Thanks

I tried to ssh into a system with KDE 4.3 Beta1 (4.2.85) and run kmail, see below:

pes@jarmilka ~ $ date
Po kvě 11 13:18:38 CEST 2009
pes@jarmilka ~ $ ps -ef | grep pes
root     19465  3465  0 13:18 ?        00:00:00 sshd: pes [priv]
pes      19470 19465  0 13:18 ?        00:00:00 sshd: pes@pts/5
pes      19472 19470  0 13:18 pts/5    00:00:00 -bash
pes      19480 19472  0 13:18 pts/5    00:00:00 ps -ef
pes      19481 19472  0 13:18 pts/5    00:00:00 grep --colour=auto pes
pes@jarmilka ~ $ kmail

[lots of messagess cut out]

kmail(19489) KMMainWin::~KMMainWin: Closing last KMMainWin: stopping mail check
kmail(19489) KMail::PopAccount::slotAbortRequested:
kmail(19489) KMail::PopAccount::slotAbortRequested:
kmail(19489)/kmail (storage internals) KMFolderMaildir::reallyDoClose: fclose(mIndexStream =  0x25188a0 )
kmail(19489) KMail::Vacation::~Vacation: ~Vacation()
kmail(19489)/kmail (storage internals) KMFolderMaildir::reallyDoClose: fclose(mIndexStream =  0x1ef8710 )
kmail(19489)/kmail (storage internals) KMFolderMaildir::reallyDoClose: fclose(mIndexStream =  0x1ef3100 )
kmail(19489)/kmail (storage internals) KMFolderMaildir::reallyDoClose: fclose(mIndexStream =  0x1eb4370 )
kmail(19489) KMKernel::~KMKernel:
kmail(19489) Sonnet::Loader::~Loader: Removing loader :  Sonnet::Loader(0x1e92830)

pes@jarmilka ~ $ date
Po kvě 11 13:22:19 CEST 2009
pes@jarmilka ~ $ ps -ef | grep pes
root     19465  3465  0 13:18 ?        00:00:00 sshd: pes [priv]
pes      19470 19465  0 13:18 ?        00:00:00 sshd: pes@pts/5
pes      19472 19470  0 13:18 pts/5    00:00:00 -bash
pes      19487     1  0 13:19 pts/5    00:00:00 dbus-launch --autolaunch d8dfff42a56f1dc69676540045b69301 --binary-syntax --close-stderr
pes      19488     1  0 13:19 ?        00:00:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
pes      19494     1  0 13:19 ?        00:00:00 kdeinit4: kdeinit4 Running...
pes      19495 19494  0 13:19 ?        00:00:00 klauncher --fd=8
pes      19498     1  0 13:19 ?        00:00:00 kded4
pes      19506 19494  0 13:19 ?        00:00:00 kdeinit4: kio_pop3 [kdeinit] pop3 local:/tmp/ksocket-pes/klauncherT19495.slave-socket local:/tmp/ksocket-pes/kmailV19489.slave-socket
pes      19507 19494  0 13:19 ?        00:00:00 kdeinit4: kio_pop3 [kdeinit] pop3s local:/tmp/ksocket-pes/klauncherT19495.slave-socket local:/tmp/ksocket-pes/kmailA19489.slave-socket
pes      19508 19494  0 13:19 ?        00:00:00 kdeinit4: kio_file [kdeinit] file local:/tmp/ksocket-pes/klauncherT19495.slave-socket local:/tmp/ksocket-pes/kmailI19489.slave-socket
pes      19509 19494  0 13:19 ?        00:00:00 kdeinit4: kio_file [kdeinit] file local:/tmp/ksocket-pes/klauncherT19495.slave-socket local:/tmp/ksocket-pes/kmailR19489.slave-socket
pes      19514 19494  0 13:19 ?        00:00:00 kdeinit4: kio_file [kdeinit] file local:/tmp/ksocket-pes/klauncherT19495.slave-socket local:/tmp/ksocket-pes/kmaili19489.slave-socket
pes      19515 19494  0 13:19 ?        00:00:00 kdeinit4: kio_file [kdeinit] file local:/tmp/ksocket-pes/klauncherT19495.slave-socket local:/tmp/ksocket-pes/kmailN19489.slave-socket
pes      19532 19472  0 13:22 pts/5    00:00:00 ps -ef
pes      19533 19472  0 13:22 pts/5    00:00:00 grep --colour=auto pes

pes@jarmilka ~ $ date
Po kvě 11 13:31:01 CEST 2009
pes@jarmilka ~ $ ps -ef | grep pes
root     19465  3465  0 13:18 ?        00:00:00 sshd: pes [priv]
pes      19470 19465  0 13:18 ?        00:00:00 sshd: pes@pts/5
pes      19472 19470  0 13:18 pts/5    00:00:00 -bash
pes      19487     1  0 13:19 pts/5    00:00:00 dbus-launch --autolaunch d8dfff42a56f1dc69676540045b69301 --binary-syntax --close-stderr
pes      19488     1  0 13:19 ?        00:00:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
pes      19494     1  0 13:19 ?        00:00:00 kdeinit4: kdeinit4 Running...
pes      19495 19494  0 13:19 ?        00:00:00 klauncher --fd=8
pes      19498     1  0 13:19 ?        00:00:00 kded4
pes      19515 19494  0 13:19 ?        00:00:00 kdeinit4: kio_file [kdeinit] file local:/tmp/ksocket-pes/klauncherT19495.slave-socket local:/tmp/ksocket-pes/kmailN19489.slave-socket
pes      19579 19472  0 13:31 pts/5    00:00:00 ps -ef
pes      19580 19472  0 13:31 pts/5    00:00:00 grep --colour=auto pes



after trying to log out, the ssh session hangs, and from another terminal I can see processes still running:
jarmilka ~ # ps -ef | grep pes
root     19465  3465  0 13:18 ?        00:00:00 sshd: pes [priv]
pes      19470 19465  0 13:18 ?        00:00:00 sshd: pes@notty
pes      19487     1  0 13:19 ?        00:00:00 dbus-launch --autolaunch d8dfff42a56f1dc69676540045b69301 --binary-syntax --close-stderr
pes      19488     1  0 13:19 ?        00:00:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
pes      19494     1  0 13:19 ?        00:00:00 kdeinit4: kdeinit4 Running...
pes      19495 19494  0 13:19 ?        00:00:00 klauncher --fd=8
pes      19498     1  0 13:19 ?        00:00:00 kded4
pes      19515 19494  0 13:19 ?        00:00:00 kdeinit4: kio_file [kdeinit] file local:/tmp/ksocket-pes/klauncherT19495.slave-socket local:/tmp/ksocket-pes/kmailN19489.slave-socket
root     19588 15695  0 13:34 pts/0    00:00:00 grep --colour=auto pes

after killing the ssh session with Ctrl+C, the rest of processes belonging to that user disappears ... not nice if I'd like to use it in a script (not to talk about the wasted resources while no KDE application is running ...)

Comment 7 kavol 2009-05-11 13:43:14 UTC

... forgot to change status (hey, bugzilla should do that automatically if info is provided) ...

Comment 8 Nate Graham 2020-09-29 03:05:09 UTC

I don't suppose this is still happening in a recent version of Plasma 5, is it?

Comment 9 Bug Janitor Service 2020-10-14 04:33:16 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 10 Bug Janitor Service 2020-10-29 04:33:35 UTC

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!