Bug 375419 - KDE accessibility dialogue appears at inappropriate times
Summary: KDE accessibility dialogue appears at inappropriate times
Status: RESOLVED WORKSFORME
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_accessibility (other bugs)
Version First Reported In: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: András Manţia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-22 18:15 UTC by Neil Turton
Modified: 2018-12-12 11:20 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Neil Turton 2017-01-22 18:15:58 UTC
I can reproduce this problem with a guest session, so it isn't due to a particularly strange configuration.

  1. Start a KDE session
  2. Open System settings and go to Desktop Behavior/Accessibility
  3. On the Activation Gestures tab, disable "Use gestures for activating sticky keys and slow keys".
  4. Enable "Show a confirmation dialog whenever a keyboard accessibility feature is toggled".
  5. Open an xterm (not konsole)
  6. Run this command to ring the terminal bell: perl -e 'print pack("C",7)'
  7. A dialogue appears reading 'Do you really want to activate "Slow keys", "Bounce keys", and "Mouse keys"?'
  8. Select "Deactivate all AccessX features and gestures".
  9. Press the "No" button to close the dialog.
 10. Run the command to ring the terminal bell: perl -e 'print pack("C",7)'
 11. The dialogue appears again.

I would expect the system bell to be rung without generating a dialogue.

Step 6 can be replaced by pressing the backspace key or tab twice or a variety of other actions which cause xterm to ring the bell.

A workaround for this bug is to disable the confirmation dialog which was enabled in step 4.  I don't think there's any side-effect of the workaround.
Comment 1 András Manţia 2018-12-12 11:20:19 UTC
I cannot reproduce this with Plasma Desktop master branch from 12/12/2018. Could be fixed as a sideeffect by https://phabricator.kde.org/D17415