[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#632970: marked as done (cannot set keyboard layout for vserver)

Your message dated Fri, 8 Jul 2011 15:32:10 +0200
with message-id <20110708133210.GD8645@mraw.org>
and subject line Re: Bug#632970: cannot set keyboard layout for vserver
has caused the Debian Bug report #632970,
regarding cannot set keyboard layout for vserver
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org

632970: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632970
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: keyboard-configuration
Version: 1.68+squeeze2

If I try to define a German keyboard layout for a vserver,
then this setting is ignored. I still get qwerty for the
XWindow session running on the vserver, even though all
real or virtual hosts involved have been configured for a
German layout. All are running Squeeze (6.0.2).



--- End Message ---
--- Begin Message ---
Harald Dunkel <harald.dunkel@aixigo.de> (08/07/2011):
> Sorry to say, but this is not reasonable. setxkbmap wouldn't
> work if Xephyr wouldn't be a XWindow server. Not to mention
> that I get the same problem using xorg's Xnest.

Xnest is dead, so there's no point in trying to prove a point
with it. As for Xephyr, it's a nested server which has no
real input device AFAICT, so you get to deal with inheriting
xkb settings.

> About running setxkbmap: This is not an option, since
> it requires to login first, but user authentication
> requires a (correctly configured) keyboard. The remote
> kdm doesn't know the user's keyboard, either.

For a Xephyr started with Xephyr :1 &, that works:
  DISPLAY=:1 setxkbmap foo bar

> I understand that you didn't take this into account on
> designing keyboard-configuration, but I cannot help it.

I have nothing to do with keyboard-configuration.

> My suggestion would be to open this bug report again
> and to try a more constructive approach.

I suggest you go call setxkbmap, and leave that bug report


Attachment: signature.asc
Description: Digital signature

--- End Message ---

Reply to: