Bug 2192668 - Mouse acceleration cannot be disabled
Summary: Mouse acceleration cannot be disabled
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: mutter
Version: 38
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: GNOME SIG Unassigned
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-05-02 17:04 UTC by Chester
Modified: 2024-05-21 14:52 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-05-21 14:52:50 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Chester 2023-05-02 17:04:44 UTC
Starting with F38, mouse acceleration seems to be always active no matter what is dictated in the settings.

In Gnome Settings, it is disabled. In Gnome Tweaks, it is set to "Flat", however there is still clearly some adaptive acceleration going on. This was working fine in F37.

Reproducible: Always

Steps to Reproduce:
1. Disable mouse acceleration in Gnome Settings
2. Perform tests with cursor
3. Notice that mouse accel is still in effect
Actual Results:  
Mouse acceleration is still in effect

Expected Results:  
Acceleration should respect the "Flat" profile

Comment 1 Chester 2023-07-09 03:33:20 UTC
I ended up filing a bug upstream, here:
https://gitlab.gnome.org/GNOME/mutter/-/issues/2893

Comment 2 Aoife Moloney 2024-05-21 14:52:50 UTC
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21.

Fedora Linux 38 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.