I like to open two similar documents in a word processor and pop back and forth between them, to compare and copy bits from one document to the other. Many macos programs provide command-` to swap from one window to another (chrome, Safari and Brave browsers for example.) Libre Office also does this, but after going back and forth two or three times, it hangs, with the "busy" coloured disc going round and round. I can command-tab to other running programs, but can't command-tab back to Libre Office. I have to go to Activity Monitor, and there I see "not responding" beside Libre Office. It doesn't respond to Quit, but Forced Quit does. My macos version is Sonoma 14.2.1 with 64G of memory. Hoping you can help, Jim
Smells like an additional manifestation of bug 148435 on a revisit from idle thread. LibreOffice 'QUOTELEFT_MOD1' issues with the Cmd+Grave accent/Shift+Cmd+Grave accent (⌘+`/⇧+⌘+`) issued by os/DE for movement between windows of the "frontmost" application. Otherwise, there is currently no UNO defined for the internal module window changes that could be assigned to the shortcut. Changes are available in UI from the main menu Window list, just no implementation as UNO. Maybe that would be the way to avoid any hang.
(In reply to Jim Henderson from comment #0) > I like to open two similar documents in a word processor and pop back and > forth between them, to compare and copy bits from one document to the other. > Many macos programs provide command-` to swap from one window to another > (chrome, Safari and Brave browsers for example.) > Libre Office also does this, but after going back and forth two or three > times, it hangs, with the "busy" coloured disc going round and round. > I can command-tab to other running programs, but can't command-tab back to > Libre Office. > I have to go to Activity Monitor, and there I see "not responding" beside > Libre Office. It doesn't respond to Quit, but Forced Quit does. > My macos version is Sonoma 14.2.1 with 64G of memory. > > Hoping you can help, > Jim Oops! Sorry everyone, that I wasted your time. My version of LO was very old (7.3.4.2) as I reported. I have updated to the current one (24.2.0) and I can't make the problem happen any more. I should have thought to update first. We can close this issue now, so I have marked it RESOLVED, FIXED.