On Mon, 23 Dec 2013, Brian wrote:
All the information you have provided indicates that your setup is sane.
If the problem persists with xdm, lightdm etc you may start to think in
terms of a search with "evdev Logitech Unifying receiver". You have a
solution (which you rightly regard as unsatisfa
On Mon 23 Dec 2013 at 19:07:16 +0100, Pierre Frenkiel wrote:
> I don't have a .xsessionrc and my .xinitrc just calls fvwm. So, as the
> problem occurs
> with startx, it doesn't seem useful to look at session managers. Anyway,
> I'll
> try with xdm when coming back, in 2 weeks.
All the in
On Mon, 23 Dec 2013, Brian wrote:
If you had a .xsessionrc file in your home directory containing the line
"setxkbmap us" this would account for what you see in an xterm. However,
it does not explain what you get at the kdm login prompt. So you likely
do not have such a file. I wonder whether xd
On Mon 23 Dec 2013 at 14:29:23 +0100, Pierre Frenkiel wrote:
> On Mon, 23 Dec 2013, Brian wrote:
>
> >Following Andrei's suggestion wouldn't be a bad idea. 'service kdm stop'
> >first.
>
> as the problem occurs with startx, no session manager od display manager is
> involved.
> More, the pr
On Mon, 23 Dec 2013, Brian wrote:
Following Andrei's suggestion wouldn't be a bad idea. 'service kdm stop'
first.
as the problem occurs with startx, no session manager od display manager is
involved.
More, the problem already exists at the grub level: I checked that by lauching
the grub
On Mon 23 Dec 2013 at 11:47:49 +0100, Pierre Frenkiel wrote:
> As far as the 2 commands above are concerned, you are perfectly right, but
> the problem is that they change nothing for the keyboard actual
> behaviour, using the fvwm display manager or startx.
> As the Xorg.0.log is correct,
On Mon, 23 Dec 2013, Brian wrote:
X (whether started with a login manager or startx) gets information about
the keyboard from udev via evdev.
. . .
desktop:/home/brian# udevadm info --export-db | grep XKB
...
desktop:/home/brian# udevadm trigger --subsystem-match=input --action=change
. . .
On Sun 22 Dec 2013 at 18:41:11 +0100, Pierre Frenkiel wrote:
> The problem is that the actual layout is still "us", in the login
> greeting window as well as in xterm. I must then run, at each session start,
>setxkbmap -layout gb (that works)
> as the layout reverts to us when I logout
>
> Ca
On Du, 22 dec 13, 18:41:11, Pierre Frenkiel wrote:
>
>61.485] (**) Option "xkb_rules" "evdev"
>[61.485] (**) Option "xkb_model" "pc105"
>[61.485] (**) Option "xkb_layout" "gb"
>
> The problem is that the actual layout is still "us", in the login
> greeting window as well as in
hi everybody,
I recently bought a Logitech wireless keyboard, and since it came from UK, its
layout is gb
I naïvely thought that I just had to replace, in /etc/default/keyboard:
XKBLAYOUT="us"
by
XKBLAYOUT="gb"
and reboot, but that works only for the console mode, although the keyboard
ma
10 matches
Mail list logo
