[Desktop-packages] [Bug 1913211] [NEW] lenovo ideapad 730s touchpad wrist detection not working
Public bug reported: Lenovo ideapad 730s touchpad wrist detection does not work. I have tried both synaptics and libinput drivers. The libinput driver's scroll coasting does not work. With the synaptics driver, using synclient to set PalmDetect=1 has no effect. In KDE's touchpad settings, pressure-dependant motion, sensitivity, and palm detection are all greyed out. I am running kubuntu 20.10 and the 5.11 kernel. >From evtest: /dev/input/event4: MSFT0001:00 04F3:30BC Mouse /dev/input/event5: MSFT0001:00 04F3:30BC Touchpad ** Affects: xserver-xorg-input-libinput (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1913211 Title: lenovo ideapad 730s touchpad wrist detection not working Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: Lenovo ideapad 730s touchpad wrist detection does not work. I have tried both synaptics and libinput drivers. The libinput driver's scroll coasting does not work. With the synaptics driver, using synclient to set PalmDetect=1 has no effect. In KDE's touchpad settings, pressure-dependant motion, sensitivity, and palm detection are all greyed out. I am running kubuntu 20.10 and the 5.11 kernel. From evtest: /dev/input/event4: MSFT0001:00 04F3:30BC Mouse /dev/input/event5: MSFT0001:00 04F3:30BC Touchpad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1913211/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
with lenovo ideapad 730s, wrist and pressure detection still don't work under
5.11.
with libinput, scroll coasting doesn't work.
I am current back to using synaptics. using synclient to turn PalmDetect on
has no effect.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1887190
Title:
MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Status in Pop!_OS:
New
Status in linux package in Ubuntu:
Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
Confirmed
Status in linux package in Arch Linux:
Fix Committed
Status in linux package in Fedora:
Confirmed
Status in linux package in openSUSE:
New
Bug description:
Update (based on #296)
=
The latest kernel tree
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
has the complete solution to fix this bug. So we can expect kernel
v5.11 to fix this issue without any additional work.
Before the release of v5.11, you are suggested to use #189 to save your
touchpad. Note that for distributions like Ubuntu and Fedora, the pinctrl-amd
driver is built into the initramfs. So you have to rebuild the initramfs after
replacing the old module with new one.
On Fedora, run `sudo dracut --force`; On ubuntu, run `sudo update-initramfs
-u`.
The complete solution is three patches,
- 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce
filter setting in IRQ type setting")
- 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way
to disable debounce filter")
- 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into
account debounce settings")
The first two patches has reached the stable tree. If the last one is
also backported to LTS kernel, you won't need to install kernel 5.11.
But I don't know when this will happen.
Original bug report
===
Hello
The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at
all (pointer and click never move when touchpad is touched). This has been
reported by other users in various websites, with various linux systems
including other Ubuntu systems, but I saw no launchpad bug so I post one.
Example of websites covering the issue :
- https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly
the same laptop)
- https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar
laptop)
xinput indentifies it as MSFT0001:00 04F3:3140
Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4[slave pointer
(2)]
⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer
(2)]
⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer
(2)]
⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave
pointer (2)]
⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer
(2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard id=5[slave
keyboard (3)]
↳ Ideapad extra buttons id=15 [slave
keyboard (3)]
↳ Power Buttonid=6[slave
keyboard (3)]
↳ Integrated Camera: Integrated C id=10 [slave
keyboard (3)]
↳ Video Bus id=7[slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave
keyboard (3)]
↳ Power Buttonid=9[slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave
keyboard (3)]
↳ AT Translated Set 2 keyboardid=18 [slave
keyboard (3)]
↳ Video Bus id=8[slave
keyboard (3)]
Thanks a lot for your time. It does not help, but I can confirm what
was reported on askubuntu by another user : the touchpad does work on
Windows.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-40-generic 5.4.0-40.44
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: nicolas1567 F pulseaudio
/dev/snd/controlC1: nicolas1567 F pulseaudio
/dev/snd/controlC2: nicolas1567 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Jul 10 20:14:25 2020
InstallationDate: Installed on 2020-07-02 (8 days ago)
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Before I grab'n'build 5.11, I'd like to know if my issue is similar.
I have a lenovo ideapad 730s.
The touchpad works fine for pointing, single, double and triple clicks.
I have tried both the synaptics and libinput drivers. It's been a while since
I was comparing them; IIRC, I'm currently running the synaptics driver as
libinput didn't have scrolling/coasting working.
My problem is that palm detection and pressure sensitivity do not work.
This makes the laptop pretty much unusable as it is almost impossible to
do any text entry without the insertion point jumping to wherever the
pointer was left.
Might the 5.11 kernel fix it?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1887190
Title:
MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Status in Pop!_OS:
New
Status in linux package in Ubuntu:
Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
Confirmed
Status in linux package in Arch Linux:
Fix Committed
Status in linux package in Fedora:
Confirmed
Status in linux package in openSUSE:
New
Bug description:
Update (based on #296)
=
The latest kernel tree
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
has the complete solution to fix this bug. So we can expect kernel
v5.11 to fix this issue without any additional work.
Before the release of v5.11, you are suggested to use #189 to save your
touchpad. Note that for distributions like Ubuntu and Fedora, the pinctrl-amd
driver is built into the initramfs. So you have to rebuild the initramfs after
replacing the old module with new one.
On Fedora, run `sudo dracut --force`; On ubuntu, run `sudo update-initramfs
-u`.
The complete solution is three patches,
- 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce
filter setting in IRQ type setting")
- 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way
to disable debounce filter")
- 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into
account debounce settings")
The first two patches has reached the stable tree. If the last one is
also backported to LTS kernel, you won't need to install kernel 5.11.
But I don't know when this will happen.
Original bug report
===
Hello
The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at
all (pointer and click never move when touchpad is touched). This has been
reported by other users in various websites, with various linux systems
including other Ubuntu systems, but I saw no launchpad bug so I post one.
Example of websites covering the issue :
- https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly
the same laptop)
- https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar
laptop)
xinput indentifies it as MSFT0001:00 04F3:3140
Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4[slave pointer
(2)]
⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer
(2)]
⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer
(2)]
⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave
pointer (2)]
⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer
(2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard id=5[slave
keyboard (3)]
↳ Ideapad extra buttons id=15 [slave
keyboard (3)]
↳ Power Buttonid=6[slave
keyboard (3)]
↳ Integrated Camera: Integrated C id=10 [slave
keyboard (3)]
↳ Video Bus id=7[slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave
keyboard (3)]
↳ Power Buttonid=9[slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave
keyboard (3)]
↳ AT Translated Set 2 keyboardid=18 [slave
keyboard (3)]
↳ Video Bus id=8[slave
keyboard (3)]
Thanks a lot for your time. It does not help, but I can confirm what
was reported on askubuntu by another user : the touchpad does work on
Windows.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-40-generic 5.4.0-40.44
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion:
[Desktop-packages] [Bug 330833] Re: NetworkManager always overwrites default route when connecting to OpenVPN network
it's 2019 and the same bug still exists. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/330833 Title: NetworkManager always overwrites default route when connecting to OpenVPN network Status in NetworkManager-OpenVPN: Invalid Status in network-manager package in Ubuntu: Invalid Status in network-manager-openvpn package in Ubuntu: Fix Released Status in network-manager package in Debian: New Status in network-manager package in Fedora: Invalid Bug description: Binary package hint: network-manager My office VPN has IMAP, (forwarding) DNS services and not much else. It doesn't forward client traffic to the Internet. This means I can't use the VPN server as a default gateway. Every time I connect to the VPN using NetworkManager/OpenVPN, my routing table gets a default route to the VPN. I've tried everything to avoid this in both the Intrepid package and the version from the network manager PPA with no success. Even telling NetworkManager to ignore routes from the server doesn't work. As it is right now, I have to connect to the VPN, delete the default route, and re-add my wireless router as the default gateway before I can have both email and web access. See attached routing table details. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 8.10 NonfreeKernelModules: nvidia Package: network-manager 0.7-0ubuntu1~nm1~intrepid1 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: network-manager Uname: Linux 2.6.27-11-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-openvpn/+bug/330833/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 738757] Re: spindown settings lost on pm-suspend indirectly affects powernap power savings
This is still broken (or broken again) in 16.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/738757 Title: spindown settings lost on pm-suspend indirectly affects powernap power savings Status in hdparm package in Ubuntu: Fix Released Status in pm-utils package in Ubuntu: Invalid Bug description: Binary package hint: hdparm Upon wakeup from pm-suspend, all spindown settings on drives as set in hdparm.conf are lost and drives will not spindown until reboot. This will affect the performance of such useful packages such as powernap, since drives will not enter spindown after the first time a system is suspended and then resumed. Power will be wasted, watts that could be saved will be lost!!! Upon investigation I found that a similar problem has been found and fixed for APM settings by use of the script /usr/lib/pm-utils/power.d /95hdparm-apm, which restores '-B' APM hdparm settings on capable drives following power events if laptop-mode-tools are not installed. Since laptop-mode-tools is not a suitable package for a server environment, it is important the hdparm provide a similar script for spindown. Indeed, hdparms has already set the precedent that it should provide such backstop functionality as part of the package to support pm-utils functionality for critical drive parameters. I have prepared a patch file that is more or less a clone of the script used for the APM functionality, but which restores the '-S' spindown hdparm parameters. I suggest that it be placed in /usr/lib /pm-utils/sleep.d/95hdparm-spindown. I kept the hdparm-try-apm test so that it will not apply to USB or firewire drives, and also kept the logic so that is applied only on drives that support APM (figured that test wouldn't hurt and might be important). I assumed it would not apply in pm-powersave and so moved it from power.d/ to sleep.d/. As a side note, I also have a patch I am submitting to powernap to extend functionality to add a monitor plugin that will key off drive standby/sleep state. The patch will only work, however, if the drives spindown more than once per boot... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hdparm/+bug/738757/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
