Charles Hines wrote:
>
> >>>>> "Dan" == Dan Calle <dcalle_at_falcon.gu.sbc.edu> writes:
>
[question about libfvwm2.a]
>
> Basically (it's used to link fvwm itself too). It really doesn't need
> to be installed, although I believe it currently is installed.
Actually the default is not to install it - which I had been following
blindly since I didn't know what it was.
[snip]
> Dan> xlock -mode flame has started dying after a few minutes of running.
> Dan> The error is:
>
> Dan> /bin/sh: 1416 Floating exception
>
[snip]
>
> Actually, I think this is a bug with xlock. Do you see the same
> problems if you run xlock by hand?
Yes.
> I've seen problems like this with xlock in various modes core
> dumping (or locking up the machine entirely) on PowerPC based
> machines, but haven't had a chance to investigate yet.
I had too, but as I said, only with galaxy mode and never this quickly
- also I don't think it was the same error. I haven't updated xlock
in over a year so if this new error is caused a bug in xlock, then
somehow it wasn't triggered by 1.24r.
[snip]
One more thing, which I think I posted a long time ago but isn't in
BUGS or TO-DO, is that when I do something that closes a window (hit
return in a dialog box, click on a close or cancel button, whatever),
often the window manager gets "stuck" with the filled-circle cursor
and nothing responds (keystrokes, edgescroll, whatever) until I click
somewhere to "unstick" it.
--
Dan Calle SysAdmin and Research Assistant
Physics Department, Sweet Briar College
Email: calle96_at_sbc.edu Talk/Finger: dcalle_at_lucifer.gu.sbc.edu
Web Page: http://csugrad.cs.vt.edu/~dcalle/ Finger for PGP key.
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Mon Jul 15 1996 - 15:35:41 BST