https://bugs.kde.org/show_bug.cgi?id=394360
Jiri Slaby <jirisl...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #112709|0 |1
is obsolete| |
--- Comment #5 from Jiri Slaby <jirisl...@gmail.com> ---
Created attachment 114320
--> https://bugs.kde.org/attachment.cgi?id=114320&action=edit
strace -f of kded5 (packed by xz due to size)
Now I reproduced even with strace capturing the process. (It still recurs and
is painful.)
13987 is kdeinit.
16233 is the pid of the setxkbmap process which became a zombie.
16213 is the last process which kdeinit called wait4 for. It is another
instance of setxkbmap:
> 16213 exit_group(0) = ?
> 16213 +++ exited with 0 +++
> 13987 --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=16213,
> si_uid=500, si_status=0, si_utime=0, si_stime=1} ---
> 13987 waitid(P_ALL, 0, {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=16213,
> si_uid=500, si_status=0, si_utime=0, si_stime=0}, WNOHANG|WEXITED|WNOWAIT,
> NULL) = 0
> 13987 wait4(16213, <unfinished ...>
> 13987 <... wait4 resumed> [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], WNOHANG,
> {ru_utime={tv_sec=0, tv_usec=2524}, ru_stime={tv_sec=0, tv_usec=10098}, ...})
> = 16213
setxkbmap is not the only unreaped process. I also saw zombie of xterm pinned
to kdeinit (opened via ctrl-alt-t which is a custom shortcut to run xterm).
--
You are receiving this mail because:
You are watching all bug changes.
