Hi Jaimos,
with setting
Style * Icon
... I made the screen shot Style_asterisk_Icon.webp, see attachment.
What you see is the area of the pager and the Icon Area below.
- Five iconified urxvt terminals are all labeled urxvt (1) - their window names
have different numbers.
- The two iconifie
Hi Jaimos,
> Since the patch you are reverting doesn't touch FvwmPager, the
> issue is in fvwm itself, and my initial guess is that fvwm stops
> broadcasting window/icon names to the modules correctly.
I agree that fvwm3 does not generate the icon (i) and window (t) labels
correctly,
see urxvt l
Hi Jaimon,
a correction: both issues ...
1) Style "*" !Icon is no more respected: I see icons on the desktop.
2) When a window is moved to another desktop, the icon in the dock (I use
tint2) does not move along with the window.
... also happen with unpatched fvwm3 1.1.2.
Moreover: if I iconify a
Dear Jaimos,
I had no missing *FvwmPager: SmallFont since I reverted
ffe942d66cdb1a24d761d9e89c1a4dab49f2400c.
Although above revert works fine in 2.6.8 and 2.7.0, it has quite substantial
side effects in fvwm3 1.1.2:
- Style "*" !Icon is no more respected: I see icons on the desktop.
- When a
Hi Jaimos,
reverting ffe942d66cdb1a24d761d9e89c1a4dab49f2400c in fvwm3 doesn't work without conflicts, hence the lengthy details below:
I cloned the current fvwm source with following last commit: https://github.com/fvwmorg/fvwm3/commit/d49736cb6c814450e967f814dac79c8e1819b8cd
# git revert
PLease find attached the screen shot Pager_started_with_fvwm3.png
Package: fvwm3
Version: 1.1.2+ds-1
Severity: normal
File: /usr/bin/fvwm3
X-Debbugs-Cc: dr.a.ro...@gmx.de
Dear Maintainer,
Dear Jaimos,
as far as I can see, you are in the process of reworking the FvwmPager in FVWM3,
and also the maintainer of Fvwm in Debian,
so you might be the most knowledgable
Dear maintainers,
with the removal of gcc-8 the upgrade from
Buster to testing/Bullseye works now flawlessly.
Thank you very much!
Dear maintainers,
I tried upgrading from from buster on jan 22 2021.
It failed due to this bug (964477 + merged 961990).
It's also really disappointing that
https://wiki.debian.org/Status/Testing
does not list any current problem...
Bullseye is less than two months away from a hard f
Dear
Package Maintainers and Authors
after ading
Acquire::GzipIndexes "true";
in apt.conf to save disk space and moreover reduce wear on the SSD
I ran into the same failure as decribed in this bug report.
Further digging into the matter revealed that
update-apt-xapian-index
10 matches
Mail list logo
