Bug#357480: xlibs: Confusion between latam and la keyboard layouts

2007-03-28 Thread roadmr
Hey! sorry for taking so long to respond. To be honest I've no idea, since
I changed jobs and i've been lucky enough to install debian only on
computers with spanish (es) keyboards, which work flawlessly.

Regards,
 Daniel

 Hi Daniel,

 About a year ago, you reported a bug to the Debian BTS regarding a
 confusion between latam and la keyboard layouts. Does this problem still
 matter today? With Xorg/Etch?

 Thanks,
 Brice



 !DSPAM:3,46019919321628110514346!








Bug#357480: xlibs: Confusion between latam and la keyboard layouts

2007-03-28 Thread Margarita Manterola

On 3/21/07, Brice Goglin [EMAIL PROTECTED] wrote:


About a year ago, you reported a bug to the Debian BTS regarding a
confusion between latam and la keyboard layouts. Does this problem still
matter today? With Xorg/Etch?


Hi!

I experienced this problem as well, and it's not currently a problem
in Etch. BUT for people that had upgraded, and changed their keyboard
to latam, the following update leaves X without keyboard, which is
cruel.

Sarge-Etch upgrades are not hit by this.

--
Besos,
Marga


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#357480: xlibs: Confusion between latam and la keyboard layouts

2007-03-21 Thread Brice Goglin
Hi Daniel,

About a year ago, you reported a bug to the Debian BTS regarding a
confusion between latam and la keyboard layouts. Does this problem still
matter today? With Xorg/Etch?

Thanks,
Brice



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#357480: xlibs: Confusion between latam and la keyboard layouts

2006-03-17 Thread Daniel Manrique
Package: xlibs
Version: 6.9.0.dfsg.1-4
Severity: important


For some reason the xlibs package has a la keyboard layout corresponding to 
the Laos keyboard; this is different from the rest of 
the system configuration which assumes la means latinamerican. Thus, when 
initially configuring the system and selecting la, one 
gets a latinamerican layout in text mode, but a Laos keyboard in graphical 
mode, thus rendering X effectively unusable. The workaround 
is to dpkg-reconfigure xserver-xorg and explicitly select the correct layout 
which for some strange reason was renamed to latam.

This behavior should be consistent between the global layout selection and that 
of X; either use the latam layout everywhere, or 
rename xlib's laos keyboard to something else and return latinamerican to la.


-- Package-specific info:
Keyboard-related contents of X.Org X server log file
/var/log/Xorg.0.log:
(==) Using config file: /etc/X11/xorg.conf
(==) ServerLayout Default Layout
(**) |--Screen Default Screen (0)
(**) |   |--Monitor HP 7540
(**) |   |--Device Intel Corporation 82915G/GV/910GL Express Chipset Family 
Graphics Controller
(**) |--Input Device Generic Keyboard
(**) Option XkbRules xorg
(**) XKB: rules: xorg
(**) Option XkbModel pc105
(**) XKB: model: pc105
(**) Option XkbLayout latam
(**) XKB: layout: latam
(==) Keyboard: CustomKeycode disabled
(**) |--Input Device Configured Mouse
(WW) The directory /usr/lib/X11/fonts/cyrillic does not exist.
Entry deleted from font path.
(WW) The directory /usr/lib/X11/fonts/CID does not exist.
Entry deleted from font path.
--
(II) Loading /usr/X11R6/lib/modules/drivers/i810_drv.so
(II) Module i810: vendor=X.Org Foundation
compiled for 6.9.0, module version = 1.4.1
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 0.8
(II) LoadModule: keyboard
(II) Loading /usr/X11R6/lib/modules/input/keyboard_drv.so
(II) Module keyboard: vendor=X.Org Foundation
compiled for 6.9.0, module version = 1.0.0
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 0.5
(II) LoadModule: mouse
(II) Loading /usr/X11R6/lib/modules/input/mouse_drv.so
--
(II) I810(0): direct rendering: Enabled
(==) RandR enabled
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension LBX
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
--
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing built-in extension XEVIE
(**) Generic Keyboard: Core Keyboard
(**) Option Protocol standard
(**) Generic Keyboard: Protocol: standard
(**) Option AutoRepeat 500 30
(**) Option XkbRules xorg
(**) Generic Keyboard: XkbRules: xorg
(**) Option XkbModel pc105
(**) Generic Keyboard: XkbModel: pc105
(**) Option XkbLayout latam
(**) Generic Keyboard: XkbLayout: latam
(**) Option CustomKeycodes off
(**) Generic Keyboard: CustomKeycodes disabled
(**) Option Protocol ImPS/2
(**) Configured Mouse: Device: /dev/psaux
(**) Configured Mouse: Protocol: ImPS/2
(**) Option CorePointer
(**) Configured Mouse: Core Pointer
--
(**) Configured Mouse: Emulate3Buttons, Emulate3Timeout: 50
(**) Option ZAxisMapping 4 5
(**) Configured Mouse: ZAxisMapping: buttons 4 and 5
(**) Configured Mouse: Buttons: 9
(II) XINPUT: Adding extended input device Configured Mouse (type: MOUSE)
(II) XINPUT: Adding extended input device Generic Keyboard (type: KEYBOARD)
(II) Configured Mouse: ps2EnableDataReporting: succeeded
Warning: font renderer for .pcf already registered at priority 0
Warning: font renderer for .pcf.Z already registered at priority 0
Warning: font renderer for .pcf.gz already registered at priority 0
Warning: font renderer for .snf already registered at priority 0

X.Org X server log files on system:
-rw-r--r--  1 root root 76018 2006-03-17 09:08 /var/log/Xorg.0.log

Compiled XKB description for X server :0.0:
xkb_keymap {
xkb_keycodes xfree86+aliases(qwerty) {
minimum = 8;
maximum = 255;
 ESC = 9;
AE01 = 10;
AE02 = 11;
AE03 = 12;
AE04 = 13;
AE05 = 14;
AE06 = 15;
AE07 = 16;
AE08 = 17;
AE09 = 18;
AE10 = 19;
AE11 = 20;
AE12 = 21;
BKSP = 22;
 TAB = 23;
AD01 = 24;
AD02 = 25;
AD03 = 26;
AD04 = 27;
AD05 = 28;
AD06 = 29;
AD07 = 30;
AD08 = 31;
AD09 = 32;
AD10 = 33;
AD11 = 34;
AD12 = 35;
RTRN = 36;
LCTL = 37;
AC01 = 38;
AC02 = 39;
AC03 = 40;
AC04 = 41;
AC05 = 42;
AC06 = 43;
AC07 = 44;
AC08 = 45;
AC09 = 46;
AC10 = 47;
AC11 = 48;
TLDE = 49;
LFSH = 50;
  

Bug#357480: xlibs: Confusion between latam and la keyboard layouts

2006-03-17 Thread Daniel Stone
On Fri, Mar 17, 2006 at 09:16:35AM -0600, Daniel Manrique wrote:
 For some reason the xlibs package has a la keyboard layout corresponding to 
 the Laos keyboard; this is different from the rest of 
 the system configuration which assumes la means latinamerican. Thus, when 
 initially configuring the system and selecting la, one 
 gets a latinamerican layout in text mode, but a Laos keyboard in graphical 
 mode, thus rendering X effectively unusable. The workaround 
 is to dpkg-reconfigure xserver-xorg and explicitly select the correct layout 
 which for some strange reason was renamed to latam.
 
 This behavior should be consistent between the global layout selection and 
 that of X; either use the latam layout everywhere, or 
 rename xlib's laos keyboard to something else and return latinamerican to 
 la.

This change was, oddly enough, done for consistency within XKB itself;
la is the ISO country code for Laos.  Other tools need to be changed to
reflect this.


signature.asc
Description: Digital signature


Bug#357480: xlibs: Confusion between latam and la keyboard layouts

2006-03-17 Thread Denis Barbier
On Fri, Mar 17, 2006 at 09:16:35AM -0600, Daniel Manrique wrote:
 Package: xlibs
 Version: 6.9.0.dfsg.1-4
 Severity: important
 
 
 For some reason the xlibs package has a la keyboard layout
 corresponding to the Laos keyboard; this is different from the rest
 of the system configuration which assumes la means latinamerican.
 Thus, when initially configuring the system and selecting la, one
 gets a latinamerican layout in text mode, but a Laos keyboard in
 graphical mode, thus rendering X effectively unusable.

Can you please tell which tool assumes that la means latinamerican?

Denis


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]