Bug 1177564 - Touchpad Bug Ideapad 5
Touchpad Bug Ideapad 5
Classification: openSUSE
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Kernel
64bit openSUSE Tumbleweed
: P5 - None : Major (vote)
: ---
Assigned To: openSUSE Kernel Bugs
E-mail List
Depends on:
  Show dependency treegraph
Reported: 2020-10-11 22:31 UTC by Nasa
Modified: 2022-01-07 13:18 UTC (History)
3 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---
tiwai: needinfo? (rujbin)


Note You need to log in before you can comment on or make changes to this bug.
Description Nasa 2020-10-11 22:31:07 UTC

theres a very annoying Bug in Tumbleweed. My friend bought an Ideapad 5, it works fine, i started the installer like 4-5 times to check if the touchpad is bugged as it is known if u search "Ideapad 5 Linux touchpad" 
It wasnt bugged in the Installer. The Ideapad 5 has the 4500U Ryzen 5 CPU with AMD Radeon Graphics.

After i installed Tumbleweed, the chance that the touchpad gets detected is 50 %. It wasnt so when i was in the installer, and i was like 3-4 times. It shows my Cursor for 1 second when i boot and KDE is loading, but when kde has been finished with loading, theres no cursor. I am using KDE Wayland with default settings. After a Reboot the Touchpad gets recognized.

Its the ideapad 5 15are05 and the Bug is known. But i would like to know if i should refund it or if it will definitly gets fixed. I dont want to make a BIOS Update on a Computer which isnt mine, its too risky that the laptop gets completly unuseable. I also dont think that a BIOS Update will help, when it always got recognized on Windows and the next 3 reboots when i started the YasT2 Installer(Tumbleweed).
Comment 1 Takashi Iwai 2020-10-12 16:12:41 UTC
Could you give hwinfo output?  At best taken from both working and non-working states.  Upload the outputs to Bugzilla.
Comment 2 Takashi Iwai 2020-10-12 16:31:45 UTC
Also, please don't touch the Priority field on Bugzilla.  It's a field to be adjusted only developer's side.  The reporter can adjust Severity state instead.
Comment 3 Miroslav Beneš 2022-01-07 13:18:04 UTC
Closing, no response