Bug 147341

Summary: The shortcuts of form 'alt+*' are not working as they used to before Libreoffice version 7.2.*
Product: LibreOffice Reporter: aystic <pmohitb3011>
Component: WriterAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: pmohitb3011
Priority: medium    
Version: 7.3.0.3 release   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
Crash report or crash signature: Regression By:
Attachments: The attachment shows the shortcut that has been set for the "alt+R" keybinding and The unexpected behaviour that is happening on pressing the shortcut

Description aystic 2022-02-10 10:30:36 UTC
Created attachment 178185 [details]
The attachment shows the shortcut that has been set for the "alt+R" keybinding and The unexpected behaviour that is happening on pressing the shortcut

===========Libreoffice version details=============
Version: 7.3.0.3 / LibreOffice Community
Build ID: 0f246aa12d0eee4a0f7adcefbf7c878fc2238db3
CPU threads: 8; OS: Linux 5.13; UI render: default; VCL: gtk3
Locale: en-IN (en_IN); UI: en-US
Calc: threaded

============Issue===================
I had some shortcuts setup for different character styles. For example, I had the shortcut "alt+R" setup for changing the font color to red. It used to work flawlessly in the previous versions of libreoffice. But in the recent version >7.2.* whenever I press the "alt+R" the menu-dropdown opens. The shortcuts of the form alt+* doesn't seem to work anymore hence I am forced to use libreoffice 7.1.6 or below versions as they don't have this issue.

=============Expected behaviour============
On pressing the alt+* type of shortcuts the intended effect should take place instead of menu taking over the opening the dropdowns.

Please refer to screenshots
Thanks
Comment 1 aystic 2022-02-10 11:08:40 UTC
I checked and Libreoffice version 7.2.5.2 also has this issue.
Libreoffice version 7.1.8.1 is NOT having this issue and is working as expected.
Comment 2 Michael Warner 2022-02-19 14:08:14 UTC

*** This bug has been marked as a duplicate of bug 146174 ***