On 07/20/10 05:09, Thomas Adam wrote:
On Mon, Jul 19, 2010 at 10:44:04PM -0200, Mauricio E. Silva wrote:
Don't get killed trying to find the problem... my
configuration file it's old and big, i'll will start a new
configuration from scratch and see what happen.
I don't suppose you're got a "non-standard" keyboard mapping? Perhaps one
that isn't US or UK?
I ask because the only thing left I can suggest is that you're calling
setxkbmap or xmodmap before any XClients have started. I've said so many
times before that if you are, you *must* start these programs before hand.
If they're in StartFunction or something, shift them to ~/.xsession or
~/.xinit, as in:
xmodmap blah&
exec fvwm
It is *not* enough to start these keyboard programs any other way, as FVWM
never remaps the keys once X11 has loaded -- which can be the only thing
which explains why restarting FVWM [0] works for you, despite the mappings
looking OK.
HTH,
-- Thomas Adam
[0] No, not a bug.
E-mail clasificado por el Idenfificador de Spam Inteligente.
Para modificar la categorÃa clasificada acceda a su webmail
Este mensaje ha sido verificado por el E-mail Protegido.
Antivirus actualizado en 20/07/2010 / Versión: 0.96/11394
Thomas:
My keyboard mapping is US and as a secondary mapping is LATAM,
the configuration
is in the xorg.conf, i did not remap any key with xmodmap. But the
problem happen even if
i remove LATAM and the option to change within keymaps (CTRL+SHIFT) from
the configuration.
I start the X manually so no .xsession or .Xclients config at
all. My .xinitrc at the moment of writing this is only one line:
exec fvwm2
--
Mauricio E. Silva
