Bug#689868: gnome-control-center: wacom button assignments broken

[Alexander Wagner]

Hi!

Futher invesitation shows, that the button assignements seem to break as 
soon as the wacom setup applet loads. If I assing keys to the tablet's 
keys, close the gnome wacom setup applet all assignements are lost. If I 
then unplug the tablet, and replug it in all buttons get assigned 
properly and things work as they should. Therefore, it seems that the 
applet causes the problem.


Additionally. I tried to use intuos4-led-config[1] to set the LED 
buttons on my intuos 4 properly. I used this application for quite a 
while on Debian squeeze, and it actually works on Wheezy as well in as 
far as it sets the leds properly. However, this also kills the tablet. 
(Note that the above mentioned tool requires to unload and reload the 
wacom module.) It seems that this is in a way related to my first 
problem with the gnome tool to set the buttons, as also with 
intuos4-led-config I can get my tablet to work properly by unplugging 
and replugging to the usb bus. (Of course then my LED assignement is lost.)



[1] http://braindump.kargulus.de/?p=408

--

Kind regards,/ War is Peace.
|Freedom is Slavery.
Alexander Wagner| Ignorance is Strength.
|
| Theory : G. Orwell, 1984
   /  In practice:   USA, since 2001


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#689868: gnome-control-center: wacom button assignments broken

[Alexander Wagner]

Package: gnome-control-center
Version: 1:3.4.2-2.1
Severity: important

Dear Maintainer,

certain wacom tablets offer a number of hardware buttons for common shortcuts.
In the past I had to assign those buttons using xsetwacom within a short shell
script. Now those settings went to gnome-control-center wacom and the map
buttons function. I therefore tried to repeat my setup from the past from
there:

---
#!/bin/bash
DEVICE=Wacom Intuos4 6x9
ERASER=$DEVICE eraser
CURSOR=$DEVICE cursor
PAD=$DEVICE pad

xsetwacom set $ERASER Rotate half
xsetwacom set $CURSOR Rotate half
xsetwacom set $PAD Rotate half

xsetwacom set $PAD Button 2  key ctrl s
xsetwacom set $PAD Button 3  key alt
xsetwacom set $PAD Button 4  key ctrl
xsetwacom set $PAD Button 5  key shift

xsetwacom set $PAD Button 6  key x
xsetwacom set $PAD Button 7  key p
xsetwacom set $PAD Button 8  key c
xsetwacom set $PAD Button 9  key ctrl y
---

First I found, that currently it is NOT possible to map bare modifiers like
CTRL, SHIFT and ALT, which is, however, in this context very sensible and
useful. The control as such just does not accept the input of ALT without any
keystroke, at least I was not able to fiddle out how I should do this. I would
treat this as a more critical bug as you'll want to have some of these keys if
you're working with the tablet alone (without a keyboard).

Secondly, given that I use the tablet in left handed orientation, I'm not sure
about the numbering scheme used for the buttons. This is just an inconvenience,
but for improvement of the GUI one should make this assignment clear (note that
xsetwacom has the very same issue.)

Anyway, to fiddle it out I just assigned the numbers 1-8 to them, to check in
vi what I will get. However, I just found that no buttons at all get assigned
to the tablet! I can assign whatever I want, but the tablet just doesn't send
any of them back. This is the very reason for this bug report. Though
everything seems to be recognized as it should (the tablet is reported
properly, the syslog is clear of any errors), even orientation switching works
fine, the buttons seem to be broken. I may note that buttons include here the
centre keyring button meant for mode switching as well as the ring itself. It
seems I get almost no events.

Note: I refer to sending back keystrokes, I'm aware that at the moment gnome-
control-centre can not set the OLEDs of the intuos4.

*** Please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these lines ***



-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages gnome-control-center depends on:
ii  accountsservice0.6.21-6
ii  apg2.2.3.dfsg.1-2
ii  desktop-file-utils 0.20-0.1
ii  gnome-control-center-data  1:3.4.2-2.1
ii  gnome-desktop3-data3.4.2-1
ii  gnome-icon-theme   3.4.0-2
ii  gnome-icon-theme-symbolic  3.4.0-2
ii  gnome-menus3.4.2-3
ii  gnome-settings-daemon  3.4.2-5
ii  gsettings-desktop-schemas  3.4.2-1
ii  libatk1.0-02.4.0-2
ii  libc6  2.13-35
ii  libcairo-gobject2  1.12.2-2
ii  libcairo2  1.12.2-2
ii  libcanberra-gtk3-0 0.28-5
ii  libcanberra0   0.28-5
ii  libcheese-gtk213.4.2-2
ii  libcheese3 3.4.2-2
ii  libclutter-1.0-0   1.10.8-2
ii  libcogl-pango0 1.10.2-6
ii  libcogl9   1.10.2-6
ii  libcolord1 0.1.21-1
ii  libcomerr2 1.42.5-1
ii  libcups2   1.5.3-1
ii  libdbus-1-31.6.0-1
ii  libdbus-glib-1-2   0.100-1
ii  libfontconfig1 2.9.0-7
ii  libgcrypt111.5.0-3
ii  libgdk-pixbuf2.0-0 2.26.1-1
ii  libglib2.0-0   2.32.3-1
ii  libgnome-bluetooth10   3.4.2-1
ii  libgnome-desktop-3-2   3.4.2-1
ii  libgnome-menu-3-0  3.4.2-3
ii  libgnomekbd7   3.4.0.2-1
ii  libgnutls262.12.20-1
ii  libgoa-1.0-0   3.4.2-1
ii  libgssapi-krb5-2   1.10.1+dfsg-2
ii  libgstreamer0.10-0 0.10.36-1
ii  libgtk-3-0 3.4.2-3
ii  libgtop2-7 2.28.4-3
ii  libjson-glib-1.0-0 0.14.2-1
ii  libk5crypto3   1.10.1+dfsg-2
ii  libkrb5-3  1.10.1+dfsg-2
ii  libnm-glib40.9.4.0-6
ii  libnm-gtk0