https://bugzilla.novell.com/show_bug.cgi?id=478666 User markgray+to-suse@puck.nac.net added comment https://bugzilla.novell.com/show_bug.cgi?id=478666#c1 Mark Gray changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |markgray+to-suse@puck.nac.n | |et Info Provider| |daved@windclimber.id.au --- Comment #1 from Mark Gray 2009-02-23 07:44:07 MST --- Please attach the information requested on webpage: http://en.opensuse.org/Bugs:X It sounds like it might be an application -- any out of the ordinary apps? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=478666 User markgray+to-suse@puck.nac.net added comment https://bugzilla.novell.com/show_bug.cgi?id=478666#c3 Mark Gray changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |daved@windclimber.id.au --- Comment #3 from Mark Gray 2009-02-24 02:49:05 MST --- I am just a screener, the X maintainers need the information requested on the webpage: http://en.opensuse.org/Bugs:X -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=478666 User daved@windclimber.id.au added comment https://bugzilla.novell.com/show_bug.cgi?id=478666#c5 --- Comment #5 from Dave Davey 2009-02-24 06:09:04 MST --- Created an attachment (id=274973) --> (https://bugzilla.novell.com/attachment.cgi?id=274973) output of hwinfo --gfx -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=478666 Dave Davey changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|daved@windclimber.id.au | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=478666 User raffo@cdi.com added comment https://bugzilla.novell.com/show_bug.cgi?id=478666#c7 Rafael Herrera changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |raffo@cdi.com --- Comment #7 from Rafael Herrera 2009-02-24 10:15:01 MST --- I have observed the same behavior. At random times the computer emits a few beeps and the keyboard stops working. The desktop I had been using was KDE4. The system log did not report any error. I've had it happen with an USB plus a PS/2 keyboards plugged in, one moment they are working, beeps, none work afterwards. Login out and login in again restores the keyboard functionality. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=478666 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sndirsch@novell.com AssignedTo|xorg-maintainer-bugs@forge. |mhopf@novell.com |provo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=478666 User raffo@cdi.com added comment https://bugzilla.novell.com/show_bug.cgi?id=478666#c10 --- Comment #10 from Rafael Herrera 2009-02-27 12:59:05 MST --- (In reply to comment #9)

Rafael, if this happens again can you verify that pressing Ctrl behaves the same way?

Hasn't happened since I switched back to kde3 a couple of days ago. I'll switch back now and wait. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=478666 User daved@windclimber.id.au added comment https://bugzilla.novell.com/show_bug.cgi?id=478666#c12 --- Comment #12 from Dave Davey 2009-02-28 15:59:18 MST --- Created an attachment (id=276212) --> (https://bugzilla.novell.com/attachment.cgi?id=276212) xev output when problem evident - testing Ctrl key xev output requested by Matthias and referred to in comment #11. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=478666 User daved@windclimber.id.au added comment https://bugzilla.novell.com/show_bug.cgi?id=478666#c14 --- Comment #14 from Dave Davey 2009-03-02 20:27:28 MST --- Now that we know what precipitates this problem, I have confirmed by booting openSuSE 11.0 and 10.3 that the same problem does not exist with those versions. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=478666 User mhopf@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=478666#c16 --- Comment #16 from Matthias Hopf 2009-03-03 01:55:31 MST --- Created an attachment (id=276643) --> (https://bugzilla.novell.com/attachment.cgi?id=276643) Tool for verifying AccessX state Please compile this tool gcc -o accessx_state accessx_state.c -lX11 and run it with ./accessx_state to validate your accessibility state. If it turns out that XkbAccessXKeysMask is on for you, something in your Desktop environment must re-enable the AccessX keyboard switching enablement (which is off by default). If the sticky/slow reaction happens again, run it again and verify the state of XkbSlowKeysMask, XkbBounceKeysMask, and XkbStickyKeysMask. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=478666 User daved@windclimber.id.au added comment https://bugzilla.novell.com/show_bug.cgi?id=478666#c18 --- Comment #18 from Dave Davey 2009-03-03 06:42:45 MST --- X was started: /usr/bin/X :0 -br -verbose -auth /var/run/gdm/auth-for-gdm-Lm28WM/database -nolisten tcp vt7 In the "normal state", ./accessx_state output includes: enabled_ctrls: 0x00001141: XkbAccessXKeysMask: Enable turning on AccessX by key sequences: on XkbAccessXTimeoutMask: Change to default values on timeout: off XkbAccessXFeedbackMask: Audible feedback (see ax_options): on XkbSlowKeysMask: Delay keypress acceptance: off XkbBounceKeysMask: Ignore keypress bounces after release: off XkbStickyKeysMask: Let modifiers stick to state: off If I hold down the Shift key for 8s and do not type anything else, the slow keys "feature" is on, and the output now includes: enabled_ctrls: 0x00001143: XkbAccessXKeysMask: Enable turning on AccessX by key sequences: on XkbAccessXTimeoutMask: Change to default values on timeout: off XkbAccessXFeedbackMask: Audible feedback (see ax_options): on XkbSlowKeysMask: Delay keypress acceptance: on XkbBounceKeysMask: Ignore keypress bounces after release: off XkbStickyKeysMask: Let modifiers stick to state: off This is reversed by holding the shift key down for eight seconds again. Note: there is no "audible feedback"; I see no evidence of the "sticky ctrl". -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=478666 User raffo@cdi.com added comment https://bugzilla.novell.com/show_bug.cgi?id=478666#c20 --- Comment #20 from Rafael Herrera 2009-03-03 11:49:02 MST --- For what is worth: /usr/bin/X -br -nolisten tcp :0 vt7 -auth /var/lib/xdm/authdir/authfiles/A:0-yEzlpY My display manager is kdm4 and the desktop is kde4. $ ./accessx_state XkbGetControls: ret 0: enabled_ctrls: 0x00001361: XkbAccessXKeysMask: Enable turning on AccessX by key sequences: on XkbAccessXTimeoutMask: Change to default values on timeout: off XkbAccessXFeedbackMask: Audible feedback (see ax_options): on XkbSlowKeysMask: Delay keypress acceptance: off XkbBounceKeysMask: Ignore keypress bounces after release: off XkbStickyKeysMask: Let modifiers stick to state: off After holding down shift for 8 secs: $ ./accessx_state XkbGetControls: ret 0: enabled_ctrls: 0x00001363: XkbAccessXKeysMask: Enable turning on AccessX by key sequences: on XkbAccessXTimeoutMask: Change to default values on timeout: off XkbAccessXFeedbackMask: Audible feedback (see ax_options): on XkbSlowKeysMask: Delay keypress acceptance: on XkbBounceKeysMask: Ignore keypress bounces after release: off XkbStickyKeysMask: Let modifiers stick to state: off There is an audible PC speaker beep after 4 secs of holding the shift key down, continuing holding the key for 4 more secs produces another beep and the slowkey feature is turned on. (In reply to comment #15)

b) verify whether you can turn this behavior off (when it's happening again) with - Pressing Shift for more than 8 seconds (if typing was painfully slow) yes

- Pressing Shift 5 times in a row (if Ctrl is sticky) yes, ctrl is sticky, i think, I get the xterm menu after releasing the ctrl key. I get a feedback beep after the 5 shifts and also after pressing the ctrl key, they have different freqs and it's not clear what they mean.

$ ./accessx_state XkbGetControls: ret 0: enabled_ctrls: 0x00001379: XkbAccessXKeysMask: Enable turning on AccessX by key sequences: on XkbAccessXTimeoutMask: Change to default values on timeout: off XkbAccessXFeedbackMask: Audible feedback (see ax_options): on XkbSlowKeysMask: Delay keypress acceptance: off XkbBounceKeysMask: Ignore keypress bounces after release: off XkbStickyKeysMask: Let modifiers stick to state: on

- Pressing two modifier keys (e.g. Shift + Ctrl) or three (Shift+Ctrl+Alt) (also if Ctrl is sticky) No. Shift+Ctrl+Alt is used by a vmware host to release the mouse under certain configurations. So there may be a possible conflict there. (I use that combo.)

- Pressing Ctrl twice (also if Ctrl is sticky)

no -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=478666 User daved@windclimber.id.au added comment https://bugzilla.novell.com/show_bug.cgi?id=478666#c22 --- Comment #22 from Dave Davey 2009-03-03 20:42:48 MST --- The XkbAccessXKeysMask is "on" only when logging in through gdm. kdm or xdm logins leave the XkbAccessXKeysMask off. I use twm. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=478666 User raffo@cdi.com added comment https://bugzilla.novell.com/show_bug.cgi?id=478666#c24 --- Comment #24 from Rafael Herrera 2009-03-04 08:52:24 MST --- With kdm4, XkbAccessXKeysMask is only on for KDE4. With GDM, XkbAccessXKeysMask is only on with KDE4. In GDM I unchecked the "read screen" feature, no other option was selected. In the accessibility options of KDE4, the all seem to be disabled except in "Activation Gestures", the option "Use gestures for activating sticky keys and slow keys" was turned on. By toggling it and applying, XkbAccessXKeysMask gets turned off. I do not remember if I set that option or if it was set by default. Other misc. information, I use KDE 4.2 out of the opensuse repository. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=478666 User mhopf@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=478666#c26 Matthias Hopf changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEW AssignedTo|mhopf@novell.com |kde-maintainers@suse.de --- Comment #26 from Matthias Hopf 2009-03-06 10:15:46 MST --- Apparently KDE4 explicitly sets XkbAccessXKeysMask. Too many users stumble over accidentally actviated AccessX features, so this shouldn't be enabled by default. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=478666 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Component|X.Org |KDE4 Workspace QAContact|xorg-maintainer-bugs@forge. |qa@suse.de |provo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=478666 User daved@windclimber.id.au added comment https://bugzilla.novell.com/show_bug.cgi?id=478666#c28 --- Comment #28 from Dave Davey 2009-03-08 18:07:29 MST --- I agree with Matthias' comment #26 that this should not be turned on by default, but not with the view that the problem should be assigned to kde (#25). I opened this bug but was not using kde. gdm seemed to be the "culprit", but I was not using a gnome desktop. So I think it is a general X problem, specifically: - nothing should enable it by default - activating/deactivating it should be logged - the audible signal on activating/deactivating should work - xset should show the ActiveX status (and allow it to be set?) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=478666 User mhopf@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=478666#c30 --- Comment #30 from Matthias Hopf 2009-03-10 09:20:35 MST --- (In reply to comment #28)

I agree with Matthias' comment #26 that this should not be turned on by default, but not with the view that the problem should be assigned to kde (#25). I opened this bug but was not using kde. gdm seemed to be the "culprit", but I was not using a gnome desktop. So I think it is a general X problem, specifically:

X doesn't (read: shouldn't) set this up - the default has changed to off quite some time ago. In order to validate you can start X without any desktop: X & sleep 1; DISPLAY=:0 xterm& DISPLAY=:0 twm& and run ./accessx_state in the xterm there. Of course you could use any other (simple) window manager, but twm is known to not interfere anywhere.

- activating/deactivating it should be logged - xset should show the ActiveX status (and allow it to be set?)

Please open upstream bug reports for that on bugs.freedesktop.org

- the audible signal on activating/deactivating should work

It works for some people (in this bug report as well). Maybe your PC speaker is not connected to the mainboard? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=478666 User sndirsch@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=478666#c32 --- Comment #32 from Stefan Dirsch 2009-03-13 07:40:34 MST ---

Agreed, but please note again, that from my perpective I "fixed" the problem by changing, in /etc/sysconfig/displaymanager DISPLAYMANAGER="gdm" to DISPLAYMANAGER="kdm"

which does not say to me that the problem should be classified "KDE Workspace".

So let's reassign this bug to GNOME after having it fixed for KDE4. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.