Bug 106886

e.g. by scrolling up/down with holding Shift and pressing Pg-Up/Pg-Down. 

Another victim (in Cc). 

Another regular victim ...

I wonder why this happens at all, since AccessX seems to be disabled by default and SlowKeys is part of AccessX.

xkbInit.c:
[...]
int                     XkbWantAccessX=         0; 
[...]
    if (XkbWantAccessX)
        ctrls->enabled_ctrls|= XkbAccessXKeysMask;
[...]

    else if ((strncmp(argv[i],"-accessx",8)==0)||
                 (strncmp(argv[i],"+accessx",8)==0)) {
        int j=1;            
        if (argv[i][0]=='-')        
            XkbWantAccessX= 0;
        else {
            XkbWantAccessX= 1;

BTW, I can't reproduce this Slowkeys problem at all. And I'm quite sure none of you starts the Xserver with the "+accessx" option.

some thoughts:
- I think I enabled accessX in sax sometimes for exactly one reason:
  the possibility to do mouse-actions via the keyboard (numpad-mouse functionality)
- are you sure that kdm/xdm do not enable this in their own config ?

I'm pretty sure slow keys is disabled by default. Just checked with
a new installation. It can be enabled by typing:

   Shift+NumLock  (beep = on) again typed (other beep = off)

In the past I had a long discussion with people from the community why
I would misuse the AccessX functions for handling mouse events if there
is no mouse connected or not detected. In principal this extension is
for disabled people and because I don't want to offend anybody this feature
has been disabled in sax some time ago. Of course the xkb system still
allows to enable it with default settings and the default toggle key
combination

It is if ever used and configurable by the window managers and as far as I
know all of them have this feature disabled by default. But I maybe wrong
here

(In reply to comment #5)
> - I think I enabled accessX in sax sometimes for exactly one reason:
>   the possibility to do mouse-actions via the keyboard (numpad-mouse
>   functionality)
Shift-Numlock (Pointer_EnableKeys) works for me. But I'm not able to enable the Slowkeys feature. No matter how long I press Shift. AFAIK it needs to be pressed for 8 seconds.

> - are you sure that kdm/xdm do not enable this in their own config ?
Maybe kdm, but xdm should not.

Marcus, are you mixing up Slowkeys and Pointer_EnableKeys here? Shift-Numlock is for en/disabling Pointer_EnableKeys. I don't think you get a beep here. The beep you get when en/disabling Slowkeys by pressing Shift for minimum of 8 seconds, but I never succeeded in doing so. :-(

yes correct, sorry for mixing it up... I was focused on the sax/mouse issue

(In reply to comment #8)
> Marcus, are you mixing up Slowkeys and Pointer_EnableKeys here? Shift-Numlock

Definitely. Pointer_EnableKeys should always be possible, as Shift+Numlock is nothing you can press accidentally.

> is for en/disabling Pointer_EnableKeys. I don't think you get a beep here. The

You do.

> beep you get when en/disabling Slowkeys by pressing Shift for minimum of 8
> seconds, but I never succeeded in doing so. :-(

For me Slowkeys has been off for a long time now.
I'm not 100% sure why some guys get slowkeys turned on. I think this had been enabled a long time ago by default, but it isn't any longer.

Maybe this happens because /etc/X11/xdm/Xservers is marked as a config file? So it probably won't be updated by rpm if you install a newer version (read: if you update instead of reinstall your system).

> Maybe this happens because /etc/X11/xdm/Xservers is marked as a config file?
> So it probably won't be updated by rpm if you install a newer version
> (read: if you update instead of reinstall your system).

I don't think anyone has ever "+accessx" in his /etc/X11/xdm/Xservers file.

*** Bug 240219 has been marked as a duplicate of this bug. ***

Since I never was able to enable Slowkeys on any default installation in the last years I'm finally closing this one as WORKSFORME.

*** Bug 473518 has been marked as a duplicate of this bug. ***

*** Bug 478666 has been marked as a duplicate of this bug. ***

The Slowkeys feature is what affected me in my comment in report #478666. I can hear the beeps I described.

Holding down the shift key for a long time can happen if you are thinking what you are about to type.

Can there be a visual notification as to what's about to happen when this feature is to be turned on? Similar to what you get when you first press Shift-NumLock.

Or use the Control key instead of the Shift key.

> Can there be a visual notification as to what's about to happen when this
> feature is to be turned on? Similar to what you get when you first press
> Shift-NumLock.

I suggest to open a seperate bugreport against the appropriate desktop (KDE3, KDE4, Gnome, Xfce, whatever) for this.

I've never been able to enable Slowkeys. See my comment #13.

I agree that this is the same issue as I first reported in #478666.

I could not see how I would be frequently holding down the shift key for
long periods, especially as I note that the 8 second requirement for SlowKeys
to be activated is interrupted if other keys are typed, i.e. typing a long
uppercase string will not inadvertantly activate SlowKeys.  But, an 8 second
period of holding shift down when using the mouse, including mouse clicks will
activate SlowKeys!  This I consider to be a bug, as I do use shift as a mouse
click modifier in my twm configuration.

I also think "xset q" should report that SlowKeys is active.  If it did so I would
never even have opened report #478666.

Most of the discussion has been taken place in bug 478666, so closing this as duplicate the other way round.

In short, this is a KDE4 issue.

*** This bug has been marked as a duplicate of bug 478666 ***