[Bug 1685343] Re: Tap to click dies after a short period
Turns out the synaptics module was getting loaded as well. When I removed this with sudo apt-get purge xserver-xorg-input-synaptics and then set up the libinout tap setting with a set-prop all was well. ** Changed in: xserver-xorg-input-libinput (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685343 Title: Tap to click dies after a short period To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1685343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685343] [NEW] Tap to click dies after a short period
Public bug reported: Upgraded from 16.04 to 17.04, Dell 9350. Using version 1.6.2 of xinput. Using libinput for touchpad, no Synaptics installed. After a variable but short period (usually within 5 minutes) the tap to click functionality of the touchpad stops working. Nothing of note in syslog or dmesg. Peculiarly, sudo libinput-debug-events --enable-tap continues to show the correct output for taps (e.g. BTTN_LEFT etc) even after the UI stops responding to taps. So it may well be that it is not libinput? But I had to start somewhere! What is the event handling chain after libinput? Any pointers towards where I might look for an issue? ** Affects: xserver-xorg-input-libinput (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685343 Title: Tap to click dies after a short period To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1685343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1654918] Re: No Internet access with default of Automatic (DHCP)
Same thing on an upgrade from 16.04 to 17.04. Some internet immediately after the upgrade, same issue as noted above with software updates needing multiple tries to access the repos, currently internet completely dead even with a reboot. Note this was a Software Updater suggested dist upgrade - I think that should be pulled, 17.04 shouldn't be auto suggesting for users in this state. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1654918 Title: No Internet access with default of Automatic (DHCP) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1654918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
