🚀 go-pugleaf

I get a very annoying problem with epoch once in a while.  I'm
wondering if anyone else has seen this behavior.

Every once in a while, I'll click on something in epoch and find that
I've accidentally entered infinite-beep-mode.  The message area
displays "marker does not point anywhere" and the keyboard beeps
forever.  Epoch is hung, and so is the keyboard, and the Xserver, and
life, the universe, and everything.  Well, the mouse still moves, but
focus no longer follows the mouse and clicks are ignored.  There is no
way to stop the beeping without logging in from another terminal and
killing processes.  Sometimes the beeping stops about a hundred beeps
after I've killed the offending epoch, sometimes I have to reboot.

As you might imagine, this is very embarassing during a demo I do for
VIPs which uses epoch.  "Oops, have to shut down the machine, that
happens sometimes."  Really professional.

The evidence makes me suspect that epoch has gone into some loop with
the server, generating errors that somehow generate new events.  Since
reading the mouse position can generate new events sometimes, I
suspect the loop is in that area.  Anyone else seen this behavior?


--
B<   Brian Kahn   blk@mitre.org   "may the farce be with you"