Wacom Graphire Bluetooth does not work.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xf86-input-wacom (Debian) |
Fix Released
|
Unknown
|
|||
xf86-input-wacom (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
After upgrade to Oneiric tablet has stopped to work. I can pair it and it show up that it's connected but stylus don't work. Sometimes after full restart it works, but if I toggle it off and on, it stops to work.
I also found similar bug in Debian's bug-tracker:
http://
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: xserver-
ProcVersionSign
Uname: Linux 3.0.0-12-generic i686
NonfreeKernelMo
ApportVersion: 1.23-0ubuntu1
Architecture: i386
Date: Tue Sep 27 02:40:08 2011
DistUpgraded: Log time: 2011-09-16 15:37:12.321518
DistroCodename: oneiric
DistroVariant: ubuntu
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: Gigabyte Technology Co., Ltd. GA-770TA-UD3
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: xf86-input-wacom
UpgradeStatus: Upgraded to oneiric on 2011-09-26 (0 days ago)
dmi.bios.date: 12/25/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F2
dmi.board.name: GA-770TA-UD3
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:bvnAwardSof
dmi.product.name: GA-770TA-UD3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.5.
version.libdrm2: libdrm2 2.4.26-1ubuntu1
version.
version.
version.
version.
version.
version.
version.
version.
summary: |
- Wacom Graphire bluetooth stopped to work. + Wacom Graphire Bluetooth does not work. |
Changed in xf86-input-wacom (Debian): | |
status: | Unknown → New |
Changed in xf86-input-wacom (Ubuntu): | |
status: | Incomplete → Opinion |
status: | Opinion → New |
Changed in xf86-input-wacom (Debian): | |
status: | New → Fix Released |
Hey pit.s,
Hi, thanks for reporting this issue during the development period of
Ubuntu.
I notice there's not been further comments to the bug report since the
release came out, would you mind updating us on the status of it in the
release?
Are you still able to reproduce the issue? If not, do you think the bug
report can be closed, or do you think we should continue tracking it?