Hide Forgot
Description of problem: When using the x230t with a second monitor attached, the stylus and touchscreen movements on the display are incorrectly placed entirely on the second monitor. This occurs when the second display is being used to extend the desktop. How reproducible: Always Steps to Reproduce: 1. Install RHEL7.0 on the x230t. 2. Plug in second monitor. 3. Try using the stylus or touchscreen on the x230t's display. Actual results: All movements are placed on the second monitor, not the tablets display. Expected results: The stylus and touchscreen only operate on the x230t's built in display.
Can you confirm this is still an issue? And if so, can you please post the product ID of the device? Thanks. The Wacom section in /proc/bus/input/devices will do.
I: Bus=0003 Vendor=056a Product=00e6 Version=0139 N: Name="Wacom ISDv4 E6 Pen" P: Phys= S: Sysfs=/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/input/input9 U: Uniq= H: Handlers=mouse2 event9 B: PROP=2 B: EV=b B: KEY=1c03 0 0 0 0 0 B: ABS=1000003 I: Bus=0003 Vendor=056a Product=00e6 Version=0139 N: Name="Wacom ISDv4 E6 Finger" P: Phys= S: Sysfs=/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.1/input/input10 U: Uniq= H: Handlers=mouse3 event10 B: PROP=2 B: EV=b B: KEY=400 0 0 0 0 0 B: ABS=260800000000003 The problem is still occurring with both the stylus and touch.
Carlos, what's going on here, can you have a look please? This bit is controlled by g-s-d.
I've just attached some patches on the upstream bug https://bugzilla.gnome.org/show_bug.cgi?id=709600 that will fix this and other issues like bug #1029612. On that other bug I was pondering that the wacom module changes are maybe too invasive, although seeing this other bug, maybe it is worth to have something unified here.
Moving this over to g-s-d as per comment #4.
(In reply to Carlos Garnacho from comment #4) > I've just attached some patches on the upstream bug > https://bugzilla.gnome.org/show_bug.cgi?id=709600 that will fix this and > other issues like bug #1029612. > > On that other bug I was pondering that the wacom module changes are maybe > too invasive, although seeing this other bug, maybe it is worth to have > something unified here. I'm fine backporting the fixes, but I think that we should make the changes upstream first. Let's handle this upstream first (and land it in 3.8 and 3.10), and target 7.1 to make sure that the changes aren't causing major regressions.
During testing of 7.2 Prebeta, I noticed this issue is no longer present. I believe this can be closed as current release, unless we want to wait until the actual beta.
closing, according to comment 11