Please describe the problem:
Stickykeys has been dodgy for a while.  

See here: https://bugs.launchpad.net/ubuntu/+source/gnome-applets/+bug/383649

And here: https://bugs.launchpad.net/ubuntu/+bug/191181

and here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=511999

Depending which version you are running different issue present themselves.  Until the latest version of Ubuntu, stickykeys would ignore the "Disable when two keys are pressed together" option, and also randomly forget user's settings.

More recent versions sometimes turn off with no warning, or notification.  When on, mouse clicks are not considered events.   Eg, I press ctrl once, leading to the [^] icon lighting up on the notification applet.  A mouse click would normally count as an event and unlock the ctrl key.  This is not currently happening.

When stickykeys turns itself off randomly, it can be re-enabled by opening the Keyboard Accessibility panel and unticking then reticking the "Simulate simultaneous keypresses".

Steps to reproduce:
On Debian stable and pre-9.04 versions of ubuntu (confirmed on AMD64 and i386, Debian and Ubuntu)

1. Enable sticky keys and the notification applet.
2. Ensure "Disable if two keys are pressed at once" is NOT ticked.
3. Press two keys at once.  Stickykeys will then be disabled.

At some points, gconf seems to 'forget' your stickykeys preferences.  I can't reproduce this reliably, but several other people have mentioned it as an issue elsewhere.

On Ubuntu 9.04 (my system is AMD64)

1. enable stickykeys
2. "stick" a modifier key down.
3. click mouse.  watch as modifier key does not unlock as it should.

Sometimes (again, can't reliably reproduce), stickykeys will stop responding.  The notification panel appears as if it's working, but it's not.  Unticking and then re-ticking the option in the control panel will make it start working again.

Actual results:
As described.

Expected results:
I would expect sticky keys to (a) remember it's settings (b) respect those settings and (c) consider mouse clicks as events.

Does this happen every time?
Yes.  Well, mostly.  This is really three bugs in one, but I suspect they might all be related.

Other information: