xsetwacom list dev broken

[lcampagn]

Binary package hint: wacom-tools

I just installed wacom tools 0.7.9.3 in hardy. When I run "xsetwacom list dev" I get no output. I am still able to set/get flags on these devices despite them not showing up via list dev. (this breaks a screen rotating script I maintain for tablets)

[Justin Dugger (jldugger)]

Wacom-tools has been upgraded to 0.7.9.8, and I can't duplicate this bug. Is this still a problem for you?

[lcampagn (luke-campagnola)]

Just upgraded, I still have the bug. "xsetwacom list dev" prints
nothing, but I can still use "xsetwacom set stylus ..." to change
parameters.
"xidump -l" says this:

Virtual core keyboard keyboard
Virtual core pointer disabled
eraser unknown
cursor unknown
stylus unknown
Configured Mouse unknown
Generic Keyboard unknown

On Sun, Mar 30, 2008 at 4:53 AM, Justin Dugger <email address hidden> wrote:
> Wacom-tools has been upgraded to 0.7.9.8, and I can't duplicate this
> bug. Is this still a problem for you?
>
>
>
> --
> xsetwacom list dev broken in hardy
> https://bugs.launchpad.net/bugs/179453
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Wouter Deconinck (wdconinc)]

0.7.9.8 fixed this problem for me.

# xsetwacom list dev
WacomEraser eraser
WacomCursor cursor
WacomStylus stylus

# xidump -l
Virtual core keyboard keyboard
Virtual core pointer disabled
WacomEraser unknown
WacomCursor unknown
WacomStylus unknown
Configured Pointer unknown
Generic Keyboard unknown

[Justin Dugger (jldugger)]

Closing as Fixed based on Wouter's report. Please reopen if you can duplicate this in hardy (or intrepid)

[Tina Russell (tinarussell)]

I'm getting this in Intrepid, with the same response to "xsetwacom list dev" (nothing) and a similar response from "xidump -l" (stylus is "unknown"). Weirder still, "xsetwacom get stylus Rotate" returns "-1", and I can't set the stylus rotation, argh (that may need to be a separate bug). However, retrieving other stylus settings still worked (like "BottomX," etc.), and the stylus still works as an extended input device with pressure sensitivity and such.

[Thor H. Johansen (thorhajo)]

I am having the issue as described by Tina Russell, but in Hardy. And can the Ubuntu team please bundle wacomcpl along in wacom-tools?

[Tina Russell (tinarussell)]

Hey,

Sorry! I figured out was was wrong, and forgot to add another comment in here. It turns out the symptoms that I described were because I had old versions of the wacom tools stuffed away in /usr/local/bin, from times that I had compiled it from source (these days, I use the “--prefix=/usr” option to ensure this doesn’t happen, although there are reasons not to use that as well). Anyway, Thor, you might want to try using “/usr/bin/xsetwacom” or whatever and see if that makes a difference, or compile the tools from source (from the source package or by getting a tarball from the Linux Wacom Project site) without installing it and try running the program directly from the source directory. Does that all make sense?

If I’m right about this, all you need to do is remove the old version, perhaps by using “sudo make uninstall” in the source directory of that old version (if you still have the source lying around), or simply by removing (“sudo rm”, though be careful with that!) the Wacom-related binaries in “/usr/local/bin”.

If was right and that works, we can probably close this bug again. If not, we’ll have to put our detective caps on and figure out what the problem is, together.

[lcampagn (luke-campagnola)]

I am not seeing this problem anymore.. I'm not sure when it was fixed,
possibly I deleted my local linux-wacom files a while back and didn't
notice the fix? Can't remember :)

Q

[Timo Aaltonen (tjaalton)]

Ok, thanks for confirming that the issue is no longer. Closing the bug.

[nitrogen (i-am-nitrogen)]

Ubuntu Intrepid:

/usr/bin/xsetwacom list dev shows nothing.

xidump -l shows:

Virtual core keyboard keyboard
Virtual core pointer disabled
Generic Keyboard unknown
Synaptics Touchpad unknown
stylus unknown
cursor unknown
eraser unknown
Macintosh mouse button emulation unknown
PS/2 Generic Mouse unknown
SynPS/2 Synaptics TouchPad unknown
AT Translated Set 2 keyboard unknown
Video Bus unknown

[nitrogen (i-am-nitrogen)]

xsetwacom insisted on having the 'Driver "intel"' line.

[lcampagn (luke-campagnola)]

Looks like everybody who has had this bug has fixed it by uninstalling previous versions of wacom files in /usr/local/bin and /usr/local/lib or by correcting their xorg.conf. I'm going to mark this bug invalid, and we can reopen it if anyone else is still having trouble.

[Tobias (tobias-j)]

I have never had any previous version of the wacom-tools on this machine. And the Driver is now in Ubuntu 9.04 HAL set-up the driver. So now this is a Ubuntu bug again. "xsetwacom list" is empty "xidump -l" lists the device and the device is working.

[Tobias (tobias-j)]

This problem is also known and solved in the "Linux Wacom Tablet Project" bugtracker:
http://sourceforge.net/tracker/index.php?func=detail&aid=2776735&group_id=69596&atid=525125

[WolphFang (mjoyner-vbservices)]

Any fix or work around for this yet?

I am trying to get screen rotate working on two Toshiba M200 tablet-pcs I just picked up off of e-bay.

[Peter Meiser (meiser79)]

The issue with the wacom tools is also that HAL doesn't put the right string into "info.product". That's why "stylus", "cursor" or "pad" as the device name don't work.

Right now, there's a script floating around in different forums or blogs:
#! /bin/sh
## find any wacom devices
for udi in `hal-find-by-property --key input.x11_driver --string wacom`
do
type=`hal-get-property --udi $udi --key input.x11_options.Type`
## rewrite the names that the Xserver will use
hal-set-property --udi $udi --key info.product --string $type
done

My patch fixes this issue in the HAL fdi and hal-setup-wacom tool.

[Bryce Harrington (bryce)]

Whoopie, can you explain your patch in more detail?
Also, have you presented this patch to upstream? I'd be more comfortable with the patch if it had been reviewed/accepted by them first.

[Peter Meiser (meiser79)]

Bryce, Loïc Martin gave his statement to the patch in bug 286028. He is right that my patch reverts the strings back to "oldstyle". And he's also right that the issue is in the utils themselves using hard-coded strings to find the devices.

[Bryce Harrington (bryce)]

loic's comment:

"It's a patch, but it fixes the wrong problem. The bug is in wacomcpl, that's the program that should be patched.

Going back to old style strings alleviates the problem for some users, but doesn't solve it long-term, since people can have different tablets plugged in at a time, and/or multiple tools for each tablets, and want to keep settings separate for them (going back would also prevent the whole stack from improving, since at least now there's no excuses for a graphic program not to allow separate options for separate pens/tools). Else we'd have "stylus", "cursor", "eraser" and "pad" by default, since it was trivial to fix by shipping a slightly different .fdi.

Now if there's a wacomcpl patch, then that would be perfect (other applications already support the more precise strings used by default now by the linuxwacom drivers)! Else, other graphical configuration programs exists, the just need one or two more functions to become complete wacomcpl replacements."

[Ulrich (uhansen)]

I had the same problem with Karmic.

This description here solved it for me:

https://help.ubuntu.com/community/X61T#Wacomcpl

Thanks and good luck!
Uli

[Timo Aaltonen (tjaalton)]

xsetwacom on the new driver doesn't use wacomcpl (which is no more), but input properties. Closing as fixed.