My fn + arrow key up and down just all of a sudden stopped working properly...

basically sometimes it works, sometimes it doesnt, or most of the time it doesnt work at all.

this happened just a day ago, my other fn hotkeys work, such as fn+f6

can someone help? i've tried updating, upgrading, reinstalling pulseaudio, changing hotkey to something different.. im out of options now but a complete reinstallation of bodhilinux

any help?

Hi fuzzyrider, and welcome to LQ.

That sounds very much to me like a hardware problem. Have you tried a different keyboard?

1 members found this post helpful.

Hi, did you update your system recently and if so, what commands did you use?

The moksha package got upgraded and that includes an integrated pulse-mixer. If the old pulse-mixer was not properly removed there might be a conflict in using these hotkeys.

2 members found this post helpful.

I agree with hydrurga. First I would rule out hardware errors. If you don't have another keyboard try to boot an ISO and see if it also has the same issue.

OK if it is not an hardware error, try to delete your .e folder and restart moksha (or reboot). Your .e folder is a hidden folder in your home directory. If that fails then I really don't know. But for reference what version of Bodhi are you using?

1 members found this post helpful.

Ah, I didn't consider that something else could be grabbing those keys, Charles. Definitely more plausible than my hardware fault theory!

thanks everyone for your replies, so since I started this thread I attempted to use my fn keys from a LiveUSB and it worked, so I confirmed that it was not a hardware issue, then I moved on to your reply and deleted the .e folder and I have no idea why but this worked, even though my desktop looked drastically different ( i dont mind really )!!

thanks a lot!

Great to hear!

If you want, you can mark this thread as "Solved" (see "Thread Tools" at the top of the thread).

Glad to have helped. You can fix your desktop if you remembered how you customized it.

As to why this happened, it is unlikely Charles suggestion that an update caused it. If you are using Bodhi 4.x then yes there is a new version of moksha in the repos but it is in the testing repo. If you are using the testing repo then yes conceivably that could have caused it. Since our old forums are gone I can't link to my post on testing this version of moksha but surely I suggested to remove the .e folder after upgrading to Moksha 3.0rc.

But anyway not many use this testing repo so I feel it unlikely that caused your issue. But if the the files in the .e folder get corrupted enlightenment or moksha can act "funny." The most likely cause of this is an improper shutdown like losing power while the system is updating the files. It has been an issue as long as I have been using e or Moksha and I suppose since I have taken a major role in Moksha development, maybe I should investigate possible fixes for this in the code. Perhaps some verification of the critical files. But honestly that would be low priority for me as under normal usage this seldom happens anymore, it used to happen alot in the early days of enlightenment (and Bodhi). Not as often now, it has been years since I have had to delete this folder to fix an issue on any of my systems.

1 members found this post helpful.

Did not realize testing was still enabled on this old rig.

I agree, can hardly remember when was the last time I deleted the .e folder