http://bugzilla.novell.com/show_bug.cgi?id=579119 http://bugzilla.novell.com/show_bug.cgi?id=579119#c9 Stefan Dirsch <sndirsch@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|sndirsch@novell.com | --- Comment #9 from Stefan Dirsch <sndirsch@novell.com> 2010-02-26 14:14:32 UTC --- (In reply to comment #8)
YaST cannot do such dark magic. If something should be changed in such code we well not know about it.
Well, thinking about it once more, it might not be a good idea to restart haldaemon on top of a Xsession (not sure what will happen then), but you need to do this so that the new HAL keyboard settings get active. Additionally you need to restart the Xserver afterwards. The only safe way I see this all can happen is in /etc/init.d/xdm script.
BTW, do I understand it correct that if user would use login manager himself, it would work for him? Than we can declare it as invalid, I think.
You mean user restarts login manager himself? Just using a login manager doesn't help of course. I don't see how to resolve that issue other than informing that (s)he needs to restart xdm script. Well, it wasn't my idea to reintroduce static X11 keyboard configuration in YaST2. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.