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

Bug#346307: marked as done (xserver-xfree86 Xkb Keyboard Layout Switching Not Working in XF86Config-4)

Your message dated Mon, 29 Jan 2007 02:07:18 +0100
with message-id <45BD48C6.6020208@ens-lyon.org>
and subject line Bug#346307: xserver-xfree86 Xkb Keyboard Layout Switching Not Working in XF86Config-4
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: xserver-xfree86
Version: XFree86 Version 4.3.0.1 (Debian 4.3.0.dfsg.1-14sarge1 20050901212727)

Hi,
I have the following options i my "/etc/X11/XF86Config-4" config file:

Section "InputDevice"
    Identifier     "Generic Keyboard"
    Driver         "keyboard"
    Option         "CoreKeyboard"
    Option         "AutoRepeat" "500 30"
    Option         "XkbRules" "xfree86"
    Option         "XkbModel" "pc104"
    Option         "XkbLayout" "us,bg(phonetic)"
    Option         "XkbOptions" "grp:alt_shift_toggle"
EndSection

I think it's some kind of an internal bug to the XFree86 server. Xorg has no problems handling the same configuration for keyboard layout switching (of course in xorg the Driver value is "kbd" and the XkbRules Option has a value "xorg").

I am using Debian GNU/Linux version 3.1 "sarge"
Kernel: Linux debian 2.6.8-2-k7 #1 Tue Aug 16 14:00:15 UTC 2005 i686 GNU/Linux

Thanks for the attention


-----------------------------------------------------------------
http://knigi.GBG.bg - Поръчай книги онлайн!

--- End Message ---
--- Begin Message --- 
Closing as suggested by the submitter since the bug has probably been
fixed in the meantime. Feel free to reopen if you ever reproduce.

Brice

--- End Message ---
Reply to: