Created attachment 125385 [details] Screen-shot of where the cursor got "stuck" Editing my 80k wd MS, ran a spell-check, made a small text alteration, and was interrupted briefly by a pop-up reminder from Workrave to take a break. The cursor ended up in the header area, and I could not shift it from there. Clicking anywhere in the main body of the document had no effect at all - the click was just ignored. I could click into the header area where the cursor had ended up: in that case, the normal UI elements appeared (see screen-shot). Hang on... while filling out this bug report, LO has finally allowed me to click back into the main body. I wonder if it's because in the meantime, another Workrave pop-up reminder has just appeared? I had planned to close the doc and re-open it, as I do when it becomes impossible to make any selection of text (only able to *move* the insertion point/cursor), which I've been experiencing now for the last dozen or so LO versions released. In those cases, once (maybe twice) I've managed to get LO working again normally by changing the "Standard selection" option via the menu available via the rectangle-beside-Ibar icon at the bottom of the window. Usually, though, no choice on that menu helps, and I have to close and reopen the doc.
Created attachment 125386 [details] Screen shot to show ruler, to indicate area affected Huh. Weird. It happens only on the Acknowledgements page (the CreateSpace "Convert 6" page style), but the cursor jumps to and gets stuck in the top left of the Header area if I click anywhere on the leftmost-side of the main body of that page (around the "64" mark on the ruler). Clicking anywhere in that area, the cursor stays stuck in the header. Clicking anywhere to the right of that allows the cursor to be positioned and function as expected. See attached screen-shot, FWIW.
What do we need to reproduce? Does it only happen with Workrave? Do we need your document?
Please let me look into this in the next day or so - I have an urgent deadline. I tried cutting the document down, and the problem stopped being reproducible. I'll see what I can do.
I just now revisited this. I have reopened the file, and couldn't reproduce the problem. I imagine it should simply be closed as not reproducible.