[Bug 589904] New: setting numlock status to on for KDM in YAST2 does not stick
http://bugzilla.novell.com/show_bug.cgi?id=589904 http://bugzilla.novell.com/show_bug.cgi?id=589904#c0 Summary: setting numlock status to on for KDM in YAST2 does not stick Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: i686 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers@suse.de ReportedBy: mrkfbrn@yahoo.co.nz QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.0) Gecko/20100115 SUSE/3.6.0-1.2 Firefox/3.6 (.NET CLR 3.5.30729) Have numlock status set to on in my Bios settings on an IBM Thinkcentre. Booting - when reaching the KDM login screen numlock is not turned on. Going in to YAST2 > System > /etc/sysconfig Editor > KBD_NUMLOCK this is set to "BIOS" which obviously does not seem to be working. Change setting to "YES" and numlock is set to "on" when reaching KDM screen - but does not work 100% of the time. Sometimes, for an unknown reason the numlock is left turned off. No apparent reason for this behaviour. KDM4 on Opensuse 11.2 with KDE 4.3.5 Reproducible: Always -- 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=589904
http://bugzilla.novell.com/show_bug.cgi?id=589904#c1
--- Comment #1 from Mark Fairbairn
http://bugzilla.novell.com/show_bug.cgi?id=589904
http://bugzilla.novell.com/show_bug.cgi?id=589904#c2
Lubos Lunak
http://bugzilla.novell.com/show_bug.cgi?id=589904
http://bugzilla.novell.com/show_bug.cgi?id=589904#c3
--- Comment #3 from Mark Fairbairn
http://bugzilla.novell.com/show_bug.cgi?id=589904
http://bugzilla.novell.com/show_bug.cgi?id=589904#c4
Mark Fairbairn
http://bugzilla.novell.com/show_bug.cgi?id=589904
http://bugzilla.novell.com/show_bug.cgi?id=589904#c5
Lubos Lunak
http://bugzilla.novell.com/show_bug.cgi?id=589904
http://bugzilla.novell.com/show_bug.cgi?id=589904#c6
Stefan Dirsch
http://bugzilla.novell.com/show_bug.cgi?id=589904
http://bugzilla.novell.com/show_bug.cgi?id=589904#c
Stefan Dirsch
http://bugzilla.novell.com/show_bug.cgi?id=589904
http://bugzilla.novell.com/show_bug.cgi?id=589904#c7
Stefan Dirsch
http://bugzilla.novell.com/show_bug.cgi?id=589904
http://bugzilla.novell.com/show_bug.cgi?id=589904#c8
Mark Fairbairn
http://bugzilla.novell.com/show_bug.cgi?id=589904
http://bugzilla.novell.com/show_bug.cgi?id=589904#c9
Stefan Dirsch
hmmmm . .. this sporadic issue has happened to me three times in the last five boots now. How do I verify /var/run/numlock-on exists when numlock is not turned on?
?!? Simply check if that file exits. Sorry, I don't know how to explain it better. -- 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=589904
http://bugzilla.novell.com/show_bug.cgi?id=589904#c10
Mark Fairbairn
http://bugzilla.novell.com/show_bug.cgi?id=589904
http://bugzilla.novell.com/show_bug.cgi?id=589904#c11
Stefan Dirsch
OK. My last boot numlock was not turned on. File /var/run/numlock-on exists but is an empty file. Is this correct?
File (empty is fine) exists but numlock was not turned on? That's weird, since in that case numlockx should be running. /etc/X11/xdm/Xsetup: [...] # # Enable Numlock if set # if test -r /var/run/numlock-on && type -p numlockx > /dev/null ; then numlockx on fi What happens when you run these commands manually in a terminal? -- 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=589904
http://bugzilla.novell.com/show_bug.cgi?id=589904#c12
Stefan Dirsch
participants (1)
-
bugzilla_noreply@novell.com