Nicolas wrote: > I managed to reproduce the problem. buici-clock does some drawing in a > signal handler using some non-reentrant functions. > > I can see now that this is really similar to bug #696148, in every > trace, there is a function waiting on a condition which can never occurs > because a similar fonction was interrupted by the alarm signal. > > I have an idea for a simple fix for the startup case.
Yay! You fixed it. I have now installed the updated package from testing and it's all good now. Which means I can put the more pixelated swisswatch to rest. I also experienced the occasional freeze up described in bug #696148 if I left it running a month or more. After many years `xkill` is still my favourite program (although I miss the skull and crossbones cursor) - one less reason to use it now. For what it's worth, I had been messing around with `pgrep`, `xwininfo -root -tree`, and `wmctrl -l` and could see that the process existed, was known to X11, but not known to the window manager. I'm using Xfce and launching X11 with `startx`. I never got a chance to test it with Fluxbox WM on this machine but on another Xfce Trixie computer buici was working ok. many thanks, Hamish
