stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: "André Kunz" <donatusmusic@gmx.de>, stable@vger.kernel.org
Cc: regressions@lists.linux.dev
Subject: Re: Found a bug with my gaming gear
Date: Fri, 17 Nov 2023 16:01:26 +0100	[thread overview]
Message-ID: <88a14de8-ceaf-4c1d-ba6c-6cfbbffa0e2a@redhat.com> (raw)
In-Reply-To: <bd1a6eb1-a8af-4181-b9e4-c7b8d3af1eea@gmx.de>

Hi André,

On 11/16/23 23:41, André Kunz wrote:
> Hey there guys,
> 
> This is my first kernel "bug" report ever, so please bear with me if I
> didn't catch the precise right way to report this.
> 
> The bug I've found:
> 
> I'm running stable kernel 6.6.1-1 and as soon as I install it, many of
> my mouse's hardware buttons stop working. I have a Logitech G502 X Plus
> (it's a wireless mouse). As soon as I install 6.6.1 the mouse's hardware
> buttons won't work, i.e. only the two side-buttons would work, not the
> buttons (and/or my created profiles/macros) would. I have a few macros
> assigned to some buttons, which work perfectly fine under 6.5.11 (and
> earlier), but as soon as I'm on 6.6 they'd stop working.
> 
> Just wanted to report this and I hope there can be a fix.
> 
> I hope this email was not too much out of the ordinary.

For starters lets collect some logs and see if that explains
anything.

Can you do the following:

1. Boot the working 6.5.11, wiggle the mouse (so that it connects)
and the run:

dmesg > dmesg-6.5.11.txt

2. Boot the non working 6.6.1, wiggle the mouse and run:

dmesg > dmesg-6.6.1.txt

And then attach both generated dmesg-...txt files to your next email ?

Regards,

Hans




  parent reply	other threads:[~2023-11-17 15:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-16 22:41 Found a bug with my gaming gear André Kunz
2023-11-17 13:49 ` Greg KH
2023-11-17 15:01 ` Hans de Goede [this message]
2023-11-19 23:15 ` Bagas Sanjaya

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=88a14de8-ceaf-4c1d-ba6c-6cfbbffa0e2a@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=donatusmusic@gmx.de \
    --cc=regressions@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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).