Hello,

We're seeing lots of kdesktop_lock processes left lying around after users have logged out. With the number of users (100+ on some of our systems) and uptimes in years, the process table is going to end up full of these :-(

If one does an strace on the process it terminates but not until then.

Here's a (partial) pstree of a user with a three hanging kdesktop_lock processes:

dbus-daemon(19522) dbus-launch(19521) dcopserver(19574) kaccess(19656) kded(19578) kdeinit(19588)-+-kio_file(8614) |-klauncher(19591) |-konqueror(20688) `-kwin(19633) kdesktop(19637)---kdesktop_lock(29060) kdesktop_lock(20636) kdesktop_lock(22549) kdesktop_lock(22120) klipper(19671) kmix(19674) knotify(19667) korgac(19676) krandrtray(19661) kicker(19643) ksmserver(19626) startkde(19416)-+-gpg-agent(19518) |-kwrapper(19624) `-ssh-agent(19517)

The 'spurious' kdesktop_locks end up with init as the PPID:

F S UID PID PPID PGID C PRI NI ADDR SZ WCHAN TTY TIME CMD 0 S 1051 22549 1 22482 0 80 0 - 7739 - ? 00:00:00 kdesktop_lock

Process 22482 (the PGID) doesn't exist.

When I do an strace on PID 20636 and I get:

Process 20636 attached - interrupt to quit --- SIGHUP (Hangup) @ 0 (0) --- --- SIGTERM (Terminated) @ 0 (0) --- munmap(0xb5b70000, 172873) = 0 gettimeofday({1423135382, 387694}, NULL) = 0 gettimeofday({1423135382, 387815}, NULL) = 0 exit_group(1) = ?

and the kdesktop_lock process is gone.

The version is:

Qt: 3.3.8d KDE: 3.5.13.2 KDesktop Locker: 2.1

all running on Debian Wheezy.

Any suggestions as to how I stop this behaviour?

TIA.