[Hardy] Mousing from one screen to another with tablet doesn't work any more

Confirming.

I have just upgraded to Hardy. Switching the display worked with Gutsy (display driver: NVIDIA-Linux-x86_64-1.0-9755), but does not work with Hardy (display driver: NVIDIA-Linux-x86_64-174.55 for CUDA 2.0 BETA). As the same problem exists with the nvidia-glx-new drivers, the driver does not seem to be the reason for the problem.

Uname: Linux 2.6.24-16-generic x86_64

As per https://wiki.ubuntu.com/X/Reporting, could you please attach /var/log/Xorg.0.log from a session exhibiting the problem?

Marked incomplete until Xorg log attached.

I added my Xorg.0.log and xorg.conf.

Commenting out the "Twinview" "horizontal" option in the xorg.conf, sets this option to the default value "none". This way the tablet is mapped to both screen. So I can reach the second screen, but using a 3:4 tablet on a 3:8 screen is not handy.

Using both, the "Twinview" "horizontal" and "ScreenNo" "1" options, results in a mapping only to the left screen, as one could expect, but setting "ScreenNo" "2" does not map the tablet to the right screen. It just adds a small displacement of the mapping of about 8 pixels to the right, so that I can no longer reach the left edge of the left screen, but the 8 leftmost pixels of the right screen. The same happens if I comment out the "ScreenNo" option.

I tried to comment out the "ForceDevice" "ISDV4" which is set by default, but the problem still remained.

Kay,

Do you also have a Graphire? I'm preparing to send this bug upstream, and I want to make sure everything here is accurate.

Oh, sorry. I just forgot to add the model I am using. It is the CTE-640, so it is not the A6, but the A5 Version. I am using Xubuntu, not ubuntu. We have a second computer here running ubuntu (not xubuntu) with an older graphire ET-0405A-U, which shows the same problem after the upgrade to Hardy.

I am new in reporting bugs. Does anything change for me, when you submit the bug to upstream, or do I still get all information here in launchpad?

What happens is I'll go to their page, and write up a bug there, then link it here. Launchpad will track the status, but not the comments etc. Since the upstream author will most likely ask more questions. Since you already have a launchpad account, once launchpad has the bug linked, just click on it and log in with openID (LP is an openID provider, see https://help.launchpad.net/OpenID) and subscribe to the bug. (You'll need to use the non 2.0 method listed at the bottom of the page).

I realize that this bug is quite old now, and related to Hardy. However, I seem to be able to reproduce it in Intrepid and I think that the solution is to compile the xorg wacom driver with the "--enable-quirk-tablet-rescale" argument to configure.

Paul, would you mind trying to reproduce this in Jaunty? Also, have you actually built and tried the binaries with that configure? I don't have a Graphire to reproduce this on.

Unfortunately I don't have a Jaunty machine around at the moment (nor any machine to spare). I'll see if I can do something about it.

I solved my problem (in Intrepid) by removing both the xserver-xorg-input-wacom and wacom-tools packages, and compiling the linuxwacom-0.8.2-2-tarball from the Linux Wacom project's website. I configured it with the "--enable-quirk-tablet-rescale" argument, and now it works.

For the record I should state that my tablet is the Wacom Bamboo. I forgot to mention that in my first comment.
Also, I forgot to mention that I got the hint from this thread: http://www.nabble.com/Cursor-stuck-in-the-wrong-screen-in-TwinView-mode-td21686575.html

Sorry for the long delay, but I finally got around trying this with Jaunty. The result is the same: Problems with the wacom-tools package. Again it is solved by enabled the "quirk tablet rescale" option to configure.

Would it be possible to make the --enable-quirk-tablet-rescale option default again? It was a really great feature and I think the combination of using a tablet and using dual head is not uncommon. If there are no serious drawbacks this would be a quite easy way to improve the usability of ubuntu.

As Paul already wrote: The Problem still exists in jaunty, not only in hardy.

Although I repeat myself, it would be great to have this configure option used by default.

Can anyone reproduce this issue on karmic?

I have no karmic installed, but I could repoduce it with the Alpha 5 karmic-desktop-amd64 live system after installing the nvidia drivers.

I also tried to compile the 0.8.4-1 release of linuxwacom myself using the --enable-quirk-tablet-rescale configure option, but I think i did something wrong, because after rebooting the tablet was mapped relative (instead of absolut) and the height of the screens was mapped to half the height of the tablet. This way the aspect ratio was correct, but it was not the right option to make the cursor stick to one screen and switch to the other one, when crossing the border.

@noiq - thanks for providing that info, but we would like to see it from the original reporter. We may want to send this bug report upstream, but upstream has a hard and fast rule that logs from someone other than the original reporter are not acceptable. The reason for that is that quite often with X.org bug reports, two people may *think* they have the same issue based on commonality of symptoms and/or hardware, but in truth they have separate issues and mixing the report and the files can cause the developers some confusion.

If this bug report seems not to be getting attention, I would encourage you to file a new bug report with this data, and simply reference this bug report in your bug description.

I just tried again to follow Pauls suggestions, but the production version (0.8.4-4) does not compile a kernel module (.ko) and the latest version (0.8.5-10) and older versions of the linuxwacom drivers do not seem to support the 2.6.31 kernel yet. The easiest workaroud is just using the tablet with one monitor deactivated.
With the xsetwacom provided by ubuntu I get a segmentation fault when I try to set my tablet to some TwinView mode:

$ xsetwacom set "Wacom Graphire4 6x8 cursor" twinview "hirizontal"
Segmentation fault

while changing the rotation works fine.

I will try to file a new bug later. Thanks for your hint.

Finally!

It was just my lack of knowledge about how HAL works. xsetwacom still does not work for me, but I can set the xorg TwinView option by adding

  <merge key="input.x11_options.TwinView" type="string">horizontal</merge>

to the wacom section in /usr/share/hal/fdi/policy/20thirdparty/10-linuxwacom.fdi or by creating a new file in /etc/hal/fdi/policy with

<?xml version="1.0" encoding="ISO-8859-1"?>
<!-- this is probably a bit imprecise -->
<deviceinfo version="0.2">
  <device>
    <match key="info.category" contains="input">
      <match key="info.product" contains_outof="Wacom">
 <merge key="input.x11_options.TwinView" type="string">horizontal</merge>
      </match>
    </match>
  </device>
</deviceinfo>

Maybe this solves other problems, too.

Thank you for reporting this issue with wacom-tools, we are migrating all of these bug reports over to the xf86-input-wacom package as this replaces the older package in the development version of Ubuntu.

This would be a good point for you to re-test this issue against the new package to see if is still occurring. If not, you can mark it as Fix Released in Launchpad.

[This is an automatic notification.]

Hi Christoph,

This bug was reported against an earlier version of Ubuntu, can you
test if it still occurs on Lucid?

Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue through
normal support channels, please see:

    http://www.ubuntu.com/support

If you are the original reporter and can still reproduce the issue on
Lucid, please run the following command to refresh the report:

  apport-collect 209911

If you are not the original reporter, please file a new bug report, so
we can work with you as the original reporter instead (you can reference
bug 209911 in your report if you think it may be related):

  ubuntu-bug xorg

If by chance you can no longer reproduce the issue on Lucid or if you
feel it is no longer relevant, please mark the bug report 'Fix Released'
or 'Invalid' as appropriate, at the following URL:

  https://bugs.launchpad.net/ubuntu/+bug/209911

Since I don't use two screens anymore, i can't retest this issue.