I updated fvwm to 2.5.12 (which is in x86) yesterday and when I rebooted, it did not use my .fvwm2rc anymore (even fvwm -replace -c "Read .fvwm2rc" does nothing...). May be does it come from gdm, which I could not make use fvwm directlw, so I edited my /etc/X11/Sessions/XSession to make it start if no other wm is chosen (ugly but works). reemerging fvwm-2.5.10-r6 made it all work again.
you mean ~/.fvwm2rc? It's depracated, but still supported in 2.5.12, ~/.fvwm/.fvwm2rc and ~/.fvwm/config are the standard names. but yours should still work, have you tried starting it with fvwm -f ~/.fvwm2rc. Are there any errors on the console? would it be possible to run strace -ologfile -eopen fvwm and post the logfile it creates here?
Marking WORKSFORME, please REOPEN if you can provide some more information to help identify any problem.
Hi, I just found why it didn't work yesterday. The new name for the config file is .fvwm/conf And I had a directory with this exact name, containing some parts of my .fvwm2rc. I changed its name and everything worked fine. Perhaps a eeinfo should be added to the ebuild ?
Alexandre: Ahh! I agree, I'll add an eeinfo.