https://bugs.documentfoundation.org/show_bug.cgi?id=164388
--- Comment #20 from Patrick (volunteer) <[email protected]> --- (In reply to Patrick (volunteer) from comment #19) > Realistically, I suspect that this is a machine-specific problem since no > one other than @Dennis can reproduce this. All I can think of is that maybe > the Command-< key events are getting intercepted by some other application > or utility (e.g. clipboard managers, accessiblity tools such as Rectangle). One other thing to try: restart LibreOffice in safe mode by selecting the Help > Restart in Safe Mode. Then, in the dialog that appears, check the "Reset to factory settings" checkbox as well as the 2 checkbox below that checkbox and press the "Apply Changes and Restart" button. Why this may help: I did a little test and set the "move to next window" shortcut to Command-a. Then, if I restart LibreOffice, Safari, etc. and open two windows, Command-a does not work in any application that has an Edit > Select All with Command-a as its shortcut. In both Safari and LibreOffice, pressing Command-a causes the Edit menu to flash in the menubar and, if any text is selected, the text is selected. What is going on: when you press a Command shortcut, macOS looks for a match in the active application's menus. Only if a match is *not* found, does macOS look a the system preferences settings for a shortcut match. Resetting LibreOffice's settings clears any custom shortcuts that you may have modified that might be intercepting the Command-< shortcut. Since I could not reproduce the bug even with the German language pack running German UI, I assume that, at least in Writer, the LibreOffice 24.8.4 German language pack does *not* set any menu shortcuts to Command-< but I didn't test Calc or Impress. -- You are receiving this mail because: You are the assignee for the bug.
