Red Hat Bugzilla – Bug 616653
Button → keycode configurations can cause server hangs
Last modified: 2010-11-10 16:57:08 EST
Description of problem:
If a button is configured to send key events, an allocation in the signal handler may cause a server hang.
Version-Release number of selected component (if applicable):
Configure a button to send key strokes, execute button action repeatedly until the server hangs.
Steps to Reproduce:
1. xsetwacom --set "Wacom device name" Button1 "key a b c"
2. Click button 1 on the device
3. repeat 2 until hang
The driver calls XkbGetCoreMap() during wcmEmitKeysym(). This function calls malloc, but we're in the signal handler. malloc() during the signal handler may hang the machine.
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release.
** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **
xorg-x11-drv-wacom-0.10.5-6.el6 is available in brew
I set the eraser button to output 'abc' and tapped it repeatedly in gedit. Based on the character count I've tapped over 600 times, no crash.
I will note I tried to set my pointer and eraser back after this and they still print out abc instead of left click. I tried
xsetwacom set "Wacom Serial Tablet PC Pen Tablet/Digitizer" Button1 "button 1"
xsetwacom set "Wacom Serial Tablet PC Pen Tablet/Digitizer" Button1 1
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.