[Kernel-packages] [Bug 1581088] Re: Middle mouse (wheel-click) button stopped working after upgrade to 16.04

2018-05-07 Thread Leo Milano
Ok, I guess this is embarrassing, but as I was trying James' workaround in #92 , I started thinking that somehow the signal was weak or intermittent. A few minutes later, Solaar (the GUI that displays status of Logitech wireless devices) tells me that the battery level in the mouse was down to 5%.

[Kernel-packages] [Bug 1581088] Re: Middle mouse (wheel-click) button stopped working after upgrade to 16.04

2018-01-07 Thread Leo Milano
Same as Kristin #85 : Disconnecting the USB receiver in a port, and connecting it in the USB port just besides it, has been working for some time now. Middle click is now recognized in System Settings. Ubuntu 16.04, NVIDIA drivers. xinput list ⎡ Virtual core pointer id=2

[Kernel-packages] [Bug 1308264] Re: Ubuntu 14.04 Beta 2 stuck at Switched to clocksource tsc when booting up, then resumes booting to the login screen, after 1 minute

2015-01-25 Thread Leo Milano
Same here, I am running the current version of Xubuntu 15.04 on an HP Chromebook 14 Falco, and the (50s) delay disappears when using the tpm_tis.force=1 option in grub. I wonder if this has to do with loading Ubuntu from coreboot, since the setting is related to Trusted Platform management

[Kernel-packages] [Bug 1386077] Re: [Dell XPS 13 9333] Touchpad not detected on Ubuntu 14.10

2014-11-04 Thread Leo Milano
Christopher, I am not sure what you mean. I experienced exactly the same bug as described here (Touchpad not detected on Ubuntu 14.10) on exactly the same hardware (Dell XPS 13), under the exact same conditions (upgrade from 14.10). I am providing information in the interest of helping handle the

[Kernel-packages] [Bug 1386077] Re: [Dell XPS 13 9333] Touchpad not detected on Ubuntu 14.10

2014-11-03 Thread Leo Milano
Same here. I have an xps 13 running ubuntu 14.10. When I upgraded from 12.04 (as installed by dell) into 14.04, I had to blacklist i2c_hid. After upgrading to 14.10, i needed to remove the blacklisting, as others reported. Here is the interesting thing: I needed to blacklist two different i2c