Bug 465349
Summary: | Wacom Bamboo tablet doesn't work at all | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Dawid Pietrala <dafydd> | ||||||
Component: | linuxwacom | Assignee: | Aristeu Rozanski <arozansk> | ||||||
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | medium | ||||||||
Version: | 10 | CC: | arozansk, bmr, bnocera, info, lxtnow, mcepl, peter.hutterer, xgl-maint | ||||||
Target Milestone: | --- | ||||||||
Target Release: | --- | ||||||||
Hardware: | All | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2009-03-27 05:48:02 UTC | Type: | --- | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Attachments: |
|
Description
Dawid Pietrala
2008-10-02 20:58:57 UTC
Please provide your xorg.conf and your Xorg.log file, otherwise we can't really debug this. Thanks. Created attachment 319376 [details]
xorg.conf
Created attachment 319377 [details]
Xorg.0.log
Please add the following line to your /usr/share/hal/fdi/policy/20thirdparty/10-linuxwacom.fdi <merge key="input.x11_options.Type" type="string">stylus</merge> This goes right below the line that specifies x11_driver as wacom. Then restart HAL and then X and let me know if that fixes it. now it works fine however only as a pointing device. thank you! So we need to fix "use as painting device", right? Or are we done here? That's as far as we can get without modification in the driver. I talked to aris this morning so we should hopefully get it fixed properly soon. (In reply to comment #6) > So we need to fix "use as painting device", right? Or are we done here? yes, we still need to fix it. i'll let you know as soon as sth changes. thanks! i've just found out that unplugging the tablet causes X to crash. no trace in logs, though. should i post another bug? Yes please. I'm suprised there isn't a backtrace or anything. Anyway, reassigning this one to linuxwacom, i know aris is/was working on it. (In reply to comment #9) > i've just found out that unplugging the tablet causes X to crash. no trace in > logs, though. should i post another bug? yes, against xorg-x11-server component, attach /etc/X11/xorg.conf, /var/log/Xorg.*.log, /var/log/dmesg, and /var/log/messages. https://bugzilla.redhat.com/show_bug.cgi?id=468264 submitted. thank you! after today's update (linuxwacom-0.8.0.3-3.fc10.i386) the tablet ceased to work. i had to repeat the step in #4. before that however, i copied a part of my Xorg.0.log: (II) config/hal: Adding input device Wacom Bamboo1 (II) LoadModule: "wacom" (II) Loading /usr/lib/xorg/modules/input//wacom_drv.so (II) Module wacom: vendor="X.Org Foundation" compiled for 4.3.99.902, module version = 1.0.0 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 2.1 (II) Wacom driver level: 47-0.8.0-2 $ (EE) Wacom Bamboo1: No type or invalid type specified. Must be one of stylus, touch, cursor, eraser, or pad (EE) PreInit returned NULL for "Wacom Bamboo1" (EE) config/hal: NewInputDeviceRequest failed (II) NVIDIA(0): Setting mode "1280x1024_75" (II) config/hal: Adding input device Wacom Bamboo1 (EE) Wacom Bamboo1: No type or invalid type specified. Must be one of stylus, touch, cursor, eraser, or pad (EE) PreInit returned NULL for "Wacom Bamboo1" (EE) config/hal: NewInputDeviceRequest failed after: (II) config/hal: Adding input device Wacom Bamboo1 (II) LoadModule: "wacom" (II) Loading /usr/lib/xorg/modules/input//wacom_drv.so (II) Module wacom: vendor="X.Org Foundation" compiled for 4.3.99.902, module version = 1.0.0 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 2.1 (II) Wacom driver level: 47-0.8.0-2 $ (**) Wacom Bamboo1: always reports core events (**) Wacom Bamboo1 device is /dev/input/event5 (**) Wacom Bamboo1 is in absolute mode (**) WACOM: suppress value is 2 (**) Option "BaudRate" "9600" (**) Wacom Bamboo1: serial speed 9600 (II) XINPUT: Adding extended input device "Wacom Bamboo1" (type: Wacom Stylus) (**) Option "Device" "/dev/input/event5" Wacom Bamboo1 Wacom X driver grabbed event device (==) Wacom using pressure threshold of 30 for button 1 (==) Wacom USB Bamboo1 tablet speed=9600 (38400) maxX=5104 maxY=3712 maxZ=511 resX=1012 resY=1012 tilt=enabled (==) Wacom device "Wacom Bamboo1" top X=0 top Y=0 bottom X=5104 bottom Y=3712 resol X=1012 resol Y=1012 but it still works only as a pointing device. The workaround is now part of 0.8.0.3-4, but with the same limitations (stylus only). At least you don't have to apply it manually anymore. (In reply to comment #14) > The workaround is now part of 0.8.0.3-4, but with the same limitations (stylus > only). At least you don't have to apply it manually anymore. well, actually i had to. before that, the tablet didn't work. doh. seriously? are you sure that's -4, and not -3? did you restart HAL before restarting the server? (In reply to comment #16) > doh. seriously? are you sure that's -4, and not -3? > did you restart HAL before restarting the server? you're right: linuxwacom-0.8.0.3-3.fc10.i386. sorry! This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping (In reply to comment #7) > That's as far as we can get without modification in the driver. I talked to > aris this morning so we should hopefully get it fixed properly soon. If this is the only reason this bug is still open, I think it can be marked as a duplicate of bug #109750 (or the other way around). Both state that changes are required in the driver to fully autoconfigure all features of the wacom tablets. I won't mark it as duplicate myself as I'm not the maintainer of these bugs. *** This bug has been marked as a duplicate of bug 109750 *** |