Problems with sticky keys

Asked by Coljep

I have to use sticky keys due to a stroke and find that after booting and not using the keyboard for about two minutes, I am told that I have pressed shift 5 times etc. and do I want to disable Sticky keys?
After clicking "Do not disable" things are OK until rebooted. This is under Gnome.
With K desktop sticky keys has to be reset each reboot using some settings.
This has been true for well over a year. I am using Feisty now.
I also find that sticky keys does not work under Wine at least with AceMoney.

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Kris Marsh (moogman) said :
#1

Hi there,

Can you take a look at the keyboard accessibility settings...

System->Preferences->Universal Access->Keyboard Accessibility

And then see if "Disable if unused for" is set. You may wish to uncheck this option.

I'm unable to help out with Wine and AceMoney, however I do use a great finance manager program called "GnuCash". It's available in Ubuntu and you can download and take a look if you wish, by clicking Applications->Add/Remove...

Hope this helps!

Kris

(I have taken the menu item name from Ubuntu Gutsy/7.10, so it may be slightly different if you are using Feisty)

Revision history for this message
Coljep (coljep) said :
#2

Kris Marsh wrote:
> Your question #13742 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/13742
>
> Status: Open => Answered
>
> Kris Marsh proposed the following answer:
> Hi there,
>
> Can you take a look at the keyboard accessibility settings...
>
> System->Preferences->Universal Access->Keyboard Accessibility
>
> And then see if "Disable if unused for" is set. You may wish to uncheck
> this option.
>
> I'm unable to help out with Wine and AceMoney, however I do use a great
> finance manager program called "GnuCash". It's available in Ubuntu and
> you can download and take a look if you wish, by clicking
> Applications->Add/Remove...
>
> Hope this helps!
>
> Kris
>
> (I have taken the menu item name from Ubuntu Gutsy/7.10, so it may be
> slightly different if you are using Feisty)
>
>
Kris,

The answer you suggest does not cure the problem. The option has always
been unchecked. I have done further tests and reported the problems as
[bug 153518].
I am sure I have also reported it to WineHQ.

Colin Jepson

Revision history for this message
Tang (robertmcgreg) said :
#3

Hi, --- Just checking out old problems posted on the Launchpad website, but maybe still not solved.
https://answers.launchpad.net/ubuntu/+questions

Have you registered your problem as solved yet?

Revision history for this message
Coljep (coljep) said :
#4

The problem still exists under Ubuntu 8.04

Revision history for this message
Tang (robertmcgreg) said :
#5

Hi again.
Having never used sticky keys, I'm trying to understand the system enough to solve your problem without boring you with options you've probably looked at countless times.

Have you reviewed settings in System/Preferences/Preferred Applications/Accessibility/mobility?

Revision history for this message
Coljep (coljep) said :
#6

Tang wrote:
> Your question #13742 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/13742
>
> Status: Open => Needs information
>
> Tang requested for more information:
> Hi again.
> Having never used sticky keys, I'm trying to understand the system enough to solve your problem without boring you with options you've probably looked at countless times.
>
> Have you reviewed settings in System/Preferences/Preferred
> Applications/Accessibility/mobility?
>
>
Sorry for delay in reply. No settings in

System/Preferences/Preferred Applications/Accessibility/mobility are relevant.

The problem is that if you do not use the keyboard at all for about 4-5 mins after startup, the standard "You just pressed two keys together or shift 5 times etc, Do you want to de-activate sticky keys?" or similar pops up. If you say no the message does not show up again. I has been like this for a long time now. This is in various flavours of Linux that I have tried.

It would also be nice if you had an option to turn of the message if you do press two keys at once. Even windows allows this.

Regards,
Colin

Revision history for this message
Tang (robertmcgreg) said :
#7

Colin, thnks for your reply

I'm wondering if your problem is linked to a network port scan or keyboard controller issue, and could be either solved or sidestepped with a cron
Perhaps if you also think that's possible, and added a footnote to Bug 153518:t, someone there could modify a kernel for folk in your situation if asked . Failing that, a new cron macro question here may result in the outcome you want

Meanwhile, on this web page,
http://www.faqs.org/docs/Linux-HOWTO/Keyboard-and-Console-HOWTO.html

I found this,
" 4.1 Keyboard hardware reset

Things may be wrong on a lower level than Linux knows about. There are at least two distinct lower levels (keyboard and keyboard controller) where one can give the command "keyboard disable" to the keyboard hardware. Keyboards can often be programmed to use one out of three different sets of scancodes.

However, I do not know of cases where this turned out to be a problem.

Some keyboards have a remapping capability built in. Stormy Henderson (<email address hidden>) writes: `If it's your keyboard accidently being reprogrammed, you can (on a Gateway AnyKey keyboard) press control-alt-suspend_macro to reset the keys to normal.' "

Could that gateway keyboard be a solution for you?

HTH

Revision history for this message
Coljep (coljep) said :
#8

Tang wrote:
> Your question #13742 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/13742
>
> Status: Open => Needs information
>
> Tang requested for more information:
> Colin, thnks for your reply
>
> I'm wondering if your problem is linked to a network port scan or keyboard controller issue, and could be either solved or sidestepped with a cron
> Perhaps if you also think that's possible, and added a footnote to Bug 153518:t, someone there could modify a kernel for folk in your situation if asked . Failing that, a new cron macro question here may result in the outcome you want
>
> Meanwhile, on this web page,
> http://www.faqs.org/docs/Linux-HOWTO/Keyboard-and-Console-HOWTO.html
>
> I found this,
> " 4.1 Keyboard hardware reset
>
> Things may be wrong on a lower level than Linux knows about. There are
> at least two distinct lower levels (keyboard and keyboard controller)
> where one can give the command "keyboard disable" to the keyboard
> hardware. Keyboards can often be programmed to use one out of three
> different sets of scancodes.
>
> However, I do not know of cases where this turned out to be a problem.
>
> Some keyboards have a remapping capability built in. Stormy Henderson
> (<email address hidden>) writes: `If it's your keyboard accidently being
> reprogrammed, you can (on a Gateway AnyKey keyboard) press control-alt-
> suspend_macro to reset the keys to normal.' "
>
> Could that gateway keyboard be a solution for you?
>
>
> HTH
>
>
Hello Tang,

No I do not think that the problem is as you describe. It happens on a
range of computers from 1.7 GHz Athlon to 3GHz Athlon XP and 3.2GHz
Celeron on an assortment of motherboards and keyboards, none of which
are Gateway. I have been using mainly the Gnome desktop because I like
Ubuntu but find Kubuntu unstable and cannot find another KDE distro that
I like. Although I am sure it has happened with KDE as well.

Please ask if you need any more information, tests or clarification.

Colin

Revision history for this message
Tang (robertmcgreg) said :
#9

Coljep wrote:
> Question #13742 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/13742
>
> Status: Needs information => Open
>
> Coljep gave more information on the question: Tang wrote:
> > Your question #13742 on Ubuntu changed:
> > https://answers.launchpad.net/ubuntu/+question/13742
> >
> > Status: Open => Needs information
> >
> > Tang requested for more information: Colin, thnks for your reply
> >
> > I'm wondering if your problem is linked to a network port scan or
> > keyboard controller issue, and could be either solved or
> > sidestepped with a cron Perhaps if you also think that's possible,
> > and added a footnote to Bug 153518:t, someone there could modify
> > a kernel for folk in your situation if asked . Failing that, a new
> > cron macro question here may result in the outcome you want
> >
> > Meanwhile, on this web page,
> > http://www.faqs.org/docs/Linux-HOWTO/Keyboard-and-Console-HOWTO.html
> >
> >
> > I found this, " 4.1 Keyboard hardware reset
> >
> > Things may be wrong on a lower level than Linux knows about. There
> > are at least two distinct lower levels (keyboard and keyboard
> > controller) where one can give the command "keyboard disable" to
> > the keyboard hardware. Keyboards can often be programmed to use one
> > out of three different sets of scancodes.
> >
> > However, I do not know of cases where this turned out to be a
> > problem.
> >
> > Some keyboards have a remapping capability built in. Stormy
> > Henderson (<email address hidden>) writes: `If it's your keyboard
> > accidently being reprogrammed, you can (on a Gateway AnyKey
> > keyboard) press control-alt- suspend_macro to reset the keys to
> > normal.' "
> >
> > Could that gateway keyboard be a solution for you?
> >
> >
> > HTH
> >
> >
> Hello Tang,
>
> No I do not think that the problem is as you describe. It happens on
> a range of computers from 1.7 GHz Athlon to 3GHz Athlon XP and 3.2GHz
> Celeron on an assortment of motherboards and keyboards, none of
> which are Gateway. I have been using mainly the Gnome desktop because
> I like Ubuntu but find Kubuntu unstable and cannot find another KDE
> distro that I like. Although I am sure it has happened with KDE as
> well.
>
> Please ask if you need any more information, tests or clarification.
>
> Colin
>

Hi Colin, seems to be a slight misunderstanding. I was referring to the
Gateway type keyboard and the reset function not as a cause but as a
possible solution to the Linux problem mentioned in the link above.

My opinion still is that a macro set for about 10-15 minutes from boot
would probably reset settings after whatever interruption occurs.
However its about 35 years since I wrote anything like original code, so
it could take the rest of my life to modify a kernel, or even write a
macro that circumvented the problem. Kids are writing that sort of stuff
before they finish school these days. That's why I suggested adding to
the bug report, and a new question here, either could catch the eye of
and challenge someone already writing stuff like that.

Also, amongst the usual Usenet nutters at alt.os.linux.ubuntu there's a
few clued up adults who would probably go out of their way to help if
you explain your situation.

HTH

Can you help with this problem?

Provide an answer of your own, or ask Coljep for more information if necessary.

To post a message you must log in.