"Faucett, John A" <fauc...@lanl.gov> writes: > When FVWM hangs on a Firefox page with an HTML <INPUT> widget (one must > actually enter text), the backtrace is: > > #0 0x00e66402 in __kernel_vsyscall () > #1 0x0067a7eb in poll () from /lib/libc.so.6 > #2 0x007b0aa9 in ?? () from /usr/lib/libX11.so.6 > #3 0x007b0e8f in _XRead () from /usr/lib/libX11.so.6 > #4 0x007b1854 in _XReply () from /usr/lib/libX11.so.6 > #5 0x007914a0 in XGetGeometry () from /usr/lib/libX11.so.6 > #6 0x0806c371 in HandlePropertyNotify (ea=0xbfdfceb4) at events.c:3314 > #7 0x0806b619 in dispatch_event (e=0xbfdfcee4) at events.c:4138 > #8 0x0806bcff in HandleEvents () at events.c:4182 > #9 0x0808d01a in main (argc=3, argv=0xbfdfd994) at fvwm.c:2591 > > I would guess that FVWM is trying to get geometry information from the X11 > server, which never returns. > > Does this necessarily mean that this is an X11 problem?
Any particular HTML or web page? I use Firefox with input widgets a lot. -- Dan Espen
