First I have a question and then I'll get on with the bug report.
It's not in the FAQ so - what exactly is the purpose of libfvwm2.a?
Is it only for those who wish to write modules or what?
"Charles Hines" <chuck_hines_at_VNET.IBM.COM> wrote:
>
[snip]
> I'd like to make this the last beta before the first official
> release (2.1.0). So let me know what other problems you find with
> it so I can clean it up (especially build and doc problems). Bear
> in mind that I can't fix ALL of it's bugs, especially the one's I
> can't reproduce...
Background info:
I'm running Digital UNIX 3.2c on an AlphaStation and 3.0 on a DEC
3000/300LX Alpha. Both systems have X11R5 and the XPM libs. Fvwm was
compiled "out of the box" with xmkmf;make Makefiles;make;make install;
make install.man - all I changed in Fvwm.tmpl were the destination
directories for the install.
Bug 1:
This had appeared on the DEC 3000 since 2.0.42 but didn't show up on
the AlphaStation 'til 2.0.43. Often, edgescroll won't work. I'll
drag and drag and it won't switch pages. If I then hit Control-right,
it works fine, and thereafter edgescroll works normally. I'm not sure
if the problem stays fixed 'til I next log out and back in again
though. The relevant lines from my .fvwm2rc file are:
EdgeScroll 100 100
EdgeResistance 200 25
Key Left A C Scroll -100 0
Key Right A C Scroll +100 +0
Key Up A C Scroll +0 -100
Key Down A C Scroll +0 +100
Bug 2:
xlock -mode flame has started dying after a few minutes of running.
The error is:
/bin/sh: 1416 Floating exception
where the number is the PID of:
/bin/sh -c xlock -nolock -mode flame
Previously the only mode I'd ever had trouble with was "galaxy". I
don't know which of the last few versions this might have appeared in
because I don't run XLock that often. I can't really say for certain
that it's fvwm but I haven't changed anything else that would affect
it.
The line in my .fvwm2rc is:
+ "flame" Exec xlock -nolock -mode flame
I haven't tried this on the AlphaStation though.
Bug 3:
The bug I mentioned in another message in which one of my xterms
wasn't getting the Styles hasn't been fixed and may be worse. I'm not
sure it was supposed to have been fixed but "Simple patch to help take
care of some timing bugs" might be referring to it. To reiterate, the
first xterm I run in my .xsession often, especially on the slower
machine, does not get any Styles (not *, not xterm, nothing) even
though the other xterms (also run from the .xsession after a short
"sleep" delay...probably not starting until after fvwm2 is already
running) do get the Styles. Restarting fvwm2 fixes this problem but,
if I do it before some of the other delayed jobs in the .xsession
finish, some of them will never finish and I end up with no xclock or
xpostit+ or something.
The reason I say this may be worse is that it's now happening more
often on the AlphaStation, which is faster and hardly ever needs to
swap. In 2.0.42, it usually happened on the slower, lower RAM,
machine and only occasionally on the fast machine.
Request for 2.1.0:
Not a bug report and I know the TO-DO list mentions resurrecting
StubbornPlacement but, in case it's not implicitly grouped with
StubbornPlacement, the return of StubbornIconPlacement would also be
very nice - especially the feature that caused icons to reposition
themselves to avoid windows when the Scroll function was called. I
had gotten used to not having to search for icons under windows.
Thanks much,
--
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 Sun Jul 14 1996 - 20:00:11 BST