Bug 828091

Summary: "Wacom graphics tablet" does not detect UC-Logic tablet
Product: [Fedora] Fedora Reporter: Ankur Sinha (FranciscoD) <sanjay.ankur>
Component: control-centerAssignee: Control Center Maintainer <control-center-maint>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 17CC: control-center-maint, mkasik, rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-31 22:21:42 UTC Type: Bug
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 Flags
Screenshot showing wacom graphics tablet not detecting my tablet none

Description Ankur Sinha (FranciscoD) 2012-06-04 08:43:35 UTC
Created attachment 589073 [details]
Screenshot showing wacom graphics tablet not detecting my tablet

Description of problem:
My tablet works out of the box with Fedora, which is awesome! However, the "wacom graphics tablet" utility does not detect it. Is this utility limited to wacoms, or is it the general utility for all tablets?

Version-Release number of selected component (if applicable):
control-center-3.4.2-1.fc17.x86_64


How reproducible:
Always

Steps to Reproduce:
1. Plug in tablet
2. Check dmesg to see if detected. Use tablet to confirm it works
3. Open "wacom graphics tablet"
  
Actual results:
Says "no attached" (Screenshot)

Expected results:
Should detect and let me configure my tablet

Additional info:
[  440.842649] usb 2-1.4: new low-speed USB device number 6 using ehci_hcd
[  440.936064] usb 2-1.4: New USB device found, idVendor=5543, idProduct=0004
[  440.936069] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  440.936074] usb 2-1.4: Product: Tablet WP5540U
[  440.936077] usb 2-1.4: Manufacturer: UC-LOGIC
[  441.038054] input: UC-LOGIC Tablet WP5540U as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.0/input/input18
[  441.039377] input: UC-LOGIC Tablet WP5540U as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.0/input/input19
[  441.039848] uclogic 0003:5543:0004.0003: input,hidraw1: USB HID v1.00 Mouse [UC-LOGIC Tablet WP5540U] on usb-0000:00:1d.0-1.4/input0

Comment 1 Fedora End Of Life 2013-07-03 21:21:02 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2013-07-31 22:21:46 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.