[regression] Bug 216946 - Toshiba satellite click mini l9w-b: touchscreen: no touch events with kernel 6.1.4

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi, this is your Linux kernel regression tracker.

I noticed a regression report in bugzilla.kernel.org. As many (most?)
kernel developer don't keep an eye on it, I decided to forward it by
mail. Quoting from https://bugzilla.kernel.org/show_bug.cgi?id=216946 :

>  Gé Koerkamp 2023-01-17 20:21:51 UTC
> 
> Created attachment 303619 [details]
> Kernel configuration for v6.1.4/ journalctl (dmesg)/ ACPIdump/lsmod
> 
> Overview: 
> The touchscreen does not react on touch events.
> Touchscreen display and touchpad are working.
> 
> Step to reproduce:
> Open any UI page
> Try to use touch on relevant UI controls (buttons etc.)
> 
> Result:
> No reaction on screen touches
> 
> Expected result:
> Reaction on touched control, same as when using the touch pad or connected mouse (which do work).
> 
> Build information:
> The error happens with kernel version 6.1.4
> After rebuilding with different kernel versions, it appears that it first fails with kernel 5.16
> 
> Additional builds:
> The click mini l9w-b still works with kernel 5.10.y LTS and 5.15.y LTS.
> 
> Important remark:
> Touchscreen still works fine with kernel 6.1.4 using  
> - an HP x2 detachable 10-p0xx or
> - a Lenovo yoga 520-14ikb
> 
> So it could be a hardware dependent issue

See the ticket for more details.


[TLDR for the rest of this mail: I'm adding this report to the list of
tracked Linux kernel regressions; the text you find below is based on a
few templates paragraphs you might have encountered already in similar
form.]

BTW, let me use this mail to also add the report to the list of tracked
regressions to ensure it's doesn't fall through the cracks:

#regzbot introduced: v5.15..v5.16
https://bugzilla.kernel.org/show_bug.cgi?id=216946
#regzbot title: hid: touchscreen broken with Toshiba satellite click
mini l9w-b
#regzbot ignore-activity

This isn't a regression? This issue or a fix for it are already
discussed somewhere else? It was fixed already? You want to clarify when
the regression started to happen? Or point out I got the title or
something else totally wrong? Then just reply and tell me -- ideally
while also telling regzbot about it, as explained by the page listed in
the footer of this mail.

Developers: When fixing the issue, remember to add 'Link:' tags pointing
to the report (e.g. the buzgzilla ticket and maybe this mail as well, if
this thread sees some discussion). See page linked in footer for details.

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
If I did something stupid, please tell me, as explained on that page.



[Index of Archives]     [Linux Media Devel]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Linux Wireless Networking]     [Linux Omap]

  Powered by Linux