Hi,
(i begin to owe Greg Wooledge half a sysadmin salary and half one for a
geriatric nurse)
Greg Wooledge wrote:
> Error messages, if there are any, should be in ~/.xsession-errors
$ cat ~/.xsession-errors
Cannot parse color "dtcolor5"
couldn't create gradient
Cannot parse color "dtcolor5"
couldn't create gradient
sh: 1: fvwm-menu-xlock: not found
sh: 1: fvwm-menu-xlock: not found
sh: 1: xdg_menu: not found
[fvwm][executeModule]: <<ERROR>> No such module 'FvwmConsole' in ModulePath
'/usr/lib/fvwm/2.6.8'
[fvwm][executeModule]: <<ERROR>> No such module 'FvwmBanner' in ModulePath
'/usr/lib/fvwm/2.6.8'
[fvwm][executeModule]: <<ERROR>> No such module 'FvwmButtons' in ModulePath
'/usr/lib/fvwm/2.6.8'
[fvwm][executeModule]: <<ERROR>> No such module 'FvwmCommandS' in ModulePath
'/usr/lib/fvwm/2.6.8'
/usr/share/X11/fvwm2/pixmaps/slate.gif is a 128x128 GIF87a image with 256
colors
Default gamma for IRGB image is 2.20
Compressing colormap...didn't find evidence of prior run.
6 unique colors
Building XImage...done
[fvwm][executeModule]: <<ERROR>> No such module 'FvwmConsole' in ModulePath
'/usr/lib/fvwm/2.6.8'
$
Indeed, there is no directory /usr/lib/fvwm .
In Debian 11 there was /usr/lib/fvwm/2.6.8 utterly filled with Fvwm* files.
Four of five fingers point to me and my ~/.fvwm2rc":
ModulePath /usr/lib/fvwm/2.6.8
I see traces that i adjusted this multiple times over the years:
/usr/lib/X11/fvwm2 , /usr/lib/fvwm/2.6.5 , /usr/lib/fvwm/2.6.8.
So what's its name this year ?
$ find /usr -name FvwmPager
/usr/libexec/fvwm2/2.7.0/FvwmPager
It's a bit late in the evening for system-wide experiments.
I will see tomorrow whether i can omit the ModulePath line or whether i
have to point it to /usr/libexec/fvwm2/2.7.0 .
Further i should begin to learn what the following lines in my ~/.fvwm2rc
mean:
Colorset 3 fg black, bg rgb:c8/d3/e5, VGradient 100 dtcolor5 rgb:c8/d3/e5
...
Colorset 6 fg black, bg rgb:b4/aa/94, VGradient 100 dtcolor5 rgb:b4/aa/94
...
PipeRead 'fvwm-menu-xlock --special-first'
PipeRead 'fvwm-menu-xlock --special-first --name=XSaverMenu -- -nolock'
...
PipeRead 'xdg_menu --charset UTF-8 --format fvwm2'
I guess that they fail since a dozen years at least. :))
As said, 20+ years of migration from machine to machine. Oh nostalgy.
Have a nice day :)
Thomas
