archive mirror
 help / color / mirror / Atom feed
From: "Linux regression tracking (Thorsten Leemhuis)"  <>
To: "Pali Rohár" <>
Cc: Steffen <>,
	Linux kernel regressions list <>,
	Dmitry Torokhov <>,
	"open list:HID CORE LAYER" <>,
	LKML <>
Subject: [regression] Bug 217182 - Dell Latitude E7450 Trackpoint not working as expected
Date: Mon, 13 Mar 2023 11:20:14 +0100	[thread overview]
Message-ID: <> (raw)

Hi, Thorsten here, the Linux kernel's regression tracker.

I noticed a regression report in As many (most?)
kernel developer don't keep an eye on it, I decided to forward it by
mail. Quoting from :

>  Steffen 2023-03-12 11:17:02 UTC
> Hi,
> I'm new to this bug tracking system and just a user, not a developer.
> I use a Dell Latitude E7450 running with the Debian unstable based
> distribution Siduction.
> After upgrading to Linux kernel 6.2.x the Trackpoint does not work
> anymore as expected. It uses an Alps PS/2 DualPoint Stick.
> Even slight touches in any direction send the cursor to the top right
> corner of the screen where it stays regardless of actual pointer
> movement. This also appears in console mode. One can retrieve the
> pointer again with the touchpad, but I'm more precise with the
> Trackpoint and prefer using that.
> The Trackpoint works well in kernel 6.1.14
> Can somebody help?

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

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: v6.1..v6.2
#regzbot title: input: alps: Dell Latitude E7450 Trackpoint acting up
#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:
If I did something stupid, please tell me, as explained on that page.

             reply	other threads:[~2023-03-13 10:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-13 10:20 Linux regression tracking (Thorsten Leemhuis) [this message]
2023-03-15  9:50 ` [regression] Bug 217182 - Dell Latitude E7450 Trackpoint not working as expected Thorsten Leemhuis
2023-03-19 16:51   ` Pali Rohár
2023-04-17 11:46 ` Linux regression tracking #update (Thorsten Leemhuis)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).