NUMLock pad is essentially inoperative in opensuse 12.3

NumLock is operative only for a few minutes after opensuse 12.3 installs; then the numbers pad is inoperative. Only the numbers at the top of the keyboard are functional.
It happened also with opensuse 12.2 and I expected it to get corrected but it never was.
Will it get solved in 12.3?
Any suggestions/ideas?

On Thu, 23 May 2013 21:06:01 +0000, scnovell wrote:

> NumLock is operative only for a few minutes after opensuse 12.3
> installs; then the numbers pad is inoperative. Only the numbers at the
> top of the keyboard are functional.
> It happened also with opensuse 12.2 and I expected it to get corrected
> but it never was.
> Will it get solved in 12.3?
> Any suggestions/ideas?

It works fine here, so it would be useful if you told us what kind of
hardware you’re using and what DE you’re using.

I use the numpad all the time on 12.2 here, multiple systems, and it’s
never just “switched off” never to return.

Jim


Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

If you think this is a bug in openSUSE, have you reported it? The developers can’t fix something that’s never mentioned to them, and they aren’t psychics. :wink:

https://en.opensuse.org/Bugzilla

Jim’s probably right though, no one else has mentioned this before. Have you tested a different keyboard to see if that’s the source of the problem? What DE are you using?

NUMLock working as designed here too.
openSUSE 12.3 ← (did that w/NUMLock)
KDE

I did have to set KDE to turn on NumLock at KDE startup. With that set, it is fine here. I don’t know what the equivalent setting is in Gnome.

on openSUSE 12.3/GNOME we need to open dconf-editor and navigate to org.gnome.settings-daemon.peripherals.keyboard and configure the settings

I will try to answer most of the comments posted.
Currently I use opensuse 12.3 with 64 bit multicore [6] amd hardware with gnome.

However, the problem also occurred with opensuse 12.2 with 32 bit hardware and different hardware including keyboard; I think we can eliminate hardware and look toward the opensuse software as the probable culprit].
I did not report it as a bug as I wasn’t sure it was a bug or something I was doing. I still am not sure… but,
I am interested in the constructive reply provided by Vazhavandan it looks promising but I would never have thought of it as a solution … where did it come from?

‘on openSUSE 12.3/GNOME we need to open dconf-editor and navigate to org.gnome.settings-daemon.peripherals.keyboard and configure the settings’

looked for a dconf-editor file - none found!
then tried open dconf-editor no good; went to
install dconf-editor which did give some result except the `install requires a number of arguments which did not immediately mean much to me - so rather than blindly plough ahead I’d rather ask for further - help!

Thanks for input[s]

On Fri, 24 May 2013 22:16:01 +0000, scnovell wrote:

> looked for a dconf-editor file - none found!

dconf-editor is a program, you need to install it through YaST or zypper.

Jim


Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

I first saw this with 12.2 .

My own guess is that it is the kernel, and probably affects all distros using the same kernel series.

Try left Win key ==> type install ==> invoke YaST installer==>and try this

http://paste.opensuse.org/images/99105069.png

After installing dconf-editor

try
left win key/Alt+F1 ==> type dconf and launch the application ==> navigate to the below schemas and play around.
You also search for keys by pressing ctrl+f
what else can it do ?
some examples :- Ultra Random Thoughts: What is dconf editor, how is it useful ?

http://paste.opensuse.org/images/45403973.png

Thanks for the dconf details I will be trying them soon and hope to get the situation righted.
I don’t quite understand why opensuse 12.x would have such a hole? I will try to report it.
By the way I was wrong the lack of numpad is not related to time - most likely to initial use - in my case entering the 3 pw numbers - works then no more.

Yes, there was a bug when 12.3 was released that Numlock wasn’t automatically activated on boot, but that was fixed in April already. See https://bugzilla.novell.com/show_bug.cgi?id=746595.
And since then it works fine for me.

Which version of the package “systemd” do you have installed?
Which setting for KBD_NUMLOCK do you have in /etc/sysconfig/keyboard?

You should be able to activate it manually by pressing the NumLock key regardless of the settings, of course. Does that work for you?