dock not recognized once reconnected
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
With my lenovo Helix 2, and in 20.04, when I remove the tablet part (it is a convertible), control is properly passed to the tablet part.
However, I plug it back into the keyboard dock, this dock is not recognized. So neither keys nor touchpad get re-activated. Logout-Login doesn't solve the problem. Only a full reboot makes the keyboard and built-in touchpad come back.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/
CasperMD5CheckR
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
HibernationDevice: RESUME=
InstallationDate: Installed on 2019-03-14 (573 days ago)
InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: LENOVO 20CHS1KL00
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=
ProcVersionSign
RelatedPackageV
linux-
linux-
linux-firmware 1.187.3
Tags: focal
Uname: Linux 5.4.0-48-generic x86_64
UpgradeStatus: Upgraded to focal on 2020-09-29 (7 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 03/24/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: N17ETB2W (2.12 )
dmi.board.
dmi.board.name: 20CHS1KL00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50510 WIN
dmi.chassis.
dmi.chassis.type: 11
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.family: ThinkPad Helix 2nd
dmi.product.name: 20CHS1KL00
dmi.product.sku: LENOVO_
dmi.product.
dmi.sys.vendor: LENOVO
Thank you for taking the time to report this bug and helping to make Ubuntu better.
This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. I have classified this bug as a bug in 'linux' due to the hardware issues that you are experiencing.
When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https:/ /help.ubuntu. com/community/ ReportingBugs.