linux-kernel - Re: [Regression] Bug 216395 - XP-Pen Star G430S stops working on any kernel newer than 5.18.7

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <nycvar.YFH.7.76.2208261304470.19850@cbobk.fhfr.pm>
Date:   Fri, 26 Aug 2022 13:05:44 +0200 (CEST)
From:   Jiri Kosina <jikos@...nel.org>
To:     Thorsten Leemhuis <regressions@...mhuis.info>
cc:     Benjamin Tissoires <benjamin.tissoires@...hat.com>,
        gomapo2868@...e-cart.com, LKML <linux-kernel@...r.kernel.org>,
        "open list:HID CORE LAYER" <linux-input@...r.kernel.org>,
        "regressions@...ts.linux.dev" <regressions@...ts.linux.dev>,
        Roman Romanenko <romu4444@...il.com>,
        Nikolai Kondrashov <spbnick@...il.com>,
        José Expósito <jose.exposito89@...il.com>
Subject: Re: [Regression] Bug 216395 - XP-Pen Star G430S stops working on
 any kernel newer than 5.18.7

On Fri, 26 Aug 2022, Thorsten Leemhuis wrote:

> Hi, this is your Linux kernel regression tracker.
> 
> I noticed a regression report in bugzilla.kernel.org that afaics nobody
> acted upon since it was reported. That's why I decided to forward it by
> mail to those that afaics should handle this.
> 
> To quote from https://bugzilla.kernel.org/show_bug.cgi?id=216395 :
> 
> >  gomapo2868@...e-cart.com 2022-08-22 16:28:00 UTC
> > 
> > XP-Pen Star G430S stops working on newer kernels than 5.18.7 (5.18.8, 5.19, 6.0rc1 tested)
> > It seems to use the uclogic drivers.
> 
> See the ticket for details and further comments.

Thorsten, thanks for the report.

CCing people who have been working on XP-Pen support recently (Roman, 
Nikolai, José).

Keeping the rest of the mail below for reference.

> 
> Please look into the issue if you're among the main recipients of this
> mail (and not just CCed). I hope I picked the right people to sent this
> to, if not just let everyone know (and apologies for getting it wrong!).
> 
> Anyway, to ensure this is not forgotten lets get this tracked by the the
> Linux kernel regression tracking bot:
> 
> #regzbot introduced: v5.18..5.18.7
> https://bugzilla.kernel.org/show_bug.cgi?id=216395
> #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 -- ideally with also
> telling regzbot about it, as explained here:
> https://linux-regtracking.leemhuis.info/tracked-regression/
> 
> Reminder for developers: When fixing the issue, add 'Link:' tags
> pointing to the report in bugzilla, as the kernel's documentation calls
> for; above page explains why this is important for tracked regressions.
> 
> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
> 
> P.S.: As the Linux kernel's regression tracker I deal with a lot of
> reports and sometimes miss something important when writing mails like
> this. If that's the case here, don't hesitate to tell me in a public
> reply, it's in everyone's interest to set the public record straight.
> 

-- 
Jiri Kosina
SUSE Labs