** Tags added: cscc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776266
Title:
Touchpad and keyboard of MacBook unresponsive
To manage notifications about this bug go to:
https://bugs.launchpad.n
Last update for people finding this via google: Changed the ribbon cable
from the touchpad to the motherboard. New cable has flaws as well,
force-click is not working. :-| But no unresponsiveness anymore. So
definitely a hardware issue.
Why on earth would Linux crap out while macOS works flawlessl
Opened up the laptop and wiggled on the touchpad/keyboard ribbon cable.
Problem is not gone, but definitely better. Seems like a hardware issue
indeed. Why there are no problems with macOS is beyond me though.
Somehow Linux has less tolerance for flaky connections?
--
You received this bug notifi
Yeah, it's permanent now.
Maybe it's connected to the USB mode. I can imagine that in grub it
would be a low protocol version (USB 1.0 or 2.0) and that it's set to
USB 3.0 during the boot. At least in normal cables there would be more
lines for USB 3.0 than for the lower variants, so maybe the int
Did this issue return? Is it still happening sporadically?
I have exactly the same issue (I'm even getting the same usb bus/device
numbers). Sometimes it works fine first time. sometimes it fails until I
power cycles a few times until it eventually detects the hardware.
Unfortunately today I've re
Apologies, I see that yours is now in this state permanently too, and
your also GRUB works fine (which is super annoying and proves that the
hardware is capable of operating to some degree)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776266
Title:
Touchpad and keyboard of MacBook unresponsive
To manage notifications a
Addendum: Got lucky and the hardware was found at next boot. Does not
happen often, though. For comparison, this is the dmesg log when it
works as it should:
[0.00] Linux version 4.15.0-22-generic (buildd@lgw01-amd64-013) (gcc
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #24-Ubuntu SMP Wed May
