https://bugs.documentfoundation.org/show_bug.cgi?id=157130
--- Comment #21 from Patrick (volunteer) <[email protected]> --- (In reply to Dennis Roczek from comment #20) > Just to be sure everybody is talking about the same glitch: using the > keyboard shortcut for taking a screenshot of the full screen, I do see the > attached cursor in the middle of the paper. Shortly after, the text appears. > On all mentioned systems with and without resetting the profile folder. (and > independent of the gerrit patch through this is only tested on the mbp2014) So from your Help > About output in comment #19, you were able to reproduce this bug on the same hardware as me (i.e. a 14" M1 MacBook Pro): Version: 24.8.2.1 (AARCH64) / LibreOffice Community Build ID: 0f794b6e29741098670a3b95d60478a65d05ef13 CPU threads: 8; OS: macOS 15.1; UI render: Skia/Metal; VCL: osx Locale: en-CA (en_CA.UTF-8); UI: en-US Calc: threaded The problem is that I still cannot reproduce this bug on my machine. I even rebooted into macOS Sonoma on my machine but still could not reproduce this bug. I wonder what is different between our Silicon Mac machines? I am not familiar with the Writer code but IIRC Writer usually does not draw immediately after a key event but instead waits to do all drawing to the window in a painting timer. In your screen snapshot, the cursor and status bar have been redrawn so my first guess is that one or more of Writer's painting timers are never getting a chance to run and they are continually deferred because LibreOffice is not finished processing a key event before another one is in the queue. Only when you stop adding new key events to the queue and LibreOffice has no new input to process does the painting timer finally get a chance to run and draw the undone text. We have more or less the same CPU so I wonder if LibreOffice is competing with some other application or background process for CPU and that might be slowing down processing of the Command-Z events enough to delay Writer's painting timers. Another possible thing to look at is if you have any applications using the macOS accessibility subsystem to listen for changes in LibreOffice. Not sure if the above helps. If any Writer developers are reading this bug, I would be interested to hear if they have any ideas. -- You are receiving this mail because: You are the assignee for the bug.
