This list is closed, nobody may subscribe to it.
| 2003 |
Jan
(47) |
Feb
(12) |
Mar
(64) |
Apr
(84) |
May
(51) |
Jun
(52) |
Jul
(51) |
Aug
(19) |
Sep
(18) |
Oct
(72) |
Nov
(67) |
Dec
(18) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(39) |
Feb
(81) |
Mar
(81) |
Apr
(63) |
May
(104) |
Jun
(37) |
Jul
(64) |
Aug
(56) |
Sep
(46) |
Oct
(36) |
Nov
(45) |
Dec
(50) |
| 2005 |
Jan
(47) |
Feb
(58) |
Mar
(40) |
Apr
(49) |
May
(29) |
Jun
(91) |
Jul
(54) |
Aug
(74) |
Sep
(59) |
Oct
(70) |
Nov
(61) |
Dec
(76) |
| 2006 |
Jan
(61) |
Feb
(64) |
Mar
(87) |
Apr
(69) |
May
(41) |
Jun
(85) |
Jul
(80) |
Aug
(41) |
Sep
(50) |
Oct
(27) |
Nov
(112) |
Dec
(49) |
| 2007 |
Jan
(125) |
Feb
(100) |
Mar
(53) |
Apr
(56) |
May
(38) |
Jun
(65) |
Jul
(100) |
Aug
(66) |
Sep
(78) |
Oct
(119) |
Nov
(127) |
Dec
(144) |
| 2008 |
Jan
(74) |
Feb
(67) |
Mar
(117) |
Apr
(109) |
May
(81) |
Jun
(72) |
Jul
(100) |
Aug
(147) |
Sep
(142) |
Oct
(91) |
Nov
(169) |
Dec
(180) |
| 2009 |
Jan
(110) |
Feb
(34) |
Mar
(42) |
Apr
(62) |
May
(131) |
Jun
(70) |
Jul
(68) |
Aug
(65) |
Sep
(109) |
Oct
(125) |
Nov
(71) |
Dec
(260) |
| 2010 |
Jan
(180) |
Feb
(93) |
Mar
(35) |
Apr
(85) |
May
(69) |
Jun
(64) |
Jul
(120) |
Aug
(127) |
Sep
(72) |
Oct
(39) |
Nov
(77) |
Dec
(128) |
| 2011 |
Jan
(190) |
Feb
(147) |
Mar
(110) |
Apr
(99) |
May
(75) |
Jun
(37) |
Jul
(16) |
Aug
(66) |
Sep
(62) |
Oct
(59) |
Nov
(50) |
Dec
(64) |
| 2012 |
Jan
(31) |
Feb
(19) |
Mar
(24) |
Apr
(49) |
May
(53) |
Jun
(46) |
Jul
(8) |
Aug
(29) |
Sep
(2) |
Oct
(42) |
Nov
(27) |
Dec
(28) |
| 2013 |
Jan
(74) |
Feb
(1) |
Mar
(52) |
Apr
(15) |
May
(15) |
Jun
(19) |
Jul
(6) |
Aug
(11) |
Sep
(31) |
Oct
(42) |
Nov
(51) |
Dec
(35) |
| 2014 |
Jan
(24) |
Feb
(1) |
Mar
(19) |
Apr
(30) |
May
(38) |
Jun
(16) |
Jul
(22) |
Aug
(13) |
Sep
(8) |
Oct
(18) |
Nov
(17) |
Dec
(9) |
| 2015 |
Jan
(30) |
Feb
(15) |
Mar
(22) |
Apr
(33) |
May
(14) |
Jun
(3) |
Jul
(9) |
Aug
(8) |
Sep
(12) |
Oct
(64) |
Nov
(40) |
Dec
(39) |
| 2016 |
Jan
(9) |
Feb
(3) |
Mar
(23) |
Apr
(17) |
May
(3) |
Jun
(15) |
Jul
(11) |
Aug
(4) |
Sep
|
Oct
(4) |
Nov
(18) |
Dec
|
| 2017 |
Jan
(20) |
Feb
(30) |
Mar
(39) |
Apr
(18) |
May
(13) |
Jun
(8) |
Jul
|
Aug
(2) |
Sep
|
Oct
(5) |
Nov
(8) |
Dec
|
| 2018 |
Jan
(6) |
Feb
(2) |
Mar
(9) |
Apr
(8) |
May
(15) |
Jun
(2) |
Jul
(6) |
Aug
(4) |
Sep
(6) |
Oct
(2) |
Nov
(1) |
Dec
|
| 2019 |
Jan
(4) |
Feb
(3) |
Mar
(3) |
Apr
|
May
(4) |
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(2) |
|
From: Aaron A. S. <sk...@gm...> - 2019-12-05 19:06:16
|
Hi James, I've reproduced the issue. Please file this issue at: https://github.com/linuxwacom/input-wacom/issues So that we can track it. Background: Centos 7 has two Wacom kernel drivers. The dongle should work with the older wacom kernel driver, but as you report, it does not. I see the dongle working with a Debian system using the same driver, so this may be an issue with RHEL/Centos and its unique driver setup. Best, Aaron On Thu, Dec 5, 2019 at 8:44 AM James Pearson <ja...@mo...> wrote: > I realize this question is for a particular distro's support for a Wacom > device, but I hoping someone here will be able to answer this simple > question: > > Does RHEL/CentOS 7 support a PTH-651 with a wireless kit? > > The wireless dongle is listed (via lsusb) as: > > 'Wacom Co., Ltd ACK-40401 [Wireless Accessory Kit]' (USB ID: 056a:0084) > > I'm asking on behalf of a colleague on the other side of the world - and > I'm told the tablet is not seen by the OS (using a stock EL7.7 kernel) - > but before I try and remotely debug things, I'd thought I'd first check > here to see if it is or isn't supported > > Thanks > > James Pearson > > > _______________________________________________ > Linuxwacom-discuss mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss > |
|
From: James P. <ja...@mo...> - 2019-12-05 16:43:44
|
I realize this question is for a particular distro's support for a Wacom device, but I hoping someone here will be able to answer this simple question: Does RHEL/CentOS 7 support a PTH-651 with a wireless kit? The wireless dongle is listed (via lsusb) as: 'Wacom Co., Ltd ACK-40401 [Wireless Accessory Kit]' (USB ID: 056a:0084) I'm asking on behalf of a colleague on the other side of the world - and I'm told the tablet is not seen by the OS (using a stock EL7.7 kernel) - but before I try and remotely debug things, I'd thought I'd first check here to see if it is or isn't supported Thanks James Pearson |
|
From: Jason G. <kil...@gm...> - 2019-06-04 17:54:11
|
My apologies for the delay in replying... I'm glad to hear that the patch has mostly solved the problem for you :) What additional configuration was required, if I may ask? I'm not very familiar with the control panel codebase but can take a look to see if it might be a symptom of another bug elsewhere. As for the patch, please do go ahead and attach it to your bug report. Hopefully their developers will be along to comment on or apply it soon. Jason --- Now instead of four in the eights place / you’ve got three, ‘Cause you added one / (That is to say, eight) to the two, / But you can’t take seven from three, / So you look at the sixty-fours.... On Fri, May 17, 2019 at 7:22 PM Patrick Rifici <pat...@pr...> wrote: > > Hi Jason, > > Thank you very much for your prompt response, as well as going the extra mile with your patch! I'm pleased to report that the patch appeared to make a positive difference (although it did not completely solve the problem). Thanks to your detailed explanation in the patch notes we were able to apply a manual configuration to the Cintiq that almost completely solved the issue, so that will serve as a good stop-gap for now. I will submit a bug report to KDE shortly. Do you mind if I submit your patch file alongside it? > > Kind regards, > > Patrick. > > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ > On Friday, 17 May 2019 11:56 PM, Jason Gerecke <kil...@gm...> wrote: > > > Ack! I hate it when you only realize a mistake immediately after > > hitting "Send"! I forgot a step between 2 and 3: > > > > Step 2.5: Run `git am 0001-Correct-width-height-values-from-X11Wacom-getMaximum.patch` to > > apply the patch > > > > Jason > > > > ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > > > Now instead of four in the eights place / > > you’ve got three, ‘Cause you added one / > > (That is to say, eight) to the two, / > > But you can’t take seven from three, / > > So you look at the sixty-fours.... > > > > On Fri, May 17, 2019 at 8:54 AM Jason Gerecke kil...@gm... wrote: > > > > > Hi Patrick, > > > We do not maintain the KCM Wacom Tablet module. However, after taking > > > a look at the code, I think I see an issue that could potentially > > > result in the kind of issue issue you're seeing. I've attached a patch > > > that you can try out by following these instructions: > > > > > > 1. Get a copy of v3.1.1 of the KCM module's code by running `git clone https://anongit.kde.org/wacomtablet -b v3.1.1` > > > > > > 2. Download the attached patch and save it into the "wacomtablet" > > > directory created above > > > > > > 3. Follow the "Building & manual installation" instructions found at > > > https://phabricator.kde.org/source/wacomtablet/ to install > > > dependencies and compile the code > > > > > > 4. Follow the "Running without installing" instructions on the same > > > page to try out the modified code. > > > > > > > > > Regardless of if the patch works or not, I would recommend filing a > > > bug at https://bugs.kde.org/enter_bug.cgi?product=wacomtablet to let > > > the KCM developers know of this problem. > > > > > > Jason > > > > > > ------ > > > > > > Now instead of four in the eights place / > > > you’ve got three, ‘Cause you added one / > > > (That is to say, eight) to the two, / > > > But you can’t take seven from three, / > > > So you look at the sixty-fours.... > > > On Thu, May 9, 2019 at 5:02 AM Patrick Rifici via Linuxwacom-discuss > > > lin...@li... wrote: > > > > > > > Hi, > > > > A friend of mine has recently switched to Arch Linux (with KDE Plasma as his desktop) and is using a Cintiq 13HD for drawing with Krita. He has found that after calibrating his tablet, the offset between the cursor and the stylus increases the further away from the center of the drawing area he moves the stylus (at it's worst on the very edge). > > > > He currently runs a dual monitor setup on his Nvidia GTX 1050 Ti, however he has also tried recalibrating his Cintiq without the second display connected. Without the second display connected, the offset is worse (he performs his calibrations through the Wacom Tablet KCM in Plasma Settings). This issue persists both inside and outside of Krita (other drawing programs, empty desktop etc). > > > > Please see below for his specifications and versions: > > > > Kernel Version: 5.0.13 > > > > Xorg Version: 1.20.4 > > > > Wacom Xorg Driver Version: 0.36.1 > > > > Nvidia Driver Version: 418.74 > > > > Wacom Settings KCM Version: 1:3.1.1 > > > > Cintiq Model: Cintiq 13HD > > > > > > > > - Hardware IDs: 056a:0304 > > > > - Connection Type: HDMI > > > > - Resolution: 1920x1080 > > > > Second Display Resolution: 2560x1080 > > > > > > > > > > > > Cintiq Calibration (dual display, default): > > > > > > > > - Map Screen To: Tablet Area > > > > - Tuning Type: Fine > > > > - Horizontal: 373, 58730 > > > > - Vertical: 336, 33150 > > > > > > > > Does anyone have any suggestions that we can try to fix this offset? > > > > > > > > Linuxwacom-discuss mailing list > > > > Lin...@li... > > > > https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss > > |
|
From: Troll de p. <und...@pr...> - 2019-06-01 21:23:23
|
Hello everyone I am on linux mint 19.1 and I am in the process of configuring my Intuos 4 tablet on my machine running this OS. At first I used the cinnamon built-in tablet manager to setup my buttons and it was working good for most of them but I have trouble with the touchwheel : I just want to configure it so it scrolls like my mouse wheel. My problem is not that I can't assign scrolling to the touchwheel but I can't find an option to adjust the scrolling speed either on the mint interface or the xsetwacom command. For the moment it scroll an entire page up or down and it's way too much I want it to scroll only a couple of lines. Is there an option I am missing or this functionality cannot be set by xsetwacom?? Thanks in advance -= Troll de pique =- Sent with [ProtonMail](https://protonmail.com) Secure Email. |
|
From: Patrick R. <pat...@pr...> - 2019-05-18 02:22:23
|
Hi Jason, Thank you very much for your prompt response, as well as going the extra mile with your patch! I'm pleased to report that the patch appeared to make a positive difference (although it did not completely solve the problem). Thanks to your detailed explanation in the patch notes we were able to apply a manual configuration to the Cintiq that almost completely solved the issue, so that will serve as a good stop-gap for now. I will submit a bug report to KDE shortly. Do you mind if I submit your patch file alongside it? Kind regards, Patrick. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Friday, 17 May 2019 11:56 PM, Jason Gerecke <kil...@gm...> wrote: > Ack! I hate it when you only realize a mistake immediately after > hitting "Send"! I forgot a step between 2 and 3: > > Step 2.5: Run `git am 0001-Correct-width-height-values-from-X11Wacom-getMaximum.patch` to > apply the patch > > Jason > > ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Now instead of four in the eights place / > you’ve got three, ‘Cause you added one / > (That is to say, eight) to the two, / > But you can’t take seven from three, / > So you look at the sixty-fours.... > > On Fri, May 17, 2019 at 8:54 AM Jason Gerecke kil...@gm... wrote: > > > Hi Patrick, > > We do not maintain the KCM Wacom Tablet module. However, after taking > > a look at the code, I think I see an issue that could potentially > > result in the kind of issue issue you're seeing. I've attached a patch > > that you can try out by following these instructions: > > > > 1. Get a copy of v3.1.1 of the KCM module's code by running `git clone https://anongit.kde.org/wacomtablet -b v3.1.1` > > > > 2. Download the attached patch and save it into the "wacomtablet" > > directory created above > > > > 3. Follow the "Building & manual installation" instructions found at > > https://phabricator.kde.org/source/wacomtablet/ to install > > dependencies and compile the code > > > > 4. Follow the "Running without installing" instructions on the same > > page to try out the modified code. > > > > > > Regardless of if the patch works or not, I would recommend filing a > > bug at https://bugs.kde.org/enter_bug.cgi?product=wacomtablet to let > > the KCM developers know of this problem. > > > > Jason > > > > ------ > > > > Now instead of four in the eights place / > > you’ve got three, ‘Cause you added one / > > (That is to say, eight) to the two, / > > But you can’t take seven from three, / > > So you look at the sixty-fours.... > > On Thu, May 9, 2019 at 5:02 AM Patrick Rifici via Linuxwacom-discuss > > lin...@li... wrote: > > > > > Hi, > > > A friend of mine has recently switched to Arch Linux (with KDE Plasma as his desktop) and is using a Cintiq 13HD for drawing with Krita. He has found that after calibrating his tablet, the offset between the cursor and the stylus increases the further away from the center of the drawing area he moves the stylus (at it's worst on the very edge). > > > He currently runs a dual monitor setup on his Nvidia GTX 1050 Ti, however he has also tried recalibrating his Cintiq without the second display connected. Without the second display connected, the offset is worse (he performs his calibrations through the Wacom Tablet KCM in Plasma Settings). This issue persists both inside and outside of Krita (other drawing programs, empty desktop etc). > > > Please see below for his specifications and versions: > > > Kernel Version: 5.0.13 > > > Xorg Version: 1.20.4 > > > Wacom Xorg Driver Version: 0.36.1 > > > Nvidia Driver Version: 418.74 > > > Wacom Settings KCM Version: 1:3.1.1 > > > Cintiq Model: Cintiq 13HD > > > > > > - Hardware IDs: 056a:0304 > > > - Connection Type: HDMI > > > - Resolution: 1920x1080 > > > Second Display Resolution: 2560x1080 > > > > > > > > > Cintiq Calibration (dual display, default): > > > > > > - Map Screen To: Tablet Area > > > - Tuning Type: Fine > > > - Horizontal: 373, 58730 > > > - Vertical: 336, 33150 > > > > > > Does anyone have any suggestions that we can try to fix this offset? > > > > > > Linuxwacom-discuss mailing list > > > Lin...@li... > > > https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss |
|
From: Jason G. <kil...@gm...> - 2019-05-17 15:56:24
|
Ack! I hate it when you only realize a mistake immediately after hitting "Send"! I forgot a step between 2 and 3: Step 2.5: Run `git am 0001-Correct-width-height-values-from-X11Wacom-getMaximum.patch` to apply the patch Jason --- Now instead of four in the eights place / you’ve got three, ‘Cause you added one / (That is to say, eight) to the two, / But you can’t take seven from three, / So you look at the sixty-fours.... On Fri, May 17, 2019 at 8:54 AM Jason Gerecke <kil...@gm...> wrote: > > Hi Patrick, > > We do not maintain the KCM Wacom Tablet module. However, after taking > a look at the code, I think I see an issue that could potentially > result in the kind of issue issue you're seeing. I've attached a patch > that you can try out by following these instructions: > > 1. Get a copy of v3.1.1 of the KCM module's code by running `git clone > https://anongit.kde.org/wacomtablet -b v3.1.1` > > 2. Download the attached patch and save it into the "wacomtablet" > directory created above > > 3. Follow the "Building & manual installation" instructions found at > https://phabricator.kde.org/source/wacomtablet/ to install > dependencies and compile the code > > 4. Follow the "Running without installing" instructions on the same > page to try out the modified code. > > Regardless of if the patch works or not, I would recommend filing a > bug at https://bugs.kde.org/enter_bug.cgi?product=wacomtablet to let > the KCM developers know of this problem. > > Jason > --- > Now instead of four in the eights place / > you’ve got three, ‘Cause you added one / > (That is to say, eight) to the two, / > But you can’t take seven from three, / > So you look at the sixty-fours.... > > On Thu, May 9, 2019 at 5:02 AM Patrick Rifici via Linuxwacom-discuss > <lin...@li...> wrote: > > > > Hi, > > > > A friend of mine has recently switched to Arch Linux (with KDE Plasma as his desktop) and is using a Cintiq 13HD for drawing with Krita. He has found that after calibrating his tablet, the offset between the cursor and the stylus increases the further away from the center of the drawing area he moves the stylus (at it's worst on the very edge). > > > > He currently runs a dual monitor setup on his Nvidia GTX 1050 Ti, however he has also tried recalibrating his Cintiq without the second display connected. Without the second display connected, the offset is worse (he performs his calibrations through the Wacom Tablet KCM in Plasma Settings). This issue persists both inside and outside of Krita (other drawing programs, empty desktop etc). > > > > Please see below for his specifications and versions: > > Kernel Version: 5.0.13 > > Xorg Version: 1.20.4 > > Wacom Xorg Driver Version: 0.36.1 > > Nvidia Driver Version: 418.74 > > Wacom Settings KCM Version: 1:3.1.1 > > Cintiq Model: Cintiq 13HD > > - Hardware IDs: 056a:0304 > > - Connection Type: HDMI > > - Resolution: 1920x1080 > > Second Display Resolution: 2560x1080 > > > > Cintiq Calibration (dual display, default): > > - Map Screen To: Tablet Area > > - Tuning Type: Fine > > - Horizontal: 373, 58730 > > - Vertical: 336, 33150 > > > > Does anyone have any suggestions that we can try to fix this offset? > > > > > > _______________________________________________ > > Linuxwacom-discuss mailing list > > Lin...@li... > > https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss |
|
From: Jason G. <kil...@gm...> - 2019-05-17 15:54:48
|
Hi Patrick, We do not maintain the KCM Wacom Tablet module. However, after taking a look at the code, I think I see an issue that could potentially result in the kind of issue issue you're seeing. I've attached a patch that you can try out by following these instructions: 1. Get a copy of v3.1.1 of the KCM module's code by running `git clone https://anongit.kde.org/wacomtablet -b v3.1.1` 2. Download the attached patch and save it into the "wacomtablet" directory created above 3. Follow the "Building & manual installation" instructions found at https://phabricator.kde.org/source/wacomtablet/ to install dependencies and compile the code 4. Follow the "Running without installing" instructions on the same page to try out the modified code. Regardless of if the patch works or not, I would recommend filing a bug at https://bugs.kde.org/enter_bug.cgi?product=wacomtablet to let the KCM developers know of this problem. Jason --- Now instead of four in the eights place / you’ve got three, ‘Cause you added one / (That is to say, eight) to the two, / But you can’t take seven from three, / So you look at the sixty-fours.... On Thu, May 9, 2019 at 5:02 AM Patrick Rifici via Linuxwacom-discuss <lin...@li...> wrote: > > Hi, > > A friend of mine has recently switched to Arch Linux (with KDE Plasma as his desktop) and is using a Cintiq 13HD for drawing with Krita. He has found that after calibrating his tablet, the offset between the cursor and the stylus increases the further away from the center of the drawing area he moves the stylus (at it's worst on the very edge). > > He currently runs a dual monitor setup on his Nvidia GTX 1050 Ti, however he has also tried recalibrating his Cintiq without the second display connected. Without the second display connected, the offset is worse (he performs his calibrations through the Wacom Tablet KCM in Plasma Settings). This issue persists both inside and outside of Krita (other drawing programs, empty desktop etc). > > Please see below for his specifications and versions: > Kernel Version: 5.0.13 > Xorg Version: 1.20.4 > Wacom Xorg Driver Version: 0.36.1 > Nvidia Driver Version: 418.74 > Wacom Settings KCM Version: 1:3.1.1 > Cintiq Model: Cintiq 13HD > - Hardware IDs: 056a:0304 > - Connection Type: HDMI > - Resolution: 1920x1080 > Second Display Resolution: 2560x1080 > > Cintiq Calibration (dual display, default): > - Map Screen To: Tablet Area > - Tuning Type: Fine > - Horizontal: 373, 58730 > - Vertical: 336, 33150 > > Does anyone have any suggestions that we can try to fix this offset? > > > _______________________________________________ > Linuxwacom-discuss mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss |
|
From: Patrick R. <pat...@pr...> - 2019-05-09 12:01:18
|
Hi, A friend of mine has recently switched to Arch Linux (with KDE Plasma as his desktop) and is using a Cintiq 13HD for drawing with Krita. He has found that after calibrating his tablet, the offset between the cursor and the stylus increases the further away from the center of the drawing area he moves the stylus (at it's worst on the very edge). He currently runs a dual monitor setup on his Nvidia GTX 1050 Ti, however he has also tried recalibrating his Cintiq without the second display connected. Without the second display connected, the offset is worse (he performs his calibrations through the Wacom Tablet KCM in Plasma Settings). This issue persists both inside and outside of Krita (other drawing programs, empty desktop etc). Please see below for his specifications and versions: Kernel Version: 5.0.13 Xorg Version: 1.20.4 Wacom Xorg Driver Version: 0.36.1 Nvidia Driver Version: 418.74 Wacom Settings KCM Version: 1:3.1.1 Cintiq Model: Cintiq 13HD - Hardware IDs: 056a:0304 - Connection Type: HDMI - Resolution: 1920x1080 Second Display Resolution: 2560x1080 Cintiq Calibration (dual display, default): - Map Screen To: Tablet Area - Tuning Type: Fine - Horizontal: 373, 58730 - Vertical: 336, 33150 Does anyone have any suggestions that we can try to fix this offset? |
|
From: Peter H. <pet...@wh...> - 2019-03-14 05:00:37
|
On Thu, Mar 14, 2019 at 02:51:17PM +1100, Brendan Scott wrote: > Hi, > > I have a 13" Mobilestudio Pro that I have just managed to get working as a > Cintiq using the link adapter. Things seem to be fine except for the > pointer location. When I use it as a single screen it seems fine. However, > if I have two screens the pointer location is scaled to cover both > screens. For example, if I have the stylus in the bottom left corner of > the tablet the pointer is where the stylus is. As I move the stylus > towards the top right the pointer moves further than the stylus, so when > the stylus is half way the pointer is moving off the edge of the screen. > > I am running opensuse leap 15.0/kernel 4.18.1-1.g2f1304f-default/KDE. > > Help appreciated, this is the standard behaviour of the X server. You'll need either a desktop environment that maps the device to the screen or do it yourself with the "Coordinate Transformation Matrix" (google has heaps of results, there is no single authoritative source). the xinput tool has a "map-to-output" argument which is sufficient in the majority of cases. Cheers, Peter |
|
From: Brendan S. <dis...@ap...> - 2019-03-14 04:03:09
|
Hi, I have a 13" Mobilestudio Pro that I have just managed to get working as a Cintiq using the link adapter. Things seem to be fine except for the pointer location. When I use it as a single screen it seems fine. However, if I have two screens the pointer location is scaled to cover both screens. For example, if I have the stylus in the bottom left corner of the tablet the pointer is where the stylus is. As I move the stylus towards the top right the pointer moves further than the stylus, so when the stylus is half way the pointer is moving off the edge of the screen. I am running opensuse leap 15.0/kernel 4.18.1-1.g2f1304f-default/KDE. Help appreciated, Thanks, Brendan |
|
From: Cole W. <prd...@gm...> - 2019-03-13 13:54:49
|
Hello! I recently tried to build/install the driver needed to use my Wacom Intuos tablet via Linux. However, when I typed in the command necessary, I received the following message: " -bash syntax error near unexpected token 'then'" I am completely new to using Linux, as I've only started using it two days ago, and I have no clue what I'm doing wrong or how to fix it. Please get back to me s soon as you can. Thank you. |
|
From: Ping C. <pin...@gm...> - 2019-02-14 23:56:34
|
On Thu, Feb 14, 2019 at 9:38 AM Carlos <pur...@gm...> wrote: > Hello, > > I was trying to test linux on a Panasonic tablet and the stylus doesn't > What Linux distro and version are you testing, specifically, what kernel version do you run? Please issue "uname -a" if you don't know the kernel version. work, It's quite interesting because neither the ISD_dualTouch nor the > Wacom Components drivers for windows are compatible (I can't install any > Well, Windows driver won't work on Linux. Did you update your Wacom kernel driver from https://github.com/linuxwacom/input-wacom? of them), however the stylus works in windows. Is this some kind of > custom-made digitizer for Panasonic? > I have no idea. But, if it works on Windows, chances are that it also works on Linux. Please update Wacom driver from the link above... Cheers, Ping > |
|
From: Carlos <pur...@gm...> - 2019-02-14 17:37:42
|
Hello, I was trying to test linux on a Panasonic tablet and the stylus doesn't work, It's quite interesting because neither the ISD_dualTouch nor the Wacom Components drivers for windows are compatible (I can't install any of them), however the stylus works in windows. Is this some kind of custom-made digitizer for Panasonic? Regards. |
|
From: John G. <jo...@in...> - 2019-02-05 01:39:38
|
There are some for fairly easy prices. |
|
From: Jason G. <kil...@gm...> - 2019-01-18 17:22:51
|
In case you're interested, here's some of the data that I gathered last year. This is the approximate end-to-end latency (in milliseconds), measured using a high-speed camera. Only 10 runs were done locally because we knew there was no issue, and 20 were attempted through our Teradici setup (with a single 100Mb network switch between the client and server). Some runs are blank because we were unable to extract data from the footage. Test, Run1, Run2, Run3, Run4, Run5, Run6, Run7, Run8, Run9, Run10, Run11, Run12, Run13, Run14, Run15, Run16, Run17, Run18, Run19, Run20, Median, Stdev 1st-gen Intuos Pro (Local), 25, 26, 26, 25, 30, 25, 13, 25, 25, 30, , , , , , , , , , , 25, 4 2nd-gen Intuos Pro (Local), 34, 38, 29, 29, 34, 38, 34, 34, 34, 34, , , , , , , , , , , 34, 3 1st-gen Intuos Pro (Teradici), 68, , , , , , , , , 72, 55, 59, 25, 63, 55, 51, 55, 51, 51, 63, 55, 11 2nd-gen Intuos Pro (Teradici), 72, 143, 63, 59, 67, , 68, 71, 71, 160, 118, 126, 135, 143, 126, 131, 139, 160, 143, 138, 126, 36 The 2nd-gen device sometimes works just as well as the 1st-gen and sometimes exhibits extra latency. Wether the extra latency is there or not seems to be decided the moment you bring the pen into proximity: if you're lucky the whole stroke will be low latency; if not, the whole stroke will be high-latency. Since Teradici thinks it may be bandwidth related, we tried several ways of reducing the amount of data sent by our device (e.g. by disabling touch input to prevent touch packets from being sent). It was hard to tell if there was any effect since we would still periodically see bouts of high latency just like in the normal case. We also weren't able to reduce bandwidth of the 2nd-gen device all the way down to the level used by the 1st-gen. For reference, the 1st-gen hardware sends 1 10-byte pen report roughly every 5 milliseconds (~2 KB/sec). The 2nd-gen hardware sends 1 27-byte pen report roughly every 5 milliseconds (~5.4 KB/sec). Jason --- Now instead of four in the eights place / you’ve got three, ‘Cause you added one / (That is to say, eight) to the two, / But you can’t take seven from three, / So you look at the sixty-fours.... On Mon, Jan 14, 2019 at 7:34 AM James Pearson <ja...@mo...> wrote: > > Thanks for the info - we'll keep pushing Teradici to see if they can fix > this issue > > James > > Ping Cheng wrote: > > > > Hi James, > > > > On Fri, Jan 11, 2019 at 7:28 AM James Pearson <ja...@mo...<mailto:ja...@mo...>> wrote: > > We have issues with using PTH-660 (Intuos Pro2) tablets on CentOS 7 > > workstations that use Teradici KVM extenders - the cursor lags behind > > the pen - which essentially makes the set up unusable ... > > > > Using older Intuos tablets (e.g. PTK-640, PTH-451, etc) works fine on > > the same set up (and the PTH-660's work fine when directly connected to > > the workstation) > > > > We tested Intuos Pro2 with CentOS 7 under Teradici environment intensively last year. We saw delays for Intuos Pro2 then. From our testing, we noticed that delay happened kind of randomly since it did not always happen. However, whenever it happened, the delay started from the beginning when stylus touched the tablet. The same length of delay stayed over the course of the whole drawing process before stylus left proximity. That is, there was no delay added during the use of the tablet. > > > > We've been trying (for a while) to get info from Teradici as to why this > > is the case, and all they have come back with is: > > > > "The underlying USB protocol has changed with the PTH-660. The PTH-660 > > generates much more USB traffic compared to the older wacom tablets, ie. > > the PTk-640. This increase in USB traffic and Pen/cursor traffic will go > > over the same USB channel from client to host can cause lag issues you > > are seeing". > > > > It is true that the protocol for Intuos Pro2 is different from older Intuos/Intuos Pro. The data packet for Intuos Pro2 is larger than older devices. However, we do not think that is the root cause of the delay. We tested the same device on a MS Windows Teradici environment. We did not see extra delay with Intuos Pro2. We feel the delay may be either Linux specific or in Teradici USB/connection initialization process on Linux. Since Teradici client is closed source, we could not trace into it to prove our guess... > > > > I just wanted to check that this is really the case - do the PTH-660 > > tablets generate much more USB traffic than the older tablets? > > > > As I explained above, PTH-660 does have bigger data packets. But, it shouldn't be the reason for the delay. Some kind of network optimization was missing on Linux or in Teradici client, I guess. > > > > Cheers, > > Ping > > > > > > Thanks > > > > James Pearson > > _______________________________________________ > > Linuxwacom-discuss mailing list > > Lin...@li...<mailto:Lin...@li...> > > https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss > > > > _______________________________________________ > Linuxwacom-discuss mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss |
|
From: James P. <ja...@mo...> - 2019-01-14 15:34:22
|
Thanks for the info - we'll keep pushing Teradici to see if they can fix this issue James Ping Cheng wrote: > > Hi James, > > On Fri, Jan 11, 2019 at 7:28 AM James Pearson <ja...@mo...<mailto:ja...@mo...>> wrote: > We have issues with using PTH-660 (Intuos Pro2) tablets on CentOS 7 > workstations that use Teradici KVM extenders - the cursor lags behind > the pen - which essentially makes the set up unusable ... > > Using older Intuos tablets (e.g. PTK-640, PTH-451, etc) works fine on > the same set up (and the PTH-660's work fine when directly connected to > the workstation) > > We tested Intuos Pro2 with CentOS 7 under Teradici environment intensively last year. We saw delays for Intuos Pro2 then. From our testing, we noticed that delay happened kind of randomly since it did not always happen. However, whenever it happened, the delay started from the beginning when stylus touched the tablet. The same length of delay stayed over the course of the whole drawing process before stylus left proximity. That is, there was no delay added during the use of the tablet. > > We've been trying (for a while) to get info from Teradici as to why this > is the case, and all they have come back with is: > > "The underlying USB protocol has changed with the PTH-660. The PTH-660 > generates much more USB traffic compared to the older wacom tablets, ie. > the PTk-640. This increase in USB traffic and Pen/cursor traffic will go > over the same USB channel from client to host can cause lag issues you > are seeing". > > It is true that the protocol for Intuos Pro2 is different from older Intuos/Intuos Pro. The data packet for Intuos Pro2 is larger than older devices. However, we do not think that is the root cause of the delay. We tested the same device on a MS Windows Teradici environment. We did not see extra delay with Intuos Pro2. We feel the delay may be either Linux specific or in Teradici USB/connection initialization process on Linux. Since Teradici client is closed source, we could not trace into it to prove our guess... > > I just wanted to check that this is really the case - do the PTH-660 > tablets generate much more USB traffic than the older tablets? > > As I explained above, PTH-660 does have bigger data packets. But, it shouldn't be the reason for the delay. Some kind of network optimization was missing on Linux or in Teradici client, I guess. > > Cheers, > Ping > > > Thanks > > James Pearson > _______________________________________________ > Linuxwacom-discuss mailing list > Lin...@li...<mailto:Lin...@li...> > https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss > |
|
From: Ping C. <pin...@gm...> - 2019-01-11 22:53:14
|
Hi James, On Fri, Jan 11, 2019 at 7:28 AM James Pearson <ja...@mo...> wrote: > We have issues with using PTH-660 (Intuos Pro2) tablets on CentOS 7 > workstations that use Teradici KVM extenders - the cursor lags behind > the pen - which essentially makes the set up unusable ... > > Using older Intuos tablets (e.g. PTK-640, PTH-451, etc) works fine on > the same set up (and the PTH-660's work fine when directly connected to > the workstation) > We tested Intuos Pro2 with CentOS 7 under Teradici environment intensively last year. We saw delays for Intuos Pro2 then. From our testing, we noticed that delay happened kind of randomly since it did not always happen. However, whenever it happened, the delay started from the beginning when stylus touched the tablet. The same length of delay stayed over the course of the whole drawing process before stylus left proximity. That is, there was no delay added during the use of the tablet. We've been trying (for a while) to get info from Teradici as to why this > is the case, and all they have come back with is: > > "The underlying USB protocol has changed with the PTH-660. The PTH-660 > generates much more USB traffic compared to the older wacom tablets, ie. > the PTk-640. This increase in USB traffic and Pen/cursor traffic will go > over the same USB channel from client to host can cause lag issues you > are seeing". > It is true that the protocol for Intuos Pro2 is different from older Intuos/Intuos Pro. The data packet for Intuos Pro2 is larger than older devices. However, we do not think that is the root cause of the delay. We tested the same device on a MS Windows Teradici environment. We did not see extra delay with Intuos Pro2. We feel the delay may be either Linux specific or in Teradici USB/connection initialization process on Linux. Since Teradici client is closed source, we could not trace into it to prove our guess... > I just wanted to check that this is really the case - do the PTH-660 > tablets generate much more USB traffic than the older tablets? > As I explained above, PTH-660 does have bigger data packets. But, it shouldn't be the reason for the delay. Some kind of network optimization was missing on Linux or in Teradici client, I guess. Cheers, Ping > Thanks > > James Pearson > _______________________________________________ > Linuxwacom-discuss mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss > |
|
From: James P. <ja...@mo...> - 2019-01-11 15:28:01
|
We have issues with using PTH-660 (Intuos Pro2) tablets on CentOS 7 workstations that use Teradici KVM extenders - the cursor lags behind the pen - which essentially makes the set up unusable ... Using older Intuos tablets (e.g. PTK-640, PTH-451, etc) works fine on the same set up (and the PTH-660's work fine when directly connected to the workstation) We've been trying (for a while) to get info from Teradici as to why this is the case, and all they have come back with is: "The underlying USB protocol has changed with the PTH-660. The PTH-660 generates much more USB traffic compared to the older wacom tablets, ie. the PTk-640. This increase in USB traffic and Pen/cursor traffic will go over the same USB channel from client to host can cause lag issues you are seeing". I just wanted to check that this is really the case - do the PTH-660 tablets generate much more USB traffic than the older tablets? Thanks James Pearson |
|
From: James P. <ja...@mo...> - 2018-11-02 12:19:33
|
We're having issues with Cintiq Pro 16 tablets on CentOS 7 when in tablet-only mode (i.e with the Cintiq screen turned off) Everything works fine when the Cintiq monitor is on, however, when switched to tablet-only mode, the stylus no longer moves the pointer on the main screen - lsusb and xsetwacom still 'see' the tablet This is with Gnome3 - plus Nvidia graphics cards using the Nvidia driver for the main and Cintiq monitors Things are even worse when using Mate instead of Gnome3 - again the stylus no longer moves the pointer, but it also partially 'locks' the main display on the workstation - the mouse pointer still moves - but the mouse buttons and keyboard don't respond (Mate is our preferred desktop manager) All starts working again when the Cintiq monitor is turned back on We didn't have this issue with the same hardware when using CentOS 6 (with Gnome2) - tablet-only mode worked fine with CentOS 6 Any ideas what may be causing the issue(s) here? Thanks James Pearson |
|
From: Pedro L. <ped...@gm...> - 2018-10-11 20:43:31
|
Hey guys, I've recently changed my OS from Windows to Linux - the Ubuntu-based distro Elementary version - and I'm in love with how smooth things work. However, I'm having some troubles to use my One by Wacom tablet with the same OS I've written about. It recognizes my tablet - I've checked it using some command in the terminal - and I started building the drivers needed to use: input-wacom and xf86-input-wacom. Everything went fine...no echo "Build error" messages, but I still can't use my tablet. It's seems to me that the OS does not recognize my tablet in the USB port, although it shows it using the command $ sudo lsusb. Have you guys experienced some similar issues using the Elementary OS version? Hugs, Pedro Leocorny |
|
From: Ping C. <pin...@gm...> - 2018-10-04 22:18:17
|
When you say "cannot get the stylus to respond", do you mean your stylus does not move the cursor? If yes, do you see the LED indicator on the tablet, which is beside the ring, changes brightness when your stylus touches the tablet? If not, your stylus might be for a different device. Or, did you test your Intuos 4 on another system or with a different Linux version? I tested it here on my CentOS 7.5. It works fine. Ping On Tue, Oct 2, 2018 at 4:35 PM Shawn Kearney < sha...@us...> wrote: > ------------------------------ > > * [bugs:#360] <https://sourceforge.net/p/linuxwacom/bugs/360/> No Stylus > on CentOS 7.5* > > *Status:* new > *Created:* Tue Oct 02, 2018 11:35 PM UTC by Shawn Kearney > *Last Updated:* Tue Oct 02, 2018 11:35 PM UTC > *Owner:* nobody > > No matter what I am doing, I cannot get the stylus to respond. I've > compiled and installed input-wacom, x86-input-wacom and libwacom without > success. > > I am using CentOS 7.5. > > I have tried running on 3.10.0-862.11.6.el7.x86_64 as well as the latest > mainline. Both results are identical: The tablet is visible to the gnome > settings, but the stylus is not. the stylus does not move the cursor. > > I tried configuring using gnome3 and cinnamon. > > The stylus does not respond and cannot be configured. Gnome3 settings > state "no stylus could be found". > > xsetwacom --list: > Wacom Intuos4 12x19 stylus id: 10 type: STYLUS > Wacom Intuos4 12x19 eraser id: 12 type: ERASER > Wacom Intuos4 12x19 cursor id: 13 type: CURSOR > Wacom Intuos4 12x19 pad id: 14 type: PAD > > All indications seem to suggest it should be working. But it just isn't. > ------------------------------ > > Sent from sourceforge.net because you indicated interest in > https://sourceforge.net/p/linuxwacom/bugs/360/ > > To unsubscribe from further messages, please visit > https://sourceforge.net/auth/subscriptions/ > |
|
From: Pablo L. S. <pa...@ke...> - 2018-09-26 19:57:33
|
Very interesting! However something is wrong: it scrolls the page right to the bottom and I can't scroll back up. I noticed that scroll is slower when the pan is activated from the upper edge of the tablet. So maybe the middle point is right on the top edge? ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Wednesday, September 26, 2018 10:51 AM, Jason Gerecke kil...@gm... wrote: > Recent versions of the xf86-input-wacom driver support a "pan" action > that translates pen drags into mousewheel scrolls. Its not exactly > what you want (no kinetic scrolling), but is closer to the desired > experience. You can run e.g. xsetwacom set <id> button 2 pan to > cause up/down and left/right scroll events to be sent whenever the pen > is dragged while button 2 is held. See man xsetwacom and search for > "pan". > Jason > --------------------------------------------------------------- > > Now instead of four in the eights place / > you’ve got three, ‘Cause you added one / > (That is to say, eight) to the two, / > But you can’t take seven from three, / > So you look at the sixty-fours.... > On Wed, Sep 26, 2018 at 1:11 AM Pablo López Soriano pa...@ke... wrote: > >> Thanks Peter. >> Evince actually has this feature. I mentioned to give example :) >> How about emulating a touchscreen? Gtk+ has this "kinetic-scrolling" property that switches ON when detecting a touchscreen display. https://developer.gnome.org/gtk3/stable/GtkScrolledWindow.html#gtk-scrolled-window-get-kinetic-scrolling >> -------- Original Message -------- >> On 26 Sep 2018, 01:41, Peter Hutterer < pet...@wh...> wrote: >> On Tue, Sep 25, 2018 at 08:30:16PM +0000, Pablo López Soriano wrote: >> >>> Hello everyone \o/ >>> My goal is to get scrolling with the Stylus as good as the one in Evince >>> (Document Viewer). On Evince, Middle Mouse Button grabs the page and uses >>> kinetic scrolling to drag it around. I tried solutions like EasyStroke but >>> it's far from ideal. >>> After much unfruitful searching, I had an idea: Could we remap a Sylus >>> button (or the MMB) to send the "two-finger scroll" event in X11? >>> Another idea is to make X11 believe the Stylus input is a Touchscreen. >>> Then, GTK+ apps would scroll as if swiping a finger. >>> I'm using Fedora 28 with GNOME 3.28. >> >> honestly, all you'd be doing here is to add a hack on the lower levels to >> trick the upper levels into doing what you want. The devil's in the details >> here too because scroll motion can have different coordinate spaces than >> normal motion, so simple 1:1 translation may not work. You may be fixing >> Evince this way, but some other application may require some different >> interaction/movement/etc. >> I recommend to push for adding the button+move == scroll ability in GTK >> instead, or Evince directly. >> Cheers, >> Peter >> Linuxwacom-discuss mailing list >> Lin...@li... >> https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss |
|
From: Jason G. <kil...@gm...> - 2018-09-26 09:51:49
|
Recent versions of the xf86-input-wacom driver support a "pan" action that translates pen drags into mousewheel scrolls. Its not exactly what you want (no kinetic scrolling), but is closer to the desired experience. You can run e.g. `xsetwacom set <id> button 2 pan` to cause up/down and left/right scroll events to be sent whenever the pen is dragged while button 2 is held. See `man xsetwacom` and search for "pan". Jason --- Now instead of four in the eights place / you’ve got three, ‘Cause you added one / (That is to say, eight) to the two, / But you can’t take seven from three, / So you look at the sixty-fours.... On Wed, Sep 26, 2018 at 1:11 AM Pablo López Soriano <pa...@ke...> wrote: > > Thanks Peter. > > Evince actually has this feature. I mentioned to give example :) > > How about emulating a touchscreen? Gtk+ has this "kinetic-scrolling" property that switches ON when detecting a touchscreen display. https://developer.gnome.org/gtk3/stable/GtkScrolledWindow.html#gtk-scrolled-window-get-kinetic-scrolling > > > > > > > -------- Original Message -------- > On 26 Sep 2018, 01:41, Peter Hutterer < pet...@wh...> wrote: > > > On Tue, Sep 25, 2018 at 08:30:16PM +0000, Pablo López Soriano wrote: > > Hello everyone \o/ > > > > My goal is to get scrolling with the Stylus as good as the one in Evince > > (Document Viewer). On Evince, Middle Mouse Button grabs the page and uses > > kinetic scrolling to drag it around. I tried solutions like EasyStroke but > > it's far from ideal. > > > > After much unfruitful searching, I had an idea: Could we remap a Sylus > > button (or the MMB) to send the "two-finger scroll" event in X11? > > > > Another idea is to make X11 believe the Stylus input is a Touchscreen. > > Then, GTK+ apps would scroll as if swiping a finger. > > > > I'm using Fedora 28 with GNOME 3.28. > > honestly, all you'd be doing here is to add a hack on the lower levels to > trick the upper levels into doing what you want. The devil's in the details > here too because scroll motion can have different coordinate spaces than > normal motion, so simple 1:1 translation may not work. You may be fixing > Evince this way, but some other application may require some different > interaction/movement/etc. > > I recommend to push for adding the button+move == scroll ability in GTK > instead, or Evince directly. > > Cheers, > Peter > > _______________________________________________ > Linuxwacom-discuss mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss |
|
From: Pablo L. S. <pa...@ke...> - 2018-09-26 08:10:46
|
Thanks Peter. Evince actually has this feature. I mentioned to give example :) How about emulating a touchscreen? Gtk+ has this "kinetic-scrolling" property that switches ON when detecting a touchscreen display. https://developer.gnome.org/gtk3/stable/GtkScrolledWindow.html#gtk-scrolled-window-get-kinetic-scrolling -------- Original Message -------- On 26 Sep 2018, 01:41, Peter Hutterer wrote: > On Tue, Sep 25, [2018](tel:2018) at 08:30:16PM +0000, Pablo López Soriano wrote: >> Hello everyone \o/ >> >> My goal is to get scrolling with the Stylus as good as the one in Evince >> (Document Viewer). On Evince, Middle Mouse Button grabs the page and uses >> kinetic scrolling to drag it around. I tried solutions like EasyStroke but >> it's far from ideal. >> >> After much unfruitful searching, I had an idea: Could we remap a Sylus >> button (or the MMB) to send the "two-finger scroll" event in X11? >> >> Another idea is to make X11 believe the Stylus input is a Touchscreen. >> Then, GTK+ apps would scroll as if swiping a finger. >> >> I'm using Fedora 28 with GNOME 3.28. > > honestly, all you'd be doing here is to add a hack on the lower levels to > trick the upper levels into doing what you want. The devil's in the details > here too because scroll motion can have different coordinate spaces than > normal motion, so simple 1:1 translation may not work. You may be fixing > Evince this way, but some other application may require some different > interaction/movement/etc. > > I recommend to push for adding the button+move == scroll ability in GTK > instead, or Evince directly. > > Cheers, > Peter |
|
From: Peter H. <pet...@wh...> - 2018-09-26 00:58:39
|
On Tue, Sep 25, 2018 at 08:30:16PM +0000, Pablo López Soriano wrote: > Hello everyone \o/ > > My goal is to get scrolling with the Stylus as good as the one in Evince > (Document Viewer). On Evince, Middle Mouse Button grabs the page and uses > kinetic scrolling to drag it around. I tried solutions like EasyStroke but > it's far from ideal. > > After much unfruitful searching, I had an idea: Could we remap a Sylus > button (or the MMB) to send the "two-finger scroll" event in X11? > > Another idea is to make X11 believe the Stylus input is a Touchscreen. > Then, GTK+ apps would scroll as if swiping a finger. > > I'm using Fedora 28 with GNOME 3.28. honestly, all you'd be doing here is to add a hack on the lower levels to trick the upper levels into doing what you want. The devil's in the details here too because scroll motion can have different coordinate spaces than normal motion, so simple 1:1 translation may not work. You may be fixing Evince this way, but some other application may require some different interaction/movement/etc. I recommend to push for adding the button+move == scroll ability in GTK instead, or Evince directly. Cheers, Peter |