10:28 a.m.
I use the number pad a lot, and the number keys below the F-keys
only for the upper case; so I keep my bios set to boot up with it on, and
expect it to stay on, unless I tell it otherwise. Yet lately I've been
being pulled up sharp a dozen times a day and more to sudden large
inconveniences which turn out to mean numlock is off. What could be doing
this? How can I tell my PC that num*lock* means LOCK, e basta!?
--
Beartooth Staffwright, Neo-Redneck Not Quite Clueless Power User
Remember I have precious (very precious!) little idea where up is.
12:37 p.m.
I can't help I'm afraid, but I noticed that with fedora 22 on
my system, the keyboard always starts with the numlock LED
turned on, but the actual numlock keyboard state turned off.
Something is definitely "helpfully" screwing around with
this stuff, but I have no idea what is doing it.
Since I use kdm as a login manager, I found I could
add a command to /etc/kde/kdm/Xsetup to get it to run
as soon as the login screen starts:
xset led off
How to get it to actually turn numlock on, I don't
know (I prefer it off). Maybe something that uses
the XTEST extension could be used to simulate
pressing the numlock key.
12:02 a.m.
Did you try xconf-query?
man xconf-query
suomi
On 2015-08-23 19:37, Tom Horsley wrote:
I can't help I'm afraid, but I noticed that with fedora 22
on
my system, the keyboard always starts with the numlock LED
turned on, but the actual numlock keyboard state turned off.
Something is definitely "helpfully" screwing around with
this stuff, but I have no idea what is doing it.
Since I use kdm as a login manager, I found I could
add a command to /etc/kde/kdm/Xsetup to get it to run
as soon as the login screen starts:
xset led off
How to get it to actually turn numlock on, I don't
know (I prefer it off). Maybe something that uses
the XTEST extension could be used to simulate
pressing the numlock key.
11:19 a.m.
On Mon, 24 Aug 2015 07:02:28 +0200, fedora wrote:
Did you try xconf-query?
man xconf-query
No; but I just tried. rpm -q says I don't have it; dnf install
doesn't find it; nor does dnf whatprovides. How do I get it?
--
Beartooth Staffwright, Neo-Redneck Not Quite Clueless Power User
Remember I have precious (very precious!) little idea where up is.
3 p.m.
On 08/25/15 00:19, Beartooth wrote:
On Mon, 24 Aug 2015 07:02:28 +0200, fedora wrote:
> Did you try xconf-query?
>
> man xconf-query
No; but I just tried. rpm -q says I don't have it; dnf install
doesn't find it; nor does dnf whatprovides. How do I get it?
It is misspelled. xfconf-query is what you're seeking
--
It seems most people that say they are "done talking about it" never really are
until given the last word.
2:44 p.m.
On Tue, 25 Aug 2015 04:00:15 +0800, Ed Greshko wrote:
On 08/25/15 00:19, Beartooth wrote:
> On Mon, 24 Aug 2015 07:02:28 +0200, fedora wrote:
>
>> Did you try xconf-query?
>>
>> man xconf-query
> No; but I just tried. rpm -q says I don't have it; dnf install
> doesn't find it; nor does dnf whatprovides. How do I get it?
It is misspelled. xfconf-query is what you're seeking
Aha! That gives :
xfconf-query
Channels:
displays
xfdashboard
xfce4-keyboard-shortcuts
xfwm4
xfce4-notifyd
thunar-volman
xfce4-session
keyboards
xsettings
xfce4-settings-manager
thunar
xfce4-desktop
xfce4-settings-editor
xfce4-appfinder
xfce4-panel
xfce4-mime-settings
None of the above, however, alas! tells me anything. Do I just go
down that list, finding each entry, and trying to open each with an
editor, looking for mentions of numlock??
--
Beartooth Staffwright, Neo-Redneck Not Quite Clueless Power User
Remember I have precious (very precious!) little idea where up is.
1:36 p.m.
On 23 August 2015 at 17:28, Beartooth <beartooth(a)comcast.net> wrote:
I use the number pad a lot, and the number keys below the F-keys
only for the upper case; so I keep my bios set to boot up with it on, and
expect it to stay on, unless I tell it otherwise. Yet lately I've been
being pulled up sharp a dozen times a day and more to sudden large
inconveniences which turn out to mean numlock is off. What could be doing
this? How can I tell my PC that num*lock* means LOCK, e basta!?
I never use the numpad for anything other than typing numbers so I use,
rather an extreme, workaround to circumvent the Numlock key altogether.
I have a USB keyboard:
$ cat /etc/udev/hwdb.d/70-numpad-always-on.hwdb
keyboard:usb:v*p*
KEYBOARD_KEY_70062=0
KEYBOARD_KEY_70059=1
KEYBOARD_KEY_7005a=2
KEYBOARD_KEY_7005b=3
KEYBOARD_KEY_7005c=4
KEYBOARD_KEY_7005d=5
KEYBOARD_KEY_7005e=6
KEYBOARD_KEY_7005f=7
KEYBOARD_KEY_70060=8
KEYBOARD_KEY_70061=9
KEYBOARD_KEY_70063=dot
(there's a space before every KEYBOARD_KEY, .hwdb files are syntax
sensitive IIRC).
Then as root:
# udevadm hwdb --update
and unplug/re-plug the keyboard. The only caveat is that you can't turn the
Numlock "off" at all. : |
--
Ahmad Samir
2:55 p.m.
On 24-08-2015 20:36, Ahmad Samir wrote:
On 23 August 2015 at 17:28, Beartooth <beartooth(a)comcast.net
<mailto:beartooth@comcast.net>> wrote:
I use the number pad a lot, and the number keys below the F-keys
only for the upper case; so I keep my bios set to boot up with it
on, and
expect it to stay on, unless I tell it otherwise. Yet lately I've been
being pulled up sharp a dozen times a day and more to sudden large
inconveniences which turn out to mean numlock is off. What could be
doing
this? How can I tell my PC that num*lock* means LOCK, e basta!?
I never use the numpad for anything other than typing numbers so I use,
rather an extreme, workaround to circumvent the Numlock key altogether.
I have a USB keyboard:
$ cat /etc/udev/hwdb.d/70-numpad-always-on.hwdb
keyboard:usb:v*p*
KEYBOARD_KEY_70062=0
KEYBOARD_KEY_70059=1
KEYBOARD_KEY_7005a=2
KEYBOARD_KEY_7005b=3
KEYBOARD_KEY_7005c=4
KEYBOARD_KEY_7005d=5
KEYBOARD_KEY_7005e=6
KEYBOARD_KEY_7005f=7
KEYBOARD_KEY_70060=8
KEYBOARD_KEY_70061=9
KEYBOARD_KEY_70063=dot
(there's a space before every KEYBOARD_KEY, .hwdb files are syntax
sensitive IIRC).
Then as root:
# udevadm hwdb --update
and unplug/re-plug the keyboard. The only caveat is that you can't turn
the Numlock "off" at all. : |
--
Ahmad Samir
I have tested on a lenoevo T400 and I don't see any problems. I have
tested it with libre office writer and libre office calc and also with
gedit. As I said before i don't see any problems. OS Fedora 22 workstation.
2:50 p.m.
On Mon, 24 Aug 2015 21:55:45 +0200, René Harder Olsen wrote:
On 24-08-2015 20:36, Ahmad Samir wrote:
>
> On 23 August 2015 at 17:28, Beartooth <beartooth(a)comcast.net
> <mailto:beartooth@comcast.net>> wrote:
>
>
> I use the number pad a lot, and the number keys below the
> F-keys
> only for the upper case; so I keep my bios set to boot up with it
> on, and expect it to stay on, unless I tell it otherwise. Yet
> lately I've been being pulled up sharp a dozen times a day and more
> to sudden large inconveniences which turn out to mean numlock is
> off. What could be doing this? How can I tell my PC that num*lock*
> means LOCK, e basta!?
[....]
I have tested on a lenoevo T400 and I don't see any problems. I
have
tested it with libre office writer and libre office calc and also with
gedit. As I said before i don't see any problems. OS Fedora 22
workstation.
What I call a problem is that numlock is getting turned off
without my having intended that to happen. I want it on unless I actually
tell it otherwise.
Neither my eyes nor my fingers are what they once were. It's
possible that I'm brushing against something without knowing it -- but
not, I believe, anything so far from home position as the numlock key.
--
Beartooth Staffwright, Neo-Redneck Not Quite Clueless Power User
Remember I have precious (very precious!) little idea where up is.
2:54 p.m.
On 08/26/2015 12:50 PM, Beartooth wrote:
On Mon, 24 Aug 2015 21:55:45 +0200, René Harder Olsen wrote:
> On 24-08-2015 20:36, Ahmad Samir wrote:
>>
>> On 23 August 2015 at 17:28, Beartooth <beartooth(a)comcast.net
>> <mailto:beartooth@comcast.net>> wrote:
>>
>>
>> I use the number pad a lot, and the number keys below the
>> F-keys
>> only for the upper case; so I keep my bios set to boot up with it
>> on, and expect it to stay on, unless I tell it otherwise. Yet
>> lately I've been being pulled up sharp a dozen times a day and more
>> to sudden large inconveniences which turn out to mean numlock is
>> off. What could be doing this? How can I tell my PC that num*lock*
>> means LOCK, e basta!?
[....]
> I have tested on a lenoevo T400 and I don't see any problems. I have
> tested it with libre office writer and libre office calc and also with
> gedit. As I said before i don't see any problems. OS Fedora 22
> workstation.
What I call a problem is that numlock is getting turned off
without my having intended that to happen. I want it on unless I actually
tell it otherwise.
Neither my eyes nor my fingers are what they once were. It's
possible that I'm brushing against something without knowing it -- but
not, I believe, anything so far from home position as the numlock key.
The thing is in "keyboards":
[rick@prophead ~]$ xfconf-query -lv -c keyboards
/Default/Numlock true
--
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital ricks(a)alldigital.com -
- AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 -
- -
- Life: That which happens while you search for the remote control. -
----------------------------------------------------------------------
1:21 p.m.
On Wed, 26 Aug 2015 12:54:56 -0700, Rick Stevens wrote:
[....]
The thing is in "keyboards":
[rick@prophead ~]$ xfconf-query -lv -c keyboards /Default/Numlock true
OK, but you're over my head. Where is "keyboards"? Or should I be
asking where xfconf is?
[root@Hbsk4 ~]# cd /usr/share/system-config-keyboard
[root@Hbsk4 system-config-keyboard]# ls
keyboard_cli.py keyboard_gui.pyo system-config-keyboard.py
keyboard_cli.pyc keyboard_tui.py system-config-keyboard.pyc
keyboard_cli.pyo keyboard_tui.pyc system-config-keyboard.pyo
keyboard_gui.py keyboard_tui.pyo
keyboard_gui.pyc pixmaps
[root@Hbsk4 system-config-keyboard]#
--
Beartooth Staffwright, Neo-Redneck Not Quite Clueless Power User
Remember I have precious (very precious!) little idea where up is.
4:28 p.m.
On 08/27/2015 11:21 AM, Beartooth wrote:
On Wed, 26 Aug 2015 12:54:56 -0700, Rick Stevens wrote:
[....]
> The thing is in "keyboards":
>
> [rick@prophead ~]$ xfconf-query -lv -c keyboards /Default/Numlock true
OK, but you're over my head. Where is "keyboards"? Or should I be
asking where xfconf is?
[root@Hbsk4 ~]# cd /usr/share/system-config-keyboard
[root@Hbsk4 system-config-keyboard]# ls
keyboard_cli.py keyboard_gui.pyo system-config-keyboard.py
keyboard_cli.pyc keyboard_tui.py system-config-keyboard.pyc
keyboard_cli.pyo keyboard_tui.pyc system-config-keyboard.pyo
keyboard_gui.py keyboard_tui.pyo
keyboard_gui.pyc pixmaps
[root@Hbsk4 system-config-keyboard]#
As the logged-in user, try running
xfconf-query -lv -c keyboards
and see what response you get. If you see something like
/Default/Numlock false
then you can try:
xfconf-query -c keyboards -p /Default/Numlock -s true
to set it to true. Here's a transcript of what I did:
[rick@prophead ~]$ xfconf-query -lv -c keyboards
/Default/Numlock true
[rick@prophead ~]$ xfconf-query -c keyboards -p /Default/Numlock -s false
[rick@prophead ~]$ xfconf-query -lv -c keyboards
/Default/Numlock false
[rick@prophead ~]$ xfconf-query -c keyboards -p /Default/Numlock -s true
This just demonstrates that it was set to "true". I set it to "false"
and verified it, then put it back to "true". I have no idea if setting
it to the other state will have any effect on your issue, but you can
try it. I don't believe numlock is set on my machine as my keypad does
cursor movement unless I actually push the NumLock key even though the
xfconf-query reports it as "true".
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital ricks(a)alldigital.com -
- AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 -
- -
- Grabel's Law: 2 is not equal to 3--not even for large values of 2. -
----------------------------------------------------------------------
11:15 a.m.
On Thu, 27 Aug 2015 14:28:54 -0700, Rick Stevens wrote:
xfconf-query -lv -c keyboards
[btth@Hbsk4 ~]$ xfconf-query -lv -c keyboards
/Default/Numlock true
[btth@Hbsk4 ~]$
--
Beartooth Staffwright, Neo-Redneck Not Quite Clueless Power User
Remember I have precious (very precious!) little idea where up is.
11:41 a.m.
I'm confused. My keyboard doesn't have a numlock key at all. The
keypad works fine in OS X and Windows, but it doesn't work at all in
Fedora and I can't figure out how to make it work.
Chris Murphy
3163
days inactive
3168
days old
13 comments
8 participants
participants (8)
-
Ahmad Samir -
Beartooth -
Chris Murphy -
Ed Greshko -
fedora -
René Harder Olsen -
Rick Stevens -
Tom Horsley