Bug 1002851 - DTU-1931 Interactive Pen Display, Data file missing
Summary: DTU-1931 Interactive Pen Display, Data file missing
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libwacom
Version: 6.3
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Peter Hutterer
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-30 06:30 UTC by Siddharth Sharma
Modified: 2016-04-28 22:05 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-28 22:05:33 UTC
Target Upstream Version:

Attachments (Terms of Use)
Data File for dtu-1931 (499 bytes, patch)
2013-08-30 06:32 UTC, Siddharth Sharma 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Description Siddharth Sharma 2013-08-30 06:30:50 UTC 
Description of problem:
Missing data file causing too big offset between stylus and event area

Version-Release number of selected component (if applicable):
libwacom-data-0.5-4

Actual results:
too big offset between stylus and event area

Expected results:
proper offset between stylus and event area

Additional info:
Comment 1 Siddharth Sharma 2013-08-30 06:32:15 UTC 
Created attachment 792035 [details]
Data File for dtu-1931

Data file patch added for correcting offsets of wacom dtu-1931
~siddharth sharma
Comment 4 RHEL Program Management 2013-10-14 02:28:50 UTC 
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 5 Michael Boisvert 2016-04-28 17:49:20 UTC 
Quite an old bug on an old tablet with a 3 year old NEEDINFO. I think it would be safe to close this one Peter.
Comment 6 Peter Hutterer 2016-04-28 22:05:33 UTC 
This data file was added with the rebase to libwacom 0.8 in RHEL 6.6. Closing the bug.
Note You need to log in before you can comment on or make changes to this bug.