https://bz.apache.org/ooo/show_bug.cgi?id=125672
myroslava <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #7 from myroslava <[email protected]> --- I have had a similar problem. Not a dev; advanced user. The version of OOo that was installed was 4.1.1. I first got this error while, with another app (Firefox) in foreground and in focus, I clicked on an odt file that was below it, and clicked on a second page of a document that just barely overflowed onto a second page while the first page had a table that reached to the end of the first page. I relaunched OOo, waited for the recovery of the document, tried to click once again under the table on the second page—same s**t. After that there was a flurry of activity that I don't think I can reproduce, which is why I'm posting my console log starting from the time that I think the problem started, and it's a long log that ends only after the error stopped manifesting. What I was doing: I tried clicking within the table, it didn't produce an error. Clicking below the table—error repeats. I started downloading 4.1.3 and googling for solutions. I installed 4.1.3 (had to disable MacOS defense against unconfirmed developers). I think it was after that that I also tried resetting my user profile. I relaunched OOo, opened the same file, got the same error, and restored my old user profile. Opened the same file again, got the same error (again while clicking below the table). Created a new Writer file, clicked somewhere on the lower margin—same error. Then I downloaded 4.1.0, installed it. Opened my table file, clicked under table—same error. Opened an ODG file I have, created a new page in it, clicked around it—no error; I closed the file without saving. I'm not sure at which point I opened the ODG file. Also at some point I increased the cache allowance in OOo settings. At some point then, the error stopped manifesting, and I can't reproduce it now. Hope someone can make heads or tails of my console log. I'm also attaching the file with the table with which the error first started. Unfortunately, the file is _not_ in the same state in which it was when I got the error, because in-between it all I saved it, and then after the error stopped I edited it and then saved again. I'm attaching it just in case, too; please not it did _not_ have an image inside it when the error started. It was just a plain table, nothing heavy. -- You are receiving this mail because: You are the assignee for the issue.
