Ask Your Question

ConWrite's profile - activity

2016-09-26 23:24:06 -0500 received badge  Necromancer (source)
2016-09-26 23:24:06 -0500 received badge  Self-Learner (source)
2016-09-26 23:24:06 -0500 received badge  Teacher (source)
2016-09-26 23:23:04 -0500 received badge  Good Question (source)
2016-09-26 17:33:53 -0500 received badge  Editor (source)
2016-09-26 17:25:33 -0500 answered a question Why is Num Lock ALWAYS an issue with EACH Release?!? It's 2015!!!

Alright, Distro Hopping has brought me back here to try again and I can Finally report success. A combination of below did the trick for me.

Edit this file /etc/gdm/custom.conf and uncomment the line WaylandEnable=false. And then activate numlockx on login screen by placing

if [ -x /usr/bin/numlockx ]; then
/usr/bin/numlockx on fi

at the end of /etc/gdm/Init/Default

(From Damus' comment elsewhere on This page)

AND

Typing >> Layout of numeric keypad >> Legacy

(From https://ask.fedoraproject.org/en/ques... )

For me it has to be Both, as I tried each individually with unsatisfactory results.

Much Thanks to damus and Frttls and everyone else that offered suggestions that might very well work for others.

2015-09-08 08:10:00 -0500 received badge  Famous Question (source)
2015-07-25 06:38:25 -0500 received badge  Nice Question (source)
2015-06-15 03:50:54 -0500 received badge  Notable Question (source)
2015-06-09 14:18:42 -0500 commented answer Why is Num Lock ALWAYS an issue with EACH Release?!? It's 2015!!!

Well, more time has been used & while I feel I have learned a fair amount, which has value of course, a fix eludes me. When I check the status after various iterations, the best I get is

Loaded: loaded (/usr/lib/systemd/system/rc-local.service; enabled; vendor preset: disabled)
Active: active (exited) since Tue 2015-06-09 13:57:48 EDT; 25min ago
Main PID: 920 (code=exited, status=0/SUCCESS)
..rc.local[920]: Error opening display!

I can't remember all that I've tried now & the reward just isn't enough to justify more time. Yours & randomuser's help has been greatly appreciated

2015-06-09 14:16:41 -0500 received badge  Commentator
2015-06-09 14:16:41 -0500 commented answer Why is Num Lock ALWAYS an issue with EACH Release?!? It's 2015!!!

It's a tad disheartening that a motivating suggestion is presented after essentially giving up. I still suspect what you mentioned is related to the issue though. There wasn't a rc.local file by default and when I created one, I did so with a grasping at straws mindset after trying other approaches. It seems silly to me now that I didn't do a status check - I guess thinking it would work or it wouldn't. I assure you, I started this believing getting numlock setup would be no big deal and even when that turned out not to be true, for me at least, positivity endured through much of the effort.

2015-06-08 15:54:51 -0500 commented answer Why is Num Lock ALWAYS an issue with EACH Release?!? It's 2015!!!

I know it wasn't listed, but this was one of the many other things I tried. BUT I tried it again and it still didn't work for me. I very much appreciate your assistance, but I'm not wasting anymore time on this. I've used Fedora on the computer I'm typing on now since F17, however, this and the fact that F22 freezes on me regularly along with a couple of other issues... well, obviously to me, it's time to move on to a different distro. Thanks again for your help.

2015-06-08 14:55:29 -0500 received badge  Popular Question (source)
2015-06-05 13:21:45 -0500 commented question Why is Num Lock ALWAYS an issue with EACH Release?!? It's 2015!!!
2015-06-05 13:11:42 -0500 commented question Why is Num Lock ALWAYS an issue with EACH Release?!? It's 2015!!!

It does work from the command line, but after I've logged in of course. The answer to the first seems to me to be absolutely -- The second is definitely not. Nothing I have done, including things that HAVE worked in the past, have worked with F22. It's just annoying for someone that has numbers in their password to type it in incorrectly because the numlock not being on by default or at least set by choice. I'm starting to adapt, but I'm also considering other options, like another distro, because it is truly that annoying.

2015-06-02 19:46:59 -0500 commented question Why is Num Lock ALWAYS an issue with EACH Release?!? It's 2015!!!

Much thanks for the replies. As far as I can tell, the keymap reflects what I see with the numlock light. I've tried numerous variations with regards to permissions and have restarted my computer so many times in the last few days that I'm starting to think I fully understand how Bill's character in Groundhog Day felt. I can't help but think this has something to do with systemd, which I've been reading a bit up on -- However, that is pure speculation. It'd be nice if numlock was simply a setting in Gnome Tweak or in the All Settings section. Nonetheless, I'm not giving up.

2015-06-01 01:31:11 -0500 commented question Why is Num Lock ALWAYS an issue with EACH Release?!? It's 2015!!!

I changed the Default, numlockx, numlockx.sh and xinitrc shell scripts back to root only and yeah, all of them are marked as Allow executing file as program. Whenever I run either command numlockx on/off, nothing additional is shown in the terminal afterward, BUT, the numlock light does turn on and off with those commands. numlockx toggle does the same.

2015-05-31 16:00:22 -0500 commented question Why is Num Lock ALWAYS an issue with EACH Release?!? It's 2015!!!

After the "I've also done this..." I intended to include this to finish the line -- done this to /etc/gdm/Init/Default

2015-05-31 15:46:44 -0500 commented question Why is Num Lock ALWAYS an issue with EACH Release?!? It's 2015!!!

numlockx and numlockx.sh shell scripts are in /etc/X11/xinit/xinitrc.d. I've tried one or two other things based on searches but those escape me now but nothing done wasn't reversible. I think that's everything, brain on lock. Thanks for your time.

2015-05-31 15:45:08 -0500 commented question Why is Num Lock ALWAYS an issue with EACH Release?!? It's 2015!!!

I've also done this

At the end of the file you will find a line like

exit 0

Above this line add the following code

if [ -x /usr/bin/numlockx ]; then /usr/bin/numlockx on fi

Through Tweak Tool (using GNOME 3 BTW) I have numlockx included in startup applications - which seems to work, but only after I've logged in and usually already have manually turned it on. I read somewhere about ctrl+shift+numlock and I've tried that at various times and it does nothing for me. Unfortunately, journalctl -b does not show the attempt, so something is missing apparently.

2015-05-31 15:42:41 -0500 commented question Why is Num Lock ALWAYS an issue with EACH Release?!? It's 2015!!!

Thanks for the responses and the welcome. The strange thing is, if the numlock light is to be believed, the computer starts with it on and stays on almost right up to when the logon screen appears. However, the numlock worked just fine in F21 without the light staying on. Anyway, the numlockx executable is in bin with permission set for read and write for all, although I've never had to do that before -- trying just about anything. I've tried /usr/bin/numlockx on in a few places in /etc/X11/xinit/xinitrc even though the included instructions say place "At the beginning of the file..."

2015-05-30 21:26:10 -0500 received badge  Student (source)
2015-05-30 20:11:51 -0500 asked a question Why is Num Lock ALWAYS an issue with EACH Release?!? It's 2015!!!

I apologize in advance for my mock irritability, but I've dumped a ton of time into this over the years.


The recent F22 is different somehow than previous Fs. Everything I've done in the past (F21 and before) no longer works.

Yes, numlockx is installed

Yes, I have tried multiple scripts

No, there is nothing in the BIOS for numlock


The Number Keys are Labeled as Numbers, why isn't what they are labeled as the Default!?