Bug 334520

Summary:	Calibration fails on Tablet PC if external screen is connected and tablet mapped to internal screen
Product:	[Plasma] wacomtablet	Reporter:	thisguy642
Component:	general	Assignee:	Jörg Ehrichs <Joerg.Ehrichs>
Status:	RESOLVED WORKSFORME
Severity:	normal
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description thisguy642 2014-05-08 15:18:03 UTC

Kubuntu 14.04, product version reported as 2.0.

Reproducible: Always

Steps to Reproduce:
1. Connect an external screen (whether as primary or secondary doesn't matter)
2. Map tablet area to Tablet PC screen only (using "Full tablet" option) and apply settings.
3. Run the calibration tool for touch or stylus, apply settings.
4. Touch the screen with whatever was supposedly calibrated
Actual Results:  
No matter where the screen is touched, the cursor always jumps to the top of the screen. It can be moved left and right, but not down.

Expected Results:  
The cursor goes where you touched the screen.

Mapping touch to "full tablet" makes my touch-enabled area too small, but works for the stylus. The touch-enabled area can only be calibrated correctly by using "xsetwacom --set <...> Area" with known-good values from xinput_calibrator (obtained without an external screen connected) or dragging the screen edges in the tool until they line up with the same known-good values.

Comment 1 Andrew Crouthamel 2018-11-11 04:22:08 UTC

Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!

Comment 2 Andrew Crouthamel 2018-11-21 04:39:18 UTC

Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!

Comment 3 Justin Zobel 2023-01-12 01:58:01 UTC

Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!

Comment 4 Bug Janitor Service 2023-01-27 05:08:07 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 5 Bug Janitor Service 2023-02-11 03:52:39 UTC

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!