I'm using Ubuntu 10.10 (Maverick, up to date) x32-64, with the last official xserver-xorg-input-wacom package (1:0.10.8-0ubuntu1 for instance).
My tablet is a Wacom Intuos3 A4 (Wacom Intuos3 9x12).
When I boot up my system, and I use the strips of my tablet to test them, they do work as default action (slide page).
But this is not what I want to do with it, so I use xsetwacom for this. And, at the precise time when I use xsetwacom to set another action key (eg. f or d), the strips stop working.
Here is the custom script I use to do that :
#!/bin/sh
# Strips
xsetwacom set "Wacom Intuos3 9x12 pad" StripLUp "key f" # Taille du pinceau
xsetwacom set "Wacom Intuos3 9x12 pad" StripLDn "key d"
xsetwacom set "Wacom Intuos3 9x12 pad" StripRUp "key s" # Opacité
xsetwacom set "Wacom Intuos3 9x12 pad" StripRDn "key a"
# Boutons gauche
# ---------
# | | 1 |
# | 3 |---|
# | | 2 |
# |-------|
# | 4 |
# ---------
xsetwacom set "Wacom Intuos3 9x12 pad" button1 "key y" # redo
xsetwacom set "Wacom Intuos3 9x12 pad" button2 "key z" # undo
xsetwacom set "Wacom Intuos3 9x12 pad" button3 "key shift" # shift
xsetwacom set "Wacom Intuos3 9x12 pad" button4 "key b" # retour au brushs
# Boutons droite
# ---------
# | 5 | |
# |---| 7 |
# | 6 | |
# |-------|
# | 8 |
# ---------
xsetwacom set "Wacom Intuos3 9x12 pad" button5 "key shift plus" # zoom +
xsetwacom set "Wacom Intuos3 9x12 pad" button6 "key minus" # zoom -
xsetwacom set "Wacom Intuos3 9x12 pad" button7 "key shift" # shift
xsetwacom set "Wacom Intuos3 9x12 pad" button8 "key g" # couleurs brushs
# Stylet ( button1=pointe;button2=premier boutton;button3=second boutton)
#xsetwacom set "Wacom Intuos3 9x12" button2 "key ctrl" # bouton 2 du stylet pipette
# Mapping absolue de la tablette
xsetwacom set "Wacom Intuos3 9x12 stylus" mode Absolute
After the execution of the script given, everything works just as expected, except the strips !
Thank you for your attention.
---
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 260.19.06 Mon Sep 13 04:29:19 PDT 2010
GCC version: gcc version 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu5)
Architecture: amd64
DistroRelease: Ubuntu 10.10
DkmsStatus:
vboxhost, 3.2.10, 2.6.35-22-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!)
nvidia-current, 260.19.06, 2.6.35-22-generic, x86_64: installed
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1)
MachineType: Gigabyte Technology Co., Ltd. 965P-DS3
NonfreeKernelModules: nvidia
Package: xf86-input-wacom (not installed)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=dd7cdc40-fdf4-43df-aae5-f8dc037cb639 ro quiet splash
ProcEnviron:
LANG=fr_FR.utf8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
Tags: maverick maverick
Uname: Linux 2.6.35-22-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 07/17/2008
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F13
dmi.board.name: 965P-DS3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd07/17/2008:svnGigabyteTechnologyCo.,Ltd.:pn965P-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rn965P-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: 965P-DS3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
system:
distro: Ubuntu
codename: maverick
architecture: x86_64
kernel: 2.6.35-22-generic
It looks like you've provided most of the information needed for this to be an actionable bug report but could you also attach log files so we know the id numbers of your hardware and so on?
For your convenience, an easy way to do this is to run the command:
apport-collect 680477
Thanks ahead of time.
Also, if there's any chance you can test against natty and upload the files from there, it'll up the priority on your bug report. (Development on maverick is completed and developers are generally focusing on bugs reported about natty now.)