[Bug 579119] New: yast2 keyboard does not update /etc/hal/fdi/policy/20thirdparty/11-keymap.fdi
http://bugzilla.novell.com/show_bug.cgi?id=579119 http://bugzilla.novell.com/show_bug.cgi?id=579119#c0 Summary: yast2 keyboard does not update /etc/hal/fdi/policy/20thirdparty/11-keymap.fdi Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: i586 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: phdm@macqel.be QAContact: jsrain@novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.2) Gecko/20090730 SUSE/3.5.2-2.1 Firefox/3.5.2 I use 'yast(2) keyboard' to select my keyboard layout. After that, /etc/sysconfig/keyboard contains my newly selected keyboard layout, but /etc/hal/fdi/policy/20thirdparty/11-keymap.fdi still contains an old (and wrong, of course) keyboard layout. When I then (re)start 'X' to get a pure X server, the keyboard is wrong. Reproducible: Always Steps to Reproduce: 1.type init 3, to stop the xdm system 2.select another keyboard layout using 'yast keyboard' 3.check if /etc/hal/fdi/policy/20thirdparty/11-keymap.fdi is updated. It is not. Also, if I remove /etc/hal/fdi/policy/20thirdparty/11-keymap.fdi before calling 'yast keyboard', /etc/hal/fdi/policy/20thirdparty/11-keymap.fdi is not created. -- 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.
http://bugzilla.novell.com/show_bug.cgi?id=579119 http://bugzilla.novell.com/show_bug.cgi?id=579119#c Philippe De Muyter <phdm@macqel.be> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High Severity|Normal |Major -- 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.
http://bugzilla.novell.com/show_bug.cgi?id=579119 http://bugzilla.novell.com/show_bug.cgi?id=579119#c1 --- Comment #1 from Philippe De Muyter <phdm@macqel.be> 2010-02-11 19:11:51 UTC --- I have now found that there is a script called /etc/X11/xdm/keytable4hal that does create /etc/hal/fdi/policy/20thirdparty/11-keymap.fdi with the changed keyboard layout info. I can solve my problem if I call that script after 'yast keyboard', but I still think that it should be more straightforward. -- 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.
http://bugzilla.novell.com/show_bug.cgi?id=579119 http://bugzilla.novell.com/show_bug.cgi?id=579119#c yang xiaoyu <xyyang@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xyyang@novell.com AssignedTo|bnc-team-screening@forge.pr |sndirsch@novell.com |ovo.novell.com | -- 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.
http://bugzilla.novell.com/show_bug.cgi?id=579119 http://bugzilla.novell.com/show_bug.cgi?id=579119#c2 Stefan Dirsch <sndirsch@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|sndirsch@novell.com |bnc-team-screening@forge.pr | |ovo.novell.com --- Comment #2 from Stefan Dirsch <sndirsch@novell.com> 2010-02-16 17:20:53 UTC --- This script is called in /etc/init.d/xdm. So "rcxdm restart" fixes that issue as well. In case we reintroduce the YaST module for the keyboard on Linux console the script needs to be run by YaST. Reassigning. -- 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.
http://bugzilla.novell.com/show_bug.cgi?id=579119 http://bugzilla.novell.com/show_bug.cgi?id=579119#c3 --- Comment #3 from Philippe De Muyter <phdm@macqel.be> 2010-02-16 22:50:33 UTC --- Actually, I start my X server using directly the command 'X -ac -retro', because I only want to make an X server. Also, the script is currently only called by 'xdm start', so it won't be invoked after CTRL-ALT-BACKSPACE, which only restarts the X server. -- 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.
http://bugzilla.novell.com/show_bug.cgi?id=579119 http://bugzilla.novell.com/show_bug.cgi?id=579119#c yang xiaoyu <xyyang@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |yast2-maintainers@suse.de |ovo.novell.com | -- 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.
http://bugzilla.novell.com/show_bug.cgi?id=579119 http://bugzilla.novell.com/show_bug.cgi?id=579119#c Lukas Ocilka <locilka@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|yast2-maintainers@suse.de |jsuchome@novell.com -- 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.
http://bugzilla.novell.com/show_bug.cgi?id=579119 http://bugzilla.novell.com/show_bug.cgi?id=579119#c4 Jiří Suchomel <jsuchome@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |sndirsch@novell.com --- Comment #4 from Jiří Suchomel <jsuchome@novell.com> 2010-02-25 12:56:00 UTC --- (In reply to comment #2)
This script is called in /etc/init.d/xdm. So "rcxdm restart" fixes that issue as well. In case we reintroduce the YaST module for the keyboard on Linux console the script needs to be run by YaST. Reassigning.
Well, "rcxdm restart" will kill X session, which is not what we want to do from YaST. Do you know gentler solution? -- 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.
http://bugzilla.novell.com/show_bug.cgi?id=579119 http://bugzilla.novell.com/show_bug.cgi?id=579119#c5 Stefan Dirsch <sndirsch@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|sndirsch@novell.com | --- Comment #5 from Stefan Dirsch <sndirsch@novell.com> 2010-02-25 13:02:02 UTC --- (In reply to comment #4)
(In reply to comment #2)
This script is called in /etc/init.d/xdm. So "rcxdm restart" fixes that issue as well. In case we reintroduce the YaST module for the keyboard on Linux console the script needs to be run by YaST. Reassigning.
Well, "rcxdm restart" will kill X session, which is not what we want to do from YaST. Do you know gentler solution?
Well, another option would be to copy the code from /etc/init.d/xdm # use system keyboard as global X keyboard configuration if [ -x /etc/X11/xdm/keytable4hal ]; then if /etc/X11/xdm/keytable4hal; then /etc/init.d/haldaemon stop && \ rm -f /var/cache/hald/fdi-cache && \ /etc/init.d/haldaemon start fi fi -- 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.
http://bugzilla.novell.com/show_bug.cgi?id=579119 http://bugzilla.novell.com/show_bug.cgi?id=579119#c6 Jiří Suchomel <jsuchome@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |sndirsch@novell.com --- Comment #6 from Jiří Suchomel <jsuchome@novell.com> 2010-02-25 13:15:36 UTC --- Well, I do not see why YaST should do this. Could it be part of kdb script, which is restarted from YaST? Or some other stand alone one, that should YaST call directly? Are there any more conditions when it should be called and when not? -- 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.
http://bugzilla.novell.com/show_bug.cgi?id=579119 http://bugzilla.novell.com/show_bug.cgi?id=579119#c7 Stefan Dirsch <sndirsch@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|sndirsch@novell.com | --- Comment #7 from Stefan Dirsch <sndirsch@novell.com> 2010-02-25 13:34:41 UTC --- (In reply to comment #6)
Well, I do not see why YaST should do this.
Why not?
Could it be part of kbd script, which is restarted from YaST?
Why? It's X configuration, not Linux console keyboard.
Or some other stand alone one, that should YaST call directly? Are there any more conditions when it should be called and when not?
Not that I'm aware of. -- 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.
http://bugzilla.novell.com/show_bug.cgi?id=579119 http://bugzilla.novell.com/show_bug.cgi?id=579119#c8 Jiří Suchomel <jsuchome@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |sndirsch@novell.com --- Comment #8 from Jiří Suchomel <jsuchome@novell.com> 2010-02-26 13:46:22 UTC --- YaST cannot do such dark magic. If something should be changed in such code we well not know about it. Either do that action in some of the script already called by YaST (what about setxkbmap?), or create a standalone script from that that you are going to maintain and YaST could call such 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. -- 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.
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.
http://bugzilla.novell.com/show_bug.cgi?id=579119 http://bugzilla.novell.com/show_bug.cgi?id=579119#c10 Jiří Suchomel <jsuchome@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |lnussel@novell.com --- Comment #10 from Jiří Suchomel <jsuchome@novell.com> 2010-02-26 14:18:32 UTC --- Ludwig, I think you had some comments about the implementation, do you have any idea here? -- 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.
http://bugzilla.novell.com/show_bug.cgi?id=579119 http://bugzilla.novell.com/show_bug.cgi?id=579119#c11 Ludwig Nussel <lnussel@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW CC| |lnussel@novell.com Info Provider|lnussel@novell.com | --- Comment #11 from Ludwig Nussel <lnussel@novell.com> 2010-02-26 15:28:20 CET --- see bug 541351 -- 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.
http://bugzilla.novell.com/show_bug.cgi?id=579119 http://bugzilla.novell.com/show_bug.cgi?id=579119#c12 Jiří Suchomel <jsuchome@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|jsuchome@novell.com |sndirsch@novell.com --- Comment #12 from Jiří Suchomel <jsuchome@novell.com> 2010-03-09 12:28:42 UTC --- Well, according bug 541351, this seems to change anyway... Please tell me if YaST should do anything when 541351 is resolved. -- 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.
http://bugzilla.novell.com/show_bug.cgi?id=579119 http://bugzilla.novell.com/show_bug.cgi?id=579119#c13 Stefan Dirsch <sndirsch@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX AssignedTo|sndirsch@novell.com |jsuchome@novell.com --- Comment #13 from Stefan Dirsch <sndirsch@novell.com> 2010-03-09 15:10:51 UTC --- I don't see a solution for that issue for HAL. I don't think this is going to change for the successor. -- 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.
participants (1)
-
bugzilla_noreply＠novell.com