[Mageia-dev] ANN: For the brave. systemd v185 in cauldron updates_testing
mageia at colin.guthr.ie
Tue Jun 19 10:07:46 CEST 2012
'Twas brillig, and JA Magallón at 18/06/12 22:47 did gyre and gimble:
> On 06/18/2012 11:28 PM, JA Magallón wrote:
>> Sorry for the delay, I've been busy with end-of-term festivals in
>> my children' schools ;)...
>>>>> - keyboard layout under Gnome got reset to English (from Spanish).
>>>>> Changed manually under
>>>>> system settings and fine again.
>> One addtional problem is that GDM starts with english keyboard which
>> is a problem for passwords with non alpha-num chars... :).
>>>> Interesting. Does this new setting survive a reboot? Does the new
>>>> mapping work at the system level (i.e. is the layout respected in GDM)?
>> Yep, the setting survives a reboot for the user that changed it, but
>> as I said above it does not change GDM settings. I did not try to do it
>> with system tools, just user preferences.
>> And keymap is OK in virtual consoles.
>>>> Do you have a /etc/vconsole.conf file?
>> Nop, I have not. I think system settings were in /etc/sysconfig/keyboard.
>>> OK, so I don't really understand why it's broken. I think it's maybe a
>>> regression in that X is no longer inheriting settings from the console,
>>> but I think longer term this is a valid thing (maybe there will not be a
>>> console to inherit from in the future?)
>>> So, it seems that systemd-localed will write an Xorg snippet into
>>> /etc/X11/xorg.conf.d/00-keyboard.conf when the keyboard is set. Thus
>>> your setting of it via the Gnome System Settings will have written this
>>> file (can you confirm it exists?) and it will remain there for the
>>> remaining boots.
>> This file does not exist in my box, I just used user prefs to change
>> the map, not sytem ones.
>>> Longer term, we need to make sure the installer runs this daemon for
>>> fresh installs. And perhaps we should run it on upgrade automatically
>>> too to ensure it's written as needed.
>> I will try to write an /etc/vconsole.conf and see if it works.
>> Perhaps the fix is just to write it from /etc/syscofig/keyboard...
> This file did not work for GDM.
Yup, I realise now that it's only good for the console. I think in the
past we must have somehow inherited from the console but that's no
longer working (I could be wrong on this one).
> So i checked systemd-localed, it was not started and started it manually,
> and then copied my settings to system in gnome settings tool.
> That made the file in xorg.conf.d appear, and GDM was OK.
You shouldn't actually need to start it manually. It should start
on-demand (it's dbus activated). That worked here.
Strangely, I wasn't able to write the file immediately It somehow
detected my system settings as the same as my local settings and refused
to write a file. I think perhaps that my "local" settings were a little
bit broken tho' (years of upgrades I guess) and adding a layout,
removing it and then copying did indeed write the xorg.conf.d snippet.
> Perhaps udev/dbus do not talk to X server anymore about keyboard layout.
Well I'm not sure at what point X will talk to udev or dbus about this?
Maybe udev no longer carries locale information in it's db? Maybe it's
simply due to X being linked against an old libudev at the moment (until
this lands in the release repo)? That said I don't see any layout
information in my udev database for my console on mga2 machines. So I'm
not really sure how this stuff works to be honest.
> My settiongs in xorg.conf were:
> Section "InputDevice"
> Identifier "keyboard"
> Driver "evdev"
> # Option "XkbLayout" "es"
> # Option "XkbModel" "pc105"
> # Option "XkbOptions" ""
Well these options are commented out so won't have any effect. Most of
the time xorg.conf isn't even needed any more, hence the desire to use
the xorg.conf.d folder instead.
> File generated by localed is:
> # Read and parsed by systemd-localed. It's probably wise not to edit
> this file
> # manually too freely.
> Section "InputClass"
> Identifier "system-keyboard"
> MatchIsKeyboard "on"
> Option "XkbLayout" "es"
Yup that seems correct.
Likely we'll need to update things accordingly to deal with this, but on
the whole I'm sure we'll get it working smoothly :)
Tribalogic Limited http://www.tribalogic.net/
Mageia Contributor http://www.mageia.org/
PulseAudio Hacker http://www.pulseaudio.org/
Trac Hacker http://trac.edgewall.org/
More information about the Mageia-dev