Apache OpenOffice (AOO) Bugzilla – Issue 111055
xmloff: Error: AutoStyle could not be found
Last modified: 2010-04-25 14:53:52 UTC
In a new text document, I entered some text, including two URLs which OO took upon itself to recognize as links. Back in Firefox 3.0 I fat-fingered an entry field, and restarted Firefox, and was once again navigating the TOC of DB2/UDB V9R7 Infocenter <http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp>. It is entirely possible that I had reached the page referenced in the first link in the open document. Debug Output ... Error: AutoStyle could not be found From File /home/terry/OOo_hacking/DEV300_m76/xmloff/source/text/txtparae.cxx at Line 806 Abort ? (Yes=abort / No=ignore / Cancel=core dump) After I took No, the message repeated itself, and this time I notice that the bottom of the OO window shows "Saving document..." and a progress bar about 80% complete. I presume this progress bar refers to an auto-save; after all, it does take my poor little machine half an hour for gdb to attach to soffice.bin and collect a backtrace. The menu I was navigating in Firefox starts at <http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp>. As it happens, the document I was creating describes the path through that menu that I was following when OO raised the assertion. I shall shortly attach the document and a backtrace taken while the Debug Output window is open. (The assertion came up twice more as I was saving the document; the second time, it somehow blocked me from switching focus back to the text editor where I am typing this message.) I am running a lightly hacked non-product build of DEV300_m76. My hacks are in connectivity/source/drivers/odbcbase/OResultSet.cxx.
Created attachment 69039 [details] document open when program raised the assertion
Created attachment 69040 [details] backtrace
This looks like a dup of bug 108345. In that case the attached document is worthless, because the problematic formatting is not there anymore. *** This issue has been marked as a duplicate of 108345 ***
closing duplicate
I have applied the third proposed patch for issue 108345, and I have not seen the assertion since. Bye the way, in the meantime I observed that the assertion came up at random times--so far as I can see--regardless of what I was doing on the system. While I was watching the clock, I observed intervals ranging from 1 to 5 minutes between addition of a URL to the document and the appearance of the assertion message.