slackware 64 current: fvwm window buttons look different

jr_bob_dobbs · 01-28-2021, 08:04 AM

I had been running a snapshot of slackware 64 current from August. On Sunday or Saturday I performed a fresh install of slackware 64 current (referred to from here on as "January).

The window buttons in Fvwm look different between January and August.

screenshot of January Fvwm, note the xmag views

Near as I can tell, something about the shadow and/or highlight lines on the buttons are misaligned by a pixel?

The Fvwm config I used is the same.

Oddly enough, it turns out the version of Fvwm is the same. The only difference is (a) the compiler & lib toolchain and (b) Patrick's Fvwm slackbuild for January has a build of 3 while the August one has a build of 2. I do not have the source from August so cannot compare to ascertain the difference.

Is this happening to anyone else's install?

Thank you.

ThomasAdam · 01-28-2021, 10:46 AM

Hi,

Is this fvwm3 or fvwm2? I haven't changed the rendering of borders in either -- but I would be keen of you could repeat a few screenshots showing how it used to work, versus how it's broken.

Interestingly though, I wonder if I too am seeing the same thing (this is on Debian though):

Here's a screenshot

Kindly,
Thomas

jr_bob_dobbs · 01-28-2021, 02:17 PM

fvwm 2.Specifically, version 2.6.9. Both August and January installs of Slackare are using the same version of Fvwm (though a build of "2" is assigned to August and "3" assigned to January).

screenshot as it is in August Slackware: https://blockhead.neocities.org/picc..._slackware.png

p.s. Off topic, but your screenshot is interesting in that it shows each of the four sides of the window a different color. I did not realize that was possible. Interesting!

ThomasAdam · 01-28-2021, 03:04 PM

Quote:

Originally Posted by jr_bob_dobbs

fvwm 2.Specifically, version 2.6.9. Both August and January installs of Slackare are using the same version of Fvwm (though a build of "2" is assigned to August and "3" assigned to January).

screenshot as it is in August Slackware: https://blockhead.neocities.org/picc..._slackware.png

It does seem rather borked. Interestingly though, on my laptop, I don't see the same glitch:

Screenshot working.

This must be an xlib problem.

Quote:

Originally Posted by jr_bob_dobbs

p.s. Off topic, but your screenshot is interesting in that it shows each of the four sides of the window a different color. I did not realize that was possible. Interesting!

It's a patch to fvwm3 which I've not released yet. Probably won't do until I rewrite the decor code.

Kindly,
Thomas

ThomasAdam · 01-28-2021, 05:22 PM

If you can send me your fvwm config, that might help, too.

jr_bob_dobbs · 01-28-2021, 06:10 PM

Quote:

Originally Posted by ThomasAdam

If you can send me your fvwm config, that might help, too.

Can do. I have attached it to this post (around 30k).

ThomasAdam · 01-29-2021, 03:35 PM

Hi,

Thanks for your config. This problem isn't in fvwm2, it's in fvwm3, and the problem is with commit 'e8c3efc53dcf5ffae5183c271accc1f38a6a5c69'.

If you can compile fvwm3 from source (by checking out the git repo for it: https://github.com/fvwmorg/fvwm3), please have a look at the "ta/revert-sh-hi-fix" branch which fixes the rendering issue for me, but would be good to let me know.

Kindly,
Thomas

ThomasAdam · 01-29-2021, 05:18 PM

As an aside,

In your config, I noticed you were quite rightly having to do this:

Code:

DestroyFunc ToggleTitle
AddToFunc   ToggleTitle
+ I ThisWindow (State 1) WindowStyle Title
+ I TestRc (Match) State 1 False
+ I TestRc (Match) Break
+ I WindowStyle !Title
+ I State 1 True

I've now committed this to master (https://github.com/fvwmorg/fvwm3/com...574a7b7f.patch)

HTH,
Thomas

jr_bob_dobbs · 02-01-2021, 07:44 PM

Quote:

Originally Posted by ThomasAdam

Hi,

Thanks for your config. This problem isn't in fvwm2, it's in fvwm3,

Umm, now I am confused. I'm having the problem with fvwm 2, in January Slackware, yet not in fvwm 2 in August Slackware. I've not yet ever run 3. Could you clarify please?

edit:
as for the "ToggleTitle" thing, that's not something I did. Because I'd tried FVWM like a year ago and it had gone horribly wrong, this time (though still in Slackware) I grabbed a fresh default config from a Devuan VM, so credit would go to either the Devuan or Debian team. I'd done this in the hope of a more stable and sane starting point.

jr_bob_dobbs · 12-12-2023, 12:37 PM

Why am I necro-posting the thread? Because it was never solved (instead I switched distros, the problem doesn't happen in Void) and because I have new data as to the original problem.

In April I started an a build of BLFS 11.3. When I got to the point where I put FVWM in, it had the same problem. A day or so later, after installing more packages, the problem went away. So the presence or absence of a particular package, program or file made the problem go away.

Because I used the slackware package manager for my BLFS, I have a record of the order of installation of packages. Here is a excerpt from an ls -trl (sort by date in "reverse" order) that shows the next few packages installed after FVWM:

Code:

-rw-r--r-- 1 root root  12287 Aug 14 14:24 fvwm-2.7.0-x86_64-1_lfs
-rw-r--r-- 1 root root   1292 Aug 16 09:47 xorg_intel_driver-20230223-x86_64-1_lfs
-rw-r--r-- 1 root root   1059 Aug 16 09:54 xorg_ati_driver-19.1.0-x86_64-1_lfs
-rw-r--r-- 1 root root   1153 Aug 16 10:03 pciutils-3.9.0-x86_64-1_lfs
-rw-r--r-- 1 root root  43571 Aug 16 12:59 imagemagick-7.1.0_61-x86_64-1_lfs
-rw-r--r-- 1 root root    746 Aug 16 13:00 autocutsel-0.10.1-x86_64-1_lfs
-rw-r--r-- 1 root root  12952 Aug 16 14:51 cryptopp-8.8.0-x86_64-1_lfs
-rw-r--r-- 1 root root   1449 Aug 19 13:17 treewm-0.4.501-x86_64-1_lfs

The above excerpt ends at treewm becuase I'd noticed the problem had gone away before putting in treewm.

I can't imagine that imagemagick, autocutsel nor cryptopp would affect graphics rendering in a window manager, but I left them for completeness, in case there is some unexpected interrelationship that I am unaware of.

One could tentatively conclude that the intel and ati drivers for xorg fixed this problem. My computer has Intel and Nvidia graphics cards in it.

More recently, in my Devuan system, I have the same visual glitch in FVWM ... and also in the Blackbox window manager. This would indicate that it's not unique to FVWM and/or not a FVWM problem. The complicating thing is this: Devuan has those two xorg drivers already in. This apparent contradiction has me confused, and with glitch buttons & borders

I hope someone can shed some light on this matter. Thank you.

jr_bob_dobbs · 01-16-2024, 05:01 PM

BTW, in topic with the original topic, it happens in a Slackware 15.0 install as well.