[Ubuntu-x-swat] [Bug 532137]

2018-06-12 Thread Chris Bagwell
I quickly looked at the Xorg.log files from launchpad below.  Right
after hotplug of tablet, usbParse() goes in infinite loop and prints
message about invalid serial #.  Not positive its infinite loop but at
least the log stops with no messages beyond repeating error message.  If
you wait long enough, perhaps the tablet corrects itself?

Intuos1 and Intuos2 are unique in that they get serial # from hardware
itself and used by xf86-input.wacom.  Serial # is a unique value that
allows tracking multiple tools at once.

You've found a case were tablet streams out packets in a way that serial
# is sent as zero.  Either tablet is saying a zero value or else an if()
statement is getting confused and not allowing to init values correctly.

This is all on kernel side, BTW.

Since I do not own own of these tablets, I do not have much more to
offer.  I can only say it appears mostly a kernel side bug from
information so far.

BTW: the best place to discuss wacom bugs is at project page bug tracker
or mailing list:  http://linuxwacom.sourceforge.net

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xf86-input-wacom in Ubuntu.
https://bugs.launchpad.net/bugs/532137

Title:
  Wacom Intuos2 tablet hotplug only works once after booting

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/532137/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 883319]

2012-04-10 Thread Chris Bagwell
Created attachment 59557
Sample fix for panning/scaling

Attached patch has been posted to mailing list for discussion but no
replies so far.  Posting here so it doesn't get lost.

This combines fix for panning from another patch and adds scaling fix as
well.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/883319

Title:
  xrandr --scale restricts area in which mouse moves

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/883319/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 881046]

2012-04-05 Thread Chris Bagwell
Created attachment 59557
Sample fix for panning/scaling

Attached patch has been posted to mailing list for discussion but no
replies so far.  Posting here so it doesn't get lost.

This combines fix for panning from another patch and adds scaling fix as
well.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/881046

Title:
  Panning in a virtual monitor is not possible after upgrade to Ubuntu
  11.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/881046/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 883319]

2012-04-03 Thread Chris Bagwell
I reviewed the other patchwork patches just now.  Patch 6209 in Comment
7 addresses panning part of issue in crtc_bounds() using same logic from
ProcRRGetCrtcInfo().

If you combine my modification from Comment 17 with the patch 6209 then
you'll get solution for both scaling and panning.

Not sure its the right solution and it seems a little excessive to
compute each X/Y movement... but I hope it helps move us along to final
solution.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/883319

Title:
  xrandr --scale restricts area in which mouse moves

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/883319/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 883319]

2012-04-03 Thread Chris Bagwell
I use xrandr for scaling to make a small netbook screen able to display
apps that don't fit in 1024x600 and noticed this regression over the
last year in 1.11.  I finally decided to look closer since 1.12 didn't
seem to fix the issue and came across this report.

I looked at the revert commit to get idea of area that could possibly be
fixed and it seems like crtc_bounds() is probably a function that should
be returning a value related to panning/scaling.

I traced were xrandr output is querying the panning/scaling values it
displays and looks like comes from ProcRRGetCrtcInfo() and that function
makes use of RRCrtcGetScanoutSize() to scaling width/height to correct
size.  Panning uses rrGetPanning().

To test the idea, I modified crtc_bounds to handle scaling case by
adding ProcRRGetCrtcInfo() call.  It does seem to work and I've not
noticed a negative in limitted testing.

I patched a source RPM so I can't offer a real patch right now but here
is my modified version of function to get an idea:

static void
crtc_bounds(RRCrtcPtr crtc, int *left, int *right, int *top, int *bottom)
{
int width, height;
RRCrtcGetScanoutSize (crtc, &width, &height);

*left = crtc->x;
*top = crtc->y;

switch (crtc->rotation) {
case RR_Rotate_0:
case RR_Rotate_180:
default:
   *right = crtc->x + width;
   *bottom = crtc->y + height;
   return;
case RR_Rotate_90:
case RR_Rotate_270:
   *right = crtc->x + height;
   *bottom = crtc->y + width;
   return;
}
}

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/883319

Title:
  xrandr --scale restricts area in which mouse moves

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/883319/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 881046]

2012-03-27 Thread Chris Bagwell
I reviewed the other patchwork patches just now.  Patch 6209 in Comment
7 addresses panning part of issue in crtc_bounds() using same logic from
ProcRRGetCrtcInfo().

If you combine my modification from Comment 17 with the patch 6209 then
you'll get solution for both scaling and panning.

Not sure its the right solution and it seems a little excessive to
compute each X/Y movement... but I hope it helps move us along to final
solution.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/881046

Title:
  Panning in a virtual monitor is not possible after upgrade to Ubuntu
  11.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/881046/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 881046]

2012-03-27 Thread Chris Bagwell
I use xrandr for scaling to make a small netbook screen able to display
apps that don't fit in 1024x600 and noticed this regression over the
last year in 1.11.  I finally decided to look closer since 1.12 didn't
seem to fix the issue and came across this report.

I looked at the revert commit to get idea of area that could possibly be
fixed and it seems like crtc_bounds() is probably a function that should
be returning a value related to panning/scaling.

I traced were xrandr output is querying the panning/scaling values it
displays and looks like comes from ProcRRGetCrtcInfo() and that function
makes use of RRCrtcGetScanoutSize() to scaling width/height to correct
size.  Panning uses rrGetPanning().

To test the idea, I modified crtc_bounds to handle scaling case by
adding ProcRRGetCrtcInfo() call.  It does seem to work and I've not
noticed a negative in limitted testing.

I patched a source RPM so I can't offer a real patch right now but here
is my modified version of function to get an idea:

static void
crtc_bounds(RRCrtcPtr crtc, int *left, int *right, int *top, int *bottom)
{
int width, height;
RRCrtcGetScanoutSize (crtc, &width, &height);

*left = crtc->x;
*top = crtc->y;

switch (crtc->rotation) {
case RR_Rotate_0:
case RR_Rotate_180:
default:
   *right = crtc->x + width;
   *bottom = crtc->y + height;
   return;
case RR_Rotate_90:
case RR_Rotate_270:
   *right = crtc->x + height;
   *bottom = crtc->y + width;
   return;
}
}

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/881046

Title:
  Panning in a virtual monitor is not possible after upgrade to Ubuntu
  11.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/881046/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 854445] Re: Asus ep121 (eee slate) touchscreen not working

2011-11-27 Thread Chris Bagwell
The discussion then moved over to linux-input mailing list were it got
fully resolved by hid-multitouch developer.  A fix will be in Linux 3.3
(its in a hid next branch).  The fix is slightly larger than adding new
product ID's to hid-multitouch.  The touchscreen uses a "MT serial"
protocol that happened to be added to hid-multitouch for another
touchscreen in November timeframe as well.  This version of eGalax
touchscreen makes use of that new feature in hid-multitouch.

This issue is pure kernel side issue and nothing to change in xf86
-input-evdev if you want to reassign bug report.  If your interested in
more why xf86-input-evdev was acting strange with HW you can look at
thread in comment #4.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.launchpad.net/bugs/854445

Title:
  Asus ep121 (eee slate) touchscreen not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/854445/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp