Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Logitec MX Anywhere 3 configuration gone after reboot #921

Open
CH-1967 opened this issue Dec 14, 2023 · 2 comments
Open

Logitec MX Anywhere 3 configuration gone after reboot #921

CH-1967 opened this issue Dec 14, 2023 · 2 comments
Labels

Comments

@CH-1967
Copy link

CH-1967 commented Dec 14, 2023

Information

  • ratbagd version (ratbagd --version): 0.16
  • Piper version: 0.7
  • Distribution: Linux Mint
  • Device: Logitec MX Aywhere 3
  • Kernel version (ex. uname -srmo): Linux 5.15.0-91-generic x86_64 GNU/Linux

Describe the error
I can configure the buttons via Piper.
This works perfectly.
However, after a restart this setting is gone again and I have to set it again.

Reproduce
I start Pieper
Change my key assignment
Restart
Configuration is gone again.

With
ratbagctl hollering-marmot info
I get the following information.

Before customizing via beeper

hollering-marmot - MX Anywhere 3
Model: bluetooth:046d:b025:0
Number of Buttons: 7
Number of leds: 0
Number of Profiles: 1
Profile 0: (active)
Name: n/a
Resolutions:
0: 1000dpi (active)
Button: 0 is mapped to 'button 1'
Button: 1 is mapped to 'button 2'
Button: 2 is mapped to 'button 3'
Button: 3 is mapped to 'button 4'
Button: 4 is mapped to 'button 5'
Button: 5 is mapped to 'ratchet-mode-switch'
Button: 6 is mapped to UNKNOWN

After customizing

hollering-marmot - MX Anywhere 3
Model: bluetooth:046d:b025:0
Number of Buttons: 7
Number of leds: 0
Number of Profiles: 1
Profile 0: (active)
Name: n/a
Resolutions:
0: 1000dpi (active)
Button: 0 is mapped to 'button 1'
Button: 1 is mapped to 'button 2'
Button: 2 is mapped to 'ratchet-mode-switch'
Button: 3 is mapped to 'button 4'
Button: 4 is mapped to 'button 5'
Button: 5 is mapped to 'button 3'
Button: 6 is mapped to UNKNOWN

The change is visible.
But it is gone again after the restart.

I am currently testing whether I should switch from WIndows to Linux.
So I don't know much about Linux yet.
But it would be important for me to be able to set the key assignment of the mouse permanently. I'm just kind of used to certain things.
I would be grateful for any tips / help. If possible something more detailed so that I know how to implement it.

Thanks a lot
Roland

@CH-1967 CH-1967 added the bug label Dec 14, 2023
@jpriollaud
Copy link

Mine are gone even after a screen lock + unlock.

@czinehuba
Copy link
Contributor

I can confirm that happens with the MX anywhere 3 business as well

This was referenced Oct 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants