On Thu, 24 Jun 1999, Dan Espen wrote:
> Dominik Vogt <dominik.vogt_at_gmx.de> writes:
> > On Thu, Jun 24, 1999 at 04:20:30PM -0400, Gary Jackson wrote:
> > >
> > > I figured out the cause of my color map problems. The color map
> > > starts out fine, but when there is console output to the frame buffer
> > > while fvwm is running, it gets all screwed up. So, starting xconsole
> > > before fvwm fixed this problem, and I feel like a moron. Oddly
> > > enough, however, I was not experiencing this problem with twm...
> > >
> > > OBTW, am I talking at a wall here? Why haven't I gotten a response of
> > > any kind, even a "fsck off" or somesuch?
And they all rolled over and said (along with me, off-list), "Sorry".
But really, this would have left me off in the ozone. This seems like a
Really Good Candidate for a Hall of Fame "Nasty Problem" list. As it is
probably very memory allocation specific, using different wm's with all
else the same could cause very different behavior. Is there a list of
really obscure "I saw this once" issues assembled for problem debuggers to
go through? The corrective action Gary took was not intuitively obvious,
but was so easy to try that it would be worth a place on such a list. At
the very least, it appears so if one has the same platform.
Now I'll go back into lurk mode until I see something I know about. And
thanks for all of you who read and make suggestions. You're a great
crowd. (That's the nearest approach I can make to an fvwm-related topic.)
Michael Tiefenback
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Thu Jun 24 1999 - 22:40:49 BST