Re: [arch-dev-public] [arch-commits] CVS update of extra/x11/xorg-server (PKGBUILD xorg-server.install)
Am Mittwoch, 20. Februar 2008 20:50:56 schrieb Alexander Baldeck:
+ echo ":: ATTENTION!" + echo ":: Since xorg-server version 1.4.0.90-7 hal support has" + echo ":: been enabled. By default keyboard layouts and variants" + echo ":: will now be overridden by hal. Please modfiy" + echo "::" + echo ":: /etc/hal/fdi/policy/11-xkeyboard.fdi"
Do you have some additional information why this change was made? This sound quite confusing to me. Is there no way to keep xorg.conf controlling which keyboard layout is set? -- archlinux.de
2008/2/21, Pierre Schmitz <pierre@archlinux.de>:
Am Mittwoch, 20. Februar 2008 20:50:56 schrieb Alexander Baldeck:
+ echo ":: ATTENTION!" + echo ":: Since xorg-server version 1.4.0.90-7 hal support has" + echo ":: been enabled. By default keyboard layouts and variants" + echo ":: will now be overridden by hal. Please modfiy" + echo "::" + echo ":: /etc/hal/fdi/policy/11-xkeyboard.fdi"
Do you have some additional information why this change was made? This sound quite confusing to me. Is there no way to keep xorg.conf controlling which keyboard layout is set?
Yeah, defining layouts & variants somewhere deep in hal config tree is ugly. and I guess this may introduce more keyboard-related bugs :-/ -- Roman Kyrylych (Роман Кирилич)
Roman Kyrylych wrote:
2008/2/21, Pierre Schmitz <pierre@archlinux.de>:
Am Mittwoch, 20. Februar 2008 20:50:56 schrieb Alexander Baldeck:
+ echo ":: ATTENTION!" + echo ":: Since xorg-server version 1.4.0.90-7 hal support has" + echo ":: been enabled. By default keyboard layouts and variants" + echo ":: will now be overridden by hal. Please modfiy" + echo "::" + echo ":: /etc/hal/fdi/policy/11-xkeyboard.fdi"
Do you have some additional information why this change was made? This sound quite confusing to me. Is there no way to keep xorg.conf controlling which keyboard layout is set?
Yeah, defining layouts & variants somewhere deep in hal config tree is ugly. and I guess this may introduce more keyboard-related bugs :-/
This is why I pushed this to testing for now. Seems as if we're going to have to wait for a better xorg.conf like implementation until a later xorg-server release which shouldn't be too far away from now. Anyway, I cannot yet confirm fully whether the keyboard behavior is not influenced by xorg.conf as I don't use any other layout than US/pc105 which it defaults to. Looks like it detects the keyboard on my mac mini perfectly fine though which is after all a little different from regular pc keyboards. I'll recheck and keep you posted. Cheers, -G
2008/2/21, Alexander Baldeck <kth5@archlinuxppc.org>:
Roman Kyrylych wrote:
2008/2/21, Pierre Schmitz <pierre@archlinux.de>:
Am Mittwoch, 20. Februar 2008 20:50:56 schrieb Alexander Baldeck:
+ echo ":: ATTENTION!" + echo ":: Since xorg-server version 1.4.0.90-7 hal support has" + echo ":: been enabled. By default keyboard layouts and variants" + echo ":: will now be overridden by hal. Please modfiy" + echo "::" + echo ":: /etc/hal/fdi/policy/11-xkeyboard.fdi"
Do you have some additional information why this change was made? This sound quite confusing to me. Is there no way to keep xorg.conf controlling which keyboard layout is set?
Yeah, defining layouts & variants somewhere deep in hal config tree is ugly. and I guess this may introduce more keyboard-related bugs :-/
This is why I pushed this to testing for now. Seems as if we're going to have to wait for a better xorg.conf like implementation until a later xorg-server release which shouldn't be too far away from now.
Anyway, I cannot yet confirm fully whether the keyboard behavior is not influenced by xorg.conf as I don't use any other layout than US/pc105 which it defaults to. Looks like it detects the keyboard on my mac mini perfectly fine though which is after all a little different from regular pc keyboards. I'll recheck and keep you posted.
I have the following configuration: Section "InputDevice" Identifier "Keyboard0" Driver "kbd" Option "XkbRules" "xorg" Option "XkbModel" "pc104" Option "XkbLayout" "us,ua,ru" Option "XkbVariant" ",winkeys,winkeys" Option "XkbOptions" "grp:ctrl_shift_toggle,eurosign:5,altwin:super_win,numpad:microsoft" EndSection It still works exactly as before in both GDM and Gnome. So I guess xorg.conf overrides hal config, and not the reverse as stated in .install. -- Roman Kyrylych (Роман Кирилич)
On Thu, 2008-02-21 at 18:56 +0200, Roman Kyrylych wrote:
I have the following configuration:
Section "InputDevice" Identifier "Keyboard0" Driver "kbd" Option "XkbRules" "xorg" Option "XkbModel" "pc104" Option "XkbLayout" "us,ua,ru" Option "XkbVariant" ",winkeys,winkeys" Option "XkbOptions" "grp:ctrl_shift_toggle,eurosign:5,altwin:super_win,numpad:microsoft" EndSection
It still works exactly as before in both GDM and Gnome. So I guess xorg.conf overrides hal config, and not the reverse as stated in .install.
I think hal is used to configure everything that wasn't configured from xorg.conf. When you take your USB keyboard out and stuff it in your laptop for example, it will get recognized by hal and configured by Xorg, but as it's a new device without configuration, there's no keyboard mapping done on the keyboard. I don't think messing around with fdi files is the way to configure Xorg, that's why you have xorg.conf.
2008/2/21, Jan de Groot <jan@jgc.homeip.net>:
On Thu, 2008-02-21 at 18:56 +0200, Roman Kyrylych wrote:
I have the following configuration:
Section "InputDevice" Identifier "Keyboard0" Driver "kbd" Option "XkbRules" "xorg" Option "XkbModel" "pc104" Option "XkbLayout" "us,ua,ru" Option "XkbVariant" ",winkeys,winkeys" Option "XkbOptions" "grp:ctrl_shift_toggle,eurosign:5,altwin:super_win,numpad:microsoft" EndSection
It still works exactly as before in both GDM and Gnome. So I guess xorg.conf overrides hal config, and not the reverse as stated in .install.
I think hal is used to configure everything that wasn't configured from xorg.conf. When you take your USB keyboard out and stuff it in your laptop for example, it will get recognized by hal and configured by Xorg, but as it's a new device without configuration, there's no keyboard mapping done on the keyboard. I don't think messing around with fdi files is the way to configure Xorg, that's why you have xorg.conf.
Makes sense. post_install should be corrected to not scare&confuse users with non-removable keyboards. ;-) -- Roman Kyrylych (Роман Кирилич)
Am Donnerstag, 21. Februar 2008 21:07:21 schrieb Roman Kyrylych:
Makes sense. post_install should be corrected to not scare&confuse users with non-removable keyboards. ;-)
No, the new xorg ignores xorg.conf and if you do not change that hal file you'll end up with an us layout. It should be the other way round: for keyboards that are not configured via xorg.conf hal should be used. (Isn't it possible to detect the layout? atm 'us' is the default) -- archlinux.de
2008/2/21, Pierre Schmitz <pierre@archlinux.de>:
Am Donnerstag, 21. Februar 2008 21:07:21 schrieb Roman Kyrylych:
Makes sense. post_install should be corrected to not scare&confuse users with non-removable keyboards. ;-)
No, the new xorg ignores xorg.conf and if you do not change that hal file you'll end up with an us layout. It should be the other way round: for keyboards that are not configured via xorg.conf hal should be used. (Isn't it possible to detect the layout? atm 'us' is the default)
Didn't you see my previous message? Xorg *does not* ignore xorg.conf here. I din't even touch hal's file. -- Roman Kyrylych (Роман Кирилич)
Am Donnerstag, 21. Februar 2008 22:02:35 schrieb Roman Kyrylych:
Didn't you see my previous message? Xorg *does not* ignore xorg.conf here. I din't even touch hal's file.
Nice for you, but that did not work for me and there are some users reporting that problem, too. -- archlinux.de
2008/2/21, Pierre Schmitz <pierre@archlinux.de>:
Am Donnerstag, 21. Februar 2008 22:02:35 schrieb Roman Kyrylych:
Didn't you see my previous message? Xorg *does not* ignore xorg.conf here. I din't even touch hal's file.
Nice for you, but that did not work for me and there are some users reporting that problem, too.
Could you please post your xorg.conf section? And is your keyboard PS/2 or USB? -- Roman Kyrylych (Роман Кирилич)
Am Donnerstag, 21. Februar 2008 22:46:35 schrieb Roman Kyrylych:
2008/2/21, Pierre Schmitz <pierre@archlinux.de>:
Am Donnerstag, 21. Februar 2008 22:02:35 schrieb Roman Kyrylych:
Didn't you see my previous message?
Xorg *does not* ignore xorg.conf here. I din't even touch hal's file.
Nice for you, but that did not work for me and there are some users reporting that problem, too.
Could you please post your xorg.conf section? And is your keyboard PS/2 or USB?
Section "InputDevice" Identifier "Keyboard0" Driver "kbd" Option "XkbLayout" "de" Option "XkbVariant" "nodeadkeys" EndSection should be PS/2 -- archlinux.de
2008/2/21, Pierre Schmitz <pierre@archlinux.de>:
Am Donnerstag, 21. Februar 2008 22:46:35 schrieb Roman Kyrylych:
2008/2/21, Pierre Schmitz <pierre@archlinux.de>:
Am Donnerstag, 21. Februar 2008 22:02:35 schrieb Roman Kyrylych:
Didn't you see my previous message?
Xorg *does not* ignore xorg.conf here. I din't even touch hal's file.
Nice for you, but that did not work for me and there are some users reporting that problem, too.
Could you please post your xorg.conf section? And is your keyboard PS/2 or USB?
Section "InputDevice" Identifier "Keyboard0" Driver "kbd"
Option "XkbLayout" "de" Option "XkbVariant" "nodeadkeys" EndSection
should be PS/2
Hm, I can think only about adding Option "XkbRules" "xorg" Option "XkbModel" "pc104" *shrugs* That's weird that it works on my system but not on others'. -- Roman Kyrylych (Роман Кирилич)
Am Thu, 21 Feb 2008 22:41:49 +0100 schrieb Pierre Schmitz <pierre@archlinux.de>:
Am Donnerstag, 21. Februar 2008 22:02:35 schrieb Roman Kyrylych:
Didn't you see my previous message? Xorg *does not* ignore xorg.conf here. I din't even touch hal's file.
Nice for you, but that did not work for me and there are some users reporting that problem, too.
completely broken for me too now. urgh. revert it. xorg.conf is not recognised anymore. Section "InputDevice" Identifier "Keyboard1" Driver "keyboard" Option "XkbModel" "cherrybluea" Option "XkbLayout" "de(nodeadkeys)" Option "XkbOptions" "compose:rwin" EndSection USB keyboard -Andy
On Sat, 2008-02-23 at 13:04 +0100, Andreas Radke wrote:
Am Thu, 21 Feb 2008 22:41:49 +0100 schrieb Pierre Schmitz <pierre@archlinux.de>:
Am Donnerstag, 21. Februar 2008 22:02:35 schrieb Roman Kyrylych:
Didn't you see my previous message? Xorg *does not* ignore xorg.conf here. I din't even touch hal's file.
Nice for you, but that did not work for me and there are some users reporting that problem, too.
completely broken for me too now. urgh. revert it.
xorg.conf is not recognised anymore.
Section "InputDevice" Identifier "Keyboard1" Driver "keyboard" Option "XkbModel" "cherrybluea" Option "XkbLayout" "de(nodeadkeys)" Option "XkbOptions" "compose:rwin" EndSection
USB keyboard
Yes, this should be reverted. This new methods makes configuration inflexible, and adds some other disadvantages: - all keyboards have the same layout, no way to set an individual keyboard layout - keyboard layouts can only be configured by root, there's no way to configure keyboard layouts other than editing a root-owned fdi file I've attended a talk about XInput today, I heard things like "trainwreck" and "should be fixed somewhere next year", so please don't make things that are working now worse than they were before.
On Sun, Feb 24, 2008 at 03:02:43PM +0100, Jan de Groot wrote:
On Sat, 2008-02-23 at 13:04 +0100, Andreas Radke wrote:
Am Thu, 21 Feb 2008 22:41:49 +0100 schrieb Pierre Schmitz <pierre@archlinux.de>:
Am Donnerstag, 21. Februar 2008 22:02:35 schrieb Roman Kyrylych:
Didn't you see my previous message? Xorg *does not* ignore xorg.conf here. I din't even touch hal's file.
Nice for you, but that did not work for me and there are some users reporting that problem, too.
completely broken for me too now. urgh. revert it.
xorg.conf is not recognised anymore.
Section "InputDevice" Identifier "Keyboard1" Driver "keyboard" Option "XkbModel" "cherrybluea" Option "XkbLayout" "de(nodeadkeys)" Option "XkbOptions" "compose:rwin" EndSection
USB keyboard
lol, I just figured out why this worked for me too (like Roman). I didn't have hal running :D
Yes, this should be reverted. This new methods makes configuration inflexible, and adds some other disadvantages: - all keyboards have the same layout, no way to set an individual keyboard layout - keyboard layouts can only be configured by root, there's no way to configure keyboard layouts other than editing a root-owned fdi file
Hmm, how could keyboard layout be configured before? Editing xorg.conf requires root access too. And setxkbmap seems to be sill working. I had no luck with xmodmap though.
-----Oorspronkelijk bericht----- Van: arch-dev-public-bounces@archlinux.org [mailto:arch-dev-public- bounces@archlinux.org] Namens Xavier Verzonden: zondag 24 februari 2008 17:46 Aan: Public mailing list for ArchLinux development Onderwerp: Re: [arch-dev-public] [arch-commits] CVS update of extra/x11/xorg-server (PKGBUILD xorg-server.install)
Hmm, how could keyboard layout be configured before? Editing xorg.conf requires root access too. And setxkbmap seems to be sill working. I had no luck with xmodmap though.
Xorg -xf86configfile ~/xorg.conf ? There's no way to specify a different hal daemon where you have the possibility to specify a different config file.
On Sun, Feb 24, 2008 at 03:02:43PM +0100, Jan de Groot wrote:
Yes, this should be reverted. This new methods makes configuration inflexible, and adds some other disadvantages: - all keyboards have the same layout, no way to set an individual keyboard layout
Is that really the case? I just felt on that post on bbs : http://bbs.archlinux.org/viewtopic.php?pid=336100#p336100 Looks like you can specify your keyboard, at least with the info.product string. Maybe there are other fields to make the distinction between two identical keyboards, but well I fail to see when someone would want to do that anyway :)
On Thu, Feb 21, 2008 at 12:19:26AM +0100, Pierre Schmitz wrote:
Am Mittwoch, 20. Februar 2008 20:50:56 schrieb Alexander Baldeck:
+ echo ":: ATTENTION!" + echo ":: Since xorg-server version 1.4.0.90-7 hal support has" + echo ":: been enabled. By default keyboard layouts and variants" + echo ":: will now be overridden by hal. Please modfiy" + echo "::" + echo ":: /etc/hal/fdi/policy/11-xkeyboard.fdi"
Do you have some additional information why this change was made? This sound quite confusing to me. Is there no way to keep xorg.conf controlling which keyboard layout is set?
I was running with this version, because it's still in the repo. I use the dvorak keyboard. And my Super key would get stuck every so often. I tried changing the keymap with setxkbmap and also in the hal config but it always froze. Only after a downgrade did it go away. Jason
Pierre Schmitz schrieb:
Am Mittwoch, 20. Februar 2008 20:50:56 schrieb Alexander Baldeck:
+ echo ":: ATTENTION!" + echo ":: Since xorg-server version 1.4.0.90-7 hal support has" + echo ":: been enabled. By default keyboard layouts and variants" + echo ":: will now be overridden by hal. Please modfiy" + echo "::" + echo ":: /etc/hal/fdi/policy/11-xkeyboard.fdi"
Do you have some additional information why this change was made? This sound quite confusing to me. Is there no way to keep xorg.conf controlling which keyboard layout is set?
Just a quick note: With the new xorg-server, I cannot get a de layout anymore: hal overrides xorg.conf (as stated in Xorg.0.log) and hal completely ignores the settings in the fdi file, it always gives me a us layout. I am using the extra/xorg-server version again now.
2008/3/1, Thomas Bächler <thomas@archlinux.org>:
Pierre Schmitz schrieb:
Am Mittwoch, 20. Februar 2008 20:50:56 schrieb Alexander Baldeck:
+ echo ":: ATTENTION!" + echo ":: Since xorg-server version 1.4.0.90-7 hal support has" + echo ":: been enabled. By default keyboard layouts and variants" + echo ":: will now be overridden by hal. Please modfiy" + echo "::" + echo ":: /etc/hal/fdi/policy/11-xkeyboard.fdi"
Do you have some additional information why this change was made? This sound quite confusing to me. Is there no way to keep xorg.conf controlling which keyboard layout is set?
Just a quick note: With the new xorg-server, I cannot get a de layout anymore: hal overrides xorg.conf (as stated in Xorg.0.log) and hal completely ignores the settings in the fdi file, it always gives me a us layout. I am using the extra/xorg-server version again now.
Could everyone who experience this problem please try what is proposed here: http://bugs.archlinux.org/task/9563#comment25506 (I'm unable to test this because hal doesn't override xorg.conf on my system). -- Roman Kyrylych (Роман Кирилич)
participants (8)
-
Alexander Baldeck
-
Andreas Radke
-
Jan de Groot
-
Jason Chu
-
Pierre Schmitz
-
Roman Kyrylych
-
Thomas Bächler
-
Xavier