Bug#363229: xserver-xorg: No way to set the XKB data directory
On Wed, May 03, 2006 at 02:04:11AM +0300, Shai Berger wrote: On Wednesday, May 3 2006 01:29, Denis Barbier wrote: On Thu, Apr 27, 2006 at 06:05:03PM +0300, Shai Berger wrote: Nope. It doesn't work for me yet. I'll just bypass it in my .xinitrc. Setting XKBPATH works fine for me, can you please explain how you proceed so that I can reproduce your problem? I set XKBPATH up in my .profile, log in on vt1, and type this command: $ XKBPATH=$XKBPATH XPSERVERLIST=:64 LANG=en_US.UTF-8 startx -- :1 -dpi 96 Ok, there was indeed an error, XKBPATH was read when parsing command-line options, so it may be ignored. You can add the 'r' option (turns on auto-repeat) for instance, it should work then. I just committed a fix into SVN. Thanks. Denis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#363229: xserver-xorg: No way to set the XKB data directory
On Thu, Apr 27, 2006 at 06:05:03PM +0300, Shai Berger wrote: Nope. It doesn't work for me yet. I'll just bypass it in my .xinitrc. Setting XKBPATH works fine for me, can you please explain how you proceed so that I can reproduce your problem? Denis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#363229: xserver-xorg: No way to set the XKB data directory
On Wednesday, May 3 2006 01:29, Denis Barbier wrote: On Thu, Apr 27, 2006 at 06:05:03PM +0300, Shai Berger wrote: Nope. It doesn't work for me yet. I'll just bypass it in my .xinitrc. Setting XKBPATH works fine for me, can you please explain how you proceed so that I can reproduce your problem? I set XKBPATH up in my .profile, log in on vt1, and type this command: $ XKBPATH=$XKBPATH XPSERVERLIST=:64 LANG=en_US.UTF-8 startx -- :1 -dpi 96 (yes, I know the beginning is superfluous, but I typed it like that once, and now I only use history to bring it up). When the session is started, if I check it in an xterm, the environment variable is set, but I do not see the effects (the difference is that with my setup, alt-caps changes keyboard layouts). I use KDE, and when I tried to do what I said I'd do (run a setxkbmap | xkbcomp in .xinitrc) it didn't work -- I had to do it in KDE's autostart, that is, after the WM is up. I suspected KDE was doing something funny, so I tried IceWM -- there, too, the XKBPATH was not respected, although it was defined in shells in xterms (IceWM was started from an .xinitrc file). However, with IceWM, running the setxkbmap|xkbcomp pipe in .xinitrc did work. Hope this helps, and thanks for your efforts, Shai. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#363229: xserver-xorg: No way to set the XKB data directory
Nope. It doesn't work for me yet. I'll just bypass it in my .xinitrc. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#363229: xserver-xorg: No way to set the XKB data directory
Just for the record, this bug would not bother me if bug #362850, which offers my customizations as a patch, were solved. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#363229: xserver-xorg: No way to set the XKB data directory
On Tue, Apr 18, 2006 at 05:02:12AM +0300, Shai Berger wrote:
Package: xserver-xorg
Version: 1:7.0.12
Severity: normal
Following the transition to xkb-data and xkeyboard-config, I was
told to put my customized xkb files aside and make the server use
them by setting the XKBPATH. However, setting the XKBPATH variable
didn't work (seems like the variable was ignored; I tried setting it
in a user's login shell as well as root's shell, then restarting X).
It works for me.
My default XKB settings with xkb-data:
$ setxkbmap -print
xkb_keymap {
xkb_keycodes { include xfree86+aliases(azerty) };
xkb_types { include complete };
xkb_compat{ include complete };
xkb_symbols { include pc(pc105)+fr+compose(caps)};
xkb_geometry { include pc(pc105) };
};
Use XKB data from obsolete xlibs package:
$ export XKBPATH=/etc/X11/xkb
$ setxkbmap -print
xkb_keymap {
xkb_keycodes { include xfree86+aliases(azerty) };
xkb_types { include complete };
xkb_compat{ include complete };
xkb_symbols { include pc/pc(pc105)+pc/fr+compose(caps) };
xkb_geometry { include pc(pc105) };
};
The pc/ subdirectory shows that files are read from /etc/X11/xkb.
Activate these settings
$ setxkbmap -print | xkbcomp - :0
Check that X did load files from /etc/X11/xkb
$ xkbcomp :0 - | grep xkb_symbols
xkb_symbols pc/pc(pc105)+pc/fr+compose(caps) {
This variable must be set before X is started, or if it is set later,
you must call setxkbmap after setting this variable.
Then I tried the other method referred to in xkb-data's README.Debian,
that of passing a -xkbdir to the server. The server did not recognize
this flag (and gave me a list of the flags it did recognize...).
Indeed, it worked with 6.9 and does not seem to work anymore, I need
to check why.
Denis
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#363229: xserver-xorg: No way to set the XKB data directory
On Tue, Apr 18, 2006 at 05:02:12AM +0300, Shai Berger wrote: Then I tried the other method referred to in xkb-data's README.Debian, that of passing a -xkbdir to the server. The server did not recognize this flag (and gave me a list of the flags it did recognize...). I removed most of the XKB command-line options upstream. signature.asc Description: Digital signature
Bug#363229: xserver-xorg: No way to set the XKB data directory
On Tuesday, April 18 2006 11:30, Denis Barbier wrote:
On Tue, Apr 18, 2006 at 05:02:12AM +0300, Shai Berger wrote:
Package: xserver-xorg
Version: 1:7.0.12
Severity: normal
Following the transition to xkb-data and xkeyboard-config, I was
told to put my customized xkb files aside and make the server use
them by setting the XKBPATH. However, setting the XKBPATH variable
didn't work (seems like the variable was ignored; I tried setting it
in a user's login shell as well as root's shell, then restarting X).
It works for me.
My default XKB settings with xkb-data:
$ setxkbmap -print
This works for me too -- that is, when XKBPATH is set, setxkbmap does the
right thing. Still, startx does not. In :0, I ran the setxkbmap | xkbcomp
pipe, and in :1, I didn't. :1 was started manually from a shell where XKBPATH
was set (I have another problem, and that is setting XKBPATH for the server
that is started automatically with the system). The results I get are:
[EMAIL PROTECTED]:~$ xkbcomp :0 - | grep xkb_symbols
xkb_symbols pc/pc(pc105)+pc/us+pc/il:2+group(alt_caps_toggle) {
Which is what I want, but
[EMAIL PROTECTED]:~$ xkbcomp :1 - | grep xkb_symbols
xkb_symbols pc(pc105)+us+il:2 {
Which tells me the files including the definition for grp:alt_caps_toggle,
which is referenced in my xorg.conf, weren't consulted.
Thanks,
Shai.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#363229: xserver-xorg: No way to set the XKB data directory
On Tue, Apr 18, 2006 at 11:40:31AM +0300, Daniel Stone wrote: On Tue, Apr 18, 2006 at 05:02:12AM +0300, Shai Berger wrote: Then I tried the other method referred to in xkb-data's README.Debian, that of passing a -xkbdir to the server. The server did not recognize this flag (and gave me a list of the flags it did recognize...). I removed most of the XKB command-line options upstream. As users can inject any random data with xkbcomp, is it really safer? IMHO this is just annoying without any security improvement. Denis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#363229: xserver-xorg: No way to set the XKB data directory
On Tue, Apr 18, 2006 at 11:35:37PM +0200, Denis Barbier wrote: On Tue, Apr 18, 2006 at 11:40:31AM +0300, Daniel Stone wrote: On Tue, Apr 18, 2006 at 05:02:12AM +0300, Shai Berger wrote: Then I tried the other method referred to in xkb-data's README.Debian, that of passing a -xkbdir to the server. The server did not recognize this flag (and gave me a list of the flags it did recognize...). I removed most of the XKB command-line options upstream. As users can inject any random data with xkbcomp, is it really safer? IMHO this is just annoying without any security improvement. It's not for security reasons, it's because I don't believe it has any place on the command line. Config file, maybe, but why command line? signature.asc Description: Digital signature
Bug#363229: xserver-xorg: No way to set the XKB data directory
On Tuesday, April 18 2006 22:59, Daniel Stone wrote: On Tue, Apr 18, 2006 at 11:35:37PM +0200, Denis Barbier wrote: On Tue, Apr 18, 2006 at 11:40:31AM +0300, Daniel Stone wrote: On Tue, Apr 18, 2006 at 05:02:12AM +0300, Shai Berger wrote: Then I tried the other method referred to in xkb-data's README.Debian, that of passing a -xkbdir to the server. The server did not recognize this flag (and gave me a list of the flags it did recognize...). I removed most of the XKB command-line options upstream. It's not for security reasons, it's because I don't believe it has any place on the command line. Config file, maybe, but why command line? Well, I'm not an X Server developer, but I can see the usefulness of controlling the xkb directory in the invocation of the X Server -- for trying things out, or for user-specific features. As things are documented, this should be doable without the command-line option -- via the environment variable, that is, $ startx -- :3 -xkbdir XXX should be equivalent to $ XKBPATH=XXX startx -- :3 And the way I see things, it is indeed equivalent -- the environment variable is ignored. Did you remove this also? If so, how can I make the X Server use a different xkb directory? If not, why not? The same reasoning should apply as for the command-line option. Thanks, Shai. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#363229: xserver-xorg: No way to set the XKB data directory
On Wed, Apr 19, 2006 at 01:06:28AM +0300, Shai Berger wrote: As things are documented, this should be doable without the command-line option -- via the environment variable, that is, $ startx -- :3 -xkbdir XXX should be equivalent to $ XKBPATH=XXX startx -- :3 And the way I see things, it is indeed equivalent -- the environment variable is ignored. Did you remove this also? No, I didn't. signature.asc Description: Digital signature
Bug#363229: xserver-xorg: No way to set the XKB data directory
On Wed, Apr 19, 2006 at 01:06:28AM +0300, Shai Berger wrote: [...] As things are documented, this should be doable without the command-line option -- via the environment variable, that is, $ startx -- :3 -xkbdir XXX should be equivalent to $ XKBPATH=XXX startx -- :3 And the way I see things, it is indeed equivalent -- the environment variable is ignored. Did you remove this also? As explained in README.Debian, this XKBPATH variable is a Debian extension which had been added to ease testing local changes in XKB files, it has not been reported upstream. As -xkbdir option is dropped, a simple solution would indeed be to let X honor XKBPATH too, but I do not know how yet. Denis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#363229: xserver-xorg: No way to set the XKB data directory
Package: xserver-xorg Version: 1:7.0.12 Severity: normal Following the transition to xkb-data and xkeyboard-config, I was told to put my customized xkb files aside and make the server use them by setting the XKBPATH. However, setting the XKBPATH variable didn't work (seems like the variable was ignored; I tried setting it in a user's login shell as well as root's shell, then restarting X). Then I tried the other method referred to in xkb-data's README.Debian, that of passing a -xkbdir to the server. The server did not recognize this flag (and gave me a list of the flags it did recognize...). Thus, it seems my only option would be to customize the files at their new location. This seems like a weird regression, because the net is full of reports where these things worked for people. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages xserver-xorg depends on: ii debconf 1.4.72 Debian configuration management sy ii x11-common1:7.0.12 X Window System (X.Org) infrastruc ii xbase-clients 1:7.0.0-4 miscellaneous X clients ii xkb-data 0.8-5 X Keyboard Extension (XKB) configu ii xserver-xorg-core 1:1.0.2-4 X.Org X server -- core server ii xserver-xorg-input-al 1:7.0.12 the X.Org X server -- input driver ii xserver-xorg-input-ev 1:1.0.0.5-2X.Org X server -- evdev input driv ii xserver-xorg-input-kb 1:1.0.1.3-2X.Org X server -- keyboard input d ii xserver-xorg-input-mo 1:1.0.4-2 X.Org X server -- mouse input driv ii xserver-xorg-video-al 1:7.0.12 the X.Org X server -- output drive ii xserver-xorg-video-ap 1:1.0.1.5-2X.Org X server -- APM display driv ii xserver-xorg-video-ar 1:0.5.0.5-2X.Org X server -- ark display driv ii xserver-xorg-video-at 1:6.5.7.3-3X.Org X server -- ATI display driv ii xserver-xorg-video-ch 1:1.0.1.3-3X.Org X server -- Chips display dr ii xserver-xorg-video-ci 1:1.0.0.5-2X.Org X server -- Cirrus display d ii xserver-xorg-video-cy 1:1.0.0.5-2X.Org X server -- Cyrix display dr ii xserver-xorg-video-du 1:0.1.0.5-2X.Org X server -- dummy display dr ii xserver-xorg-video-fb 1:0.1.0.5-2X.Org X server -- fbdev display dr ii xserver-xorg-video-gl 1:1.0.1.3-2X.Org X server -- Glint display dr ii xserver-xorg-video-i1 1:1.1.0.5-2X.Org X server -- i128 display dri ii xserver-xorg-video-i7 1:1.0.0.5-2X.Org X server -- i740 display dri ii xserver-xorg-video-i8 1:1.5.1.0-2X.Org X server -- Intel i8xx, i9xx ii xserver-xorg-video-im 1:1.0.0.5-2X.Org X server -- IMSTT display dr ii xserver-xorg-video-mg 1:1.2.1.3.dfsg.1-2 X.Org X server -- MGA display driv ii xserver-xorg-video-ne 1:1.0.0.5-2X.Org X server -- Neomagic display ii xserver-xorg-video-ne 1:0.1.4.1-3X.Org X server -- Newport display ii xserver-xorg-video-ns 1:2.7.6.5-2X.Org X server -- NSC display driv ii xserver-xorg-video-nv 1:1.0.1.5-2X.Org X server -- NV display drive ii xserver-xorg-video-re 1:4.0.1.3.dfsg.1-2 X.Org X server -- Rendition displa ii xserver-xorg-video-s3 1:1.8.6.5-2X.Org X server -- S3 ViRGE display ii xserver-xorg-video-sa 1:2.0.2.3-4X.Org X server -- Savage display d ii xserver-xorg-video-si 1:1.3.1.5-3X.Org X server -- SiliconMotion di ii xserver-xorg-video-si 1:0.8.1.3-2X.Org X server -- SiS display driv ii xserver-xorg-video-si 1:0.7.1.3-2X.Org X server -- SiS USB display ii xserver-xorg-video-td 1:1.1.1.3-3X.Org X server -- tdfx display dri ii xserver-xorg-video-tg 1:1.0.0.5-3X.Org X server -- TGA display driv ii xserver-xorg-video-tr 1:1.0.1.2-2X.Org X server -- Trident display ii xserver-xorg-video-ts 1:1.0.0.5-2X.Org X server -- Tseng display dr ii xserver-xorg-video-ve 1:1.0.1.3-2X.Org X server -- VESA display dri ii xserver-xorg-video-vg 1:4.0.0.5-2X.Org X server -- VGA display driv ii xserver-xorg-video-vi 1:0.1.33.2-2 X.Org X server -- VIA display driv ii xserver-xorg-video-vm 1:10.11.1.3-2 X.Org X server -- VMware display d ii xserver-xorg-video-vo 1:1.0.0.5-2X.Org X server -- Voodoo display d Versions of packages xserver-xorg recommends: ii discover1 1.7.18hardware identification system ii laptop-detect 0.12.1attempt to detect a laptop ii mdetect0.5.2.1 mouse device autodetection tool ii xresprobe 0.4.23debian1 X Resolution Probe -- debconf information: * xserver-xorg/multiple_possible_x-drivers:
