[qubes-users] Re: Touchscreen not working on Qubes 3.2
On Saturday, December 30, 2017 at 4:24:20 AM UTC-5, Vít Šesták wrote: > While both mouse and touchscreen have some similarities (both are pointing > devices), there are also some important differences: > > First, mouse reports relative movements, while touchscreen reports absolute > positions of touch. > Second, mouse reports two different types of events (movement and clicks*), > while touchscreen reports just touches. > Third, touchscreen might report multiple pointers. > > For those reasons, touchscreen needs a different proxy, which is not > implemented yet. > > Regards, > Vít Šesták 'v6ak' > > *) Scrolling is AFAIK a specific type of button. I see, only time this happened to me was an older baremetal fedora release with lxde on an old laptop, I had to add entries to xorg file. So in this case only solution is not use a sys-usb? Or just not use touchscreen I guess... -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/bc194b1d-63c4-406b-afa4-ad411c51ff79%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Touchscreen not working on Qubes 3.2
While both mouse and touchscreen have some similarities (both are pointing devices), there are also some important differences: First, mouse reports relative movements, while touchscreen reports absolute positions of touch. Second, mouse reports two different types of events (movement and clicks*), while touchscreen reports just touches. Third, touchscreen might report multiple pointers. For those reasons, touchscreen needs a different proxy, which is not implemented yet. Regards, Vít Šesták 'v6ak' *) Scrolling is AFAIK a specific type of button. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/8677bc98-f7c1-490f-b28e-4cd6cb243f5e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Touchscreen not working on Qubes 3.2
On Thursday, March 2, 2017 at 6:02:56 AM UTC-5, atlahua wrote: > ISSUE: Touchscreen and all other USB devices assigned to the same USB bus > stop working > > On Qubes 3.1 I found a workaround solution assining the USB bus that manages > the touchscreen to dom0 (on sys-usb services tab). The touch screen started > working. The disadvantage in terms of security is that the other devices > assigned to this bus (USB port and built-in camera were also assigned to dom0. > > The news is that after upgrading to Qubes 3.2, this workaround solution does > not work anymore. Thinking that it might be related to having Xfce instead of > KDE I swaped the desktop environment to KDE as instructed in your help pages > but it seems that was not the issue. Also all other devices on the same bus > stopped working, that is, the computer does not even detect a pendrive to one > of the USB ports on the computer. > > All the USB devices work fine when re-assinged to sys-usb, except from the > touchscreen, that is. > > ___Laptop: Asus TP300LA > 4GB > [user@sys-usb /]$ lsusb > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > **Bus 002 Device 005: ID 03eb:8b03 Atmel Corp.** > Bus 002 Device 004: ID 064e:9700 Suyin Corp. Asus Integrated Webcam > Bus 002 Device 003: ID 8087:07dc Intel Corp. > Bus 002 Device 002: ID 8087:8000 Intel Corp. > Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > i'm not sure, but maybe you need to manually enable mouse proxy for it, check its enabled correctly? https://www.qubes-os.org/doc/usb/ -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/c996a3a3-4e38-4062-8d9d-7fb771c80fe6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Touchscreen not working on Qubes 3.2
AFAIK this is related to kernel option rd.qubes.hide_all_usb, not to Xfce vs. KDE. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/ed1775c2-c396-4451-87da-61e38027cec0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Touchscreen not working on Qubes 3.2
Same issue with Dell precision M3800. This was working in previous versions of Qubes, 3.1 I think. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/03654db4-88c5-4b6b-bdd8-37b5505cbe0c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Touchscreen not working on Qubes 3.2
Am Donnerstag, 2. März 2017 12:02:56 UTC+1 schrieb atlahua: > ISSUE: Touchscreen and all other USB devices assigned to the same USB bus > stop working > > On Qubes 3.1 I found a workaround solution assining the USB bus that manages > the touchscreen to dom0 (on sys-usb services tab). The touch screen started > working. The disadvantage in terms of security is that the other devices > assigned to this bus (USB port and built-in camera were also assigned to dom0. > > The news is that after upgrading to Qubes 3.2, this workaround solution does > not work anymore. Thinking that it might be related to having Xfce instead of > KDE I swaped the desktop environment to KDE as instructed in your help pages > but it seems that was not the issue. Also all other devices on the same bus > stopped working, that is, the computer does not even detect a pendrive to one > of the USB ports on the computer. > > All the USB devices work fine when re-assinged to sys-usb, except from the > touchscreen, that is. > > ___Laptop: Asus TP300LA > 4GB > [user@sys-usb /]$ lsusb > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > **Bus 002 Device 005: ID 03eb:8b03 Atmel Corp.** > Bus 002 Device 004: ID 064e:9700 Suyin Corp. Asus Integrated Webcam > Bus 002 Device 003: ID 8087:07dc Intel Corp. > Bus 002 Device 002: ID 8087:8000 Intel Corp. > Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > Issue : Touchscreen on Samsung ATIV Book 9 Plus not working On Qubes 3.2: Does anyone know how to activate the touch screen ? Please help. Tom -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/428d2082-10c5-4aec-ab1c-ff2ac5795dcc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
