Package: vtwm Version: 5.4.7-2.2+b1 Severity: normal File: /usr/bin/vtwm If vtwm is sent a SIGTERM signal then goes into a hard loop 100% CPU with an apparent GrabServer in force, thereby locking the screen.
Under gdb it looks like something in libX11, and/or libxcb which libX11 uses, doesn't like the cleanups run by vtwm's Done(). I don't know if a signal handler like Done() is allowed to interrupt ReadEvent() and do things like XGetGeometry() per vtwm's RestoreWithdrawnLocation(). I presume it worked once or it wouldn't have been written that way. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-486 Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages vtwm depends on: ii libc6 2.13-10 ii libice6 2:1.0.8-2 ii librplay3 3.3.2-14 ii libsm6 2:1.2.1-2 ii libx11-6 2:1.5.0-1 ii libxext6 2:1.3.1-2 ii libxmu6 2:1.1.1-1 ii libxpm4 1:3.5.10-1 ii libxt6 1:1.1.3-1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
