#1049863 (no subject)

Package:
fvwm
Source:
fvwm
Description:
F(?) Virtual Window Manager
Submitter:
Ilya Olegovich
Date:
2025-05-31 19:09:02 UTC
Severity:
normal
#1049863#5
Date:
2023-08-16 10:17:44 UTC
From:
To:
Dear Maintainer,

When changing screen from/to fullscreen mode, or when restarting FVWM, icons of iconified (minimized) applocations dissapear, deiconify/iconify action is required or FVWM Recapture command to make it visible again. Also, when using original FVWM source code without debian patches, icons not only dissapear on fullscreen change/FVWM restart, but whole FVWM is crashing, so, probably, something is bad with dependencies, or existing patch is not solving the whole problem.

#1049863#10
Date:
2023-08-16 11:42:48 UTC
From:
To:

#1049863#15
Date:
2023-08-16 14:49:29 UTC
From:
To:
The crashes without Debian patches are due to a change in xlib that
causes fvwm to crash without a fix.  In essence you need the patch
xthread_fix.patch to keep fvwm2 from crashing with newer versions of
xlib. This fix is applied upstream, just not in a release tarball.
This fix should have nothing to do with the icon issue you are
experiencing.

As for the icon issue you are experiencing, I'll see if I can
reproduce it. Note that fvwm version 2 is no longer supported
upstream, you may want to give fvwm3 a try and see if the issue is
still there.

jaimos

#1049863#20
Date:
2023-08-16 15:02:05 UTC
From:
To:

#1049863#25
Date:
2023-08-16 15:03:59 UTC
From:
To:
Can you clarify what you mean by 'switching fullscreen mode', as I
don't recognize this as an fvwm option.

jaimos

#1049863#30
Date:
2023-08-16 15:09:08 UTC
From:
To:

#1049863#35
Date:
2023-08-16 15:45:33 UTC
From:
To:

#1049863#40
Date:
2023-08-16 15:51:47 UTC
From:
To:

#1049863#45
Date:
2023-08-16 15:51:55 UTC
From:
To:
The Debian patches should not be affecting the Icon behavior (there
are only a few, and they mostly just rename things to fit Debian
policy). It might be some dependency issue, if you rebuild the whole
package using the libs on your machine does this issue go away? Maybe
you have some library conflict and require the package being rebuilt
for your system, so it is the rebuild of the package that is fixing
the issue for you, not the debian patches.

#1049863#50
Date:
2023-08-16 15:57:43 UTC
From:
To:

#1049863#55
Date:
2023-08-16 18:19:59 UTC
From:
To:
It was suggested to add the following option to the builds configure
script, --disable-thread-safety-constructor.

Can you add this option to your build and see if that helps the issue at all?

jaimos

#1049863#60
Date:
2023-08-16 18:53:10 UTC
From:
To:

#1049863#65
Date:
2023-08-17 17:38:20 UTC
From:
To:
I am dropping this bug to normal, since it is just a virusal issue due to
missing some an expose event causing the icons to refresh themselves.

It seems fvwm3 has a similar issue, if you want to follow up on this please
use the github issue form in fvwm3 (fvwm version 2 is no longer supported
upstream).

https://github.com/fvwmorg/fvwm3/issues/818

If you want to follow up more, you can use that issue and the fvwm3 devs
might be able to help track down the issue.

If it gets fixed in fvwm3, I will see if it is possible to backport the
fix, but as of now I can't fix this until it is fixed in fvwm3.

jaimos

#1049863#70
Date:
2023-08-17 18:49:31 UTC
From:
To:

#1049863#75
Date:
2023-09-10 09:57:51 UTC
From:
To:
After applying patch "xthread_fix.patch" and siebenmann's patch posted here:
https://github.com/fvwmorg/fvwm3/issues/818#issuecomment-1401144381

The issue seems to go away, when using fvwm 2.7.0 source code, icons
are displayed as it should, after restart, application fullscreen
change, etc.
But, maybe, there is a reason to wait for a more official solution, as
a main FVWM developer is aware about this issue in all FVWM 2/3
versions when using new GNU/Linux distributions.