On Sep 19 2022, Jonathan Gray wrote:
> On Sun, Sep 18, 2022 at 08:57:18PM +0200, Walter Alejandro Iglesias wrote:
> > On Sep 18 2022, Walter Alejandro Iglesias wrote:
> > > On Sep 18 2022, Walter Alejandro Iglesias wrote:
> > > > On Sep 18 2022, Jonathan Gray wrote:
> > > > > On Fri, Sep 16, 2022 at 10:19:15PM +1000, Jonathan Gray wrote:
> > > > > > I'll see if I can reproduce this on another 965 machine.
> > > > >
> > > > > I don't see any errors with fvwm2 on mobile 965 (x61).
> > > >
> > > > I can not reproduce it in my thinkpad T410 either (same snapshot).
> > > >
> > > > For me at least, it's curious that I can trigger the issue *only*
> > > > brousing fvwm2 menus. I don't know what fvwm2 does with its menus.
> > >
> > > As it happened to me with other fvwm2 issue recently, today I noticed
> > > that using fvwm2 default configuration I couldn't reproduce the bug.
> > >
> > > This time it took me an hour to discover which setting made the
> > > difference. It came out that adding any of the following two options to
> > > MenuStyle the bug is gone:
> > >
> > > MenuStyle * TrianglesSolid
> > > MenuStyle * TrianglesUseFore
> > >
> > > Both disable the relief in menus arrows, so the relief shape is what
> > > confuses drm, mesa or whatever is making X to crash.
> > >
> > > That's mean that to reproduce the bug you have to remove the following
> >
> > "That means", is what I meant. :-)
> >
> > > line in the default fvwm2 config (line 275):
> > >
> > > MenuStyle * TrianglesSolid, TrianglesUseFore
>
> that line does not appear in
> /usr/X11R6/lib/X11/fvwm/.fvwmrc
>
> is there another sample config?
I assume you understood me in that I've been talking about "fvwm2" from
ports all the time. If you have nothing under your ~/.fvwm directory
and run fvwm2, it will load its default configuration under
/usr/local/share/fvwm/default-config. So, you can copy the contents of
that directory to your home:
$ cp -r /usr/local/share/fvwm/default-config/* ~/.fvwm/
... and modify the file ~/.fvwm/config to your taste.
***
By the way. I've been using fvwm2 for many years, and I observed many
issues that appear only with the modesetting driver (with OpenBSD and
Linux), at least with intel graphics. Mostly with fvwm2 fake
transparencies and animations, I didn't mention them because they
weren't severe (X didn't crash), and my solution was simply run intel
drivers. Yesterday I noticed another one, for some reason running
oclock under fvwm2 (again, this happens with modesetting, not with the
intel driver) slows down how images are drawn in the screen, creating
some scrolling effect. If they are useful to debug X I can report them
from now on.
--
Walter
