Start kde, and run htop. You'll see several zombie processess.
Created attachment 617 [details] Patch for Xsession to avoid leaving zombie processes
Severity: normal => minor
I can't reproduce this issue, after login I I don't have any ck-launch-session processes running.
My mistake, it's ck-xinit-session. On my i586 system, running kde, htop sorted by pid shows ... 25728 dave 20 0 3892 1612 692 S 0.0 0.1 0:01.83 /usr/bin/dbus-daemon --fork --print-pid 5 --print-addr 25731 dave 20 0 0 0 0 Z 0.0 0.0 0:00.00 25735 dave 20 0 0 0 0 Z 0.0 0.0 0:00.00 25738 dave 20 0 0 0 0 Z 0.0 0.0 0:00.00 25740 dave 20 0 0 0 0 Z 0.0 0.0 0:00.00 25742 dave 20 0 0 0 0 Z 0.0 0.0 0:00.00 25745 dave 20 0 0 0 0 Z 0.0 0.0 0:00.00 25747 dave 20 0 0 0 0 Z 0.0 0.0 0:00.00 25750 dave 20 0 0 0 0 Z 0.0 0.0 0:00.00 25753 dave 20 0 0 0 0 Z 0.0 0.0 0:00.00 25789 dave 20 0 17120 2760 2108 S 0.0 0.1 0:00.00 s2u --daemon=yes $ grep Name /proc/2574*/status /proc/25740/status:Name: ck-xinit-sessio /proc/25742/status:Name: ck-xinit-sessio /proc/25745/status:Name: ck-xinit-sessio /proc/25747/status:Name: ck-xinit-sessio When I use the patched /etc/X11/Xsession, the zombie processes don't exist.
I don't see any ck-* processes, either active or zombie ones. How are you starting X? which DM? anything customised/special in your setup?
I boot to run level 3, then use "startx" which starts kde4. This is a clean install of Mageia 1, with only kde4 available as a dm. During the actual install I selected custom packaging, console and configuration tools only. After reboot, installed task-kde4. Minimal customization since install. Mostly testing new backports or updates.
Summary: There are several ck-launch-session zombie processes running when using kde. => There are several ck-xinit-session zombie processes running when using kde.
Hello, is this bug still valid ?
Yes. From htop ... 22402 dave 20 0 5868 1272 1048 S 0.0 0.1 0:00.04 | | `- /bin/sh /usr/bin/startkde 22611 dave 20 0 1844 224 180 S 0.0 0.0 0:00.00 | | | `- kwrapper4 ksmserver 22301 dave 20 0 0 0 0 Z 0.0 0.0 0:00.00 | | `- 22298 dave 20 0 0 0 0 Z 0.0 0.0 0:00.00 | | `- 22296 dave 20 0 0 0 0 Z 0.0 0.0 0:00.00 | | `- 22293 dave 20 0 0 0 0 Z 0.0 0.0 0:00.00 | | `- 22290 dave 20 0 0 0 0 Z 0.0 0.0 0:00.00 | | `- 22288 dave 20 0 0 0 0 Z 0.0 0.0 0:00.00 | | `- 22285 dave 20 0 0 0 0 Z 0.0 0.0 0:00.00 | | `- 22282 dave 20 0 0 0 0 Z 0.0 0.0 0:00.00 | | `- 22278 dave 20 0 0 0 0 Z 0.0 0.0 0:00.00 | | `- 22275 dave 20 0 0 0 0 Z 0.0 0.0 0:00.00 | | `- 22273 dave 20 0 0 0 0 Z 0.0 0.0 0:00.00 | | `- 22237 root 19 -1 68860 25612 3104 S 0.0 1.2 38:33.23 | `- /etc/X11/X :0 -auth /home/dave/.s $ grep Name /proc/22275/status Name: ck-xinit-sessio
@ Dave Did you check whether the problem occurs in current cauldron, too? I didn't try to reproduce the bug (I don't have it when booting straight into RL5, and I can't reboot into RL3 and do startx now, if I remember I'll try that later - my installation isn't similar to yours, btw)
CC: (none) => marja11, thierry.vignaud
Doesn't happen in current cauldron
maybe systemd is helping reaping session processes...
CC: (none) => mageia
I don't think systemd is responsible for reaping processes here.... I can be configured to kill all processes started in a session at logout but we don't enable that option AFAIK. I'd say that the KDE xsession script simply no longer calls ck-xinit-session as it's probably handled internally in kde... (that's my guess) I presume your user account still shows up in ck-list-sessions after logging in? (FYI console kit will die in the (likely) mga3 timeframe)
(In reply to comment #11) > I don't think systemd is responsible for reaping processes here.... I can be > configured to kill all processes started in a session at logout but we don't > enable that option AFAIK. > > I'd say that the KDE xsession script simply no longer calls ck-xinit-session as > it's probably handled internally in kde... (that's my guess) > > I presume your user account still shows up in ck-list-sessions after logging > in? > > (FYI console kit will die in the (likely) mga3 timeframe) @ Dave Did you see that question? Since console kit will likely die.... can you live with a wontfix?
Keywords: (none) => NEEDINFO
Sorry, I had missed that one. Yes the ck-list-sessions does show the account after I login in cauldron. I'll go ahead and close this as wont fix. Although the fix is very easy, it's also a very minor issue. The reason I originally opened it, is that the zombie processes were in a list of items that caused one person to describe Mageia 1 as unpolished. Once I tracked down the cause, and fix, I thought it best to open this report.
Status: NEW => RESOLVEDResolution: (none) => WONTFIX