This bug was filed from the crash reporting server and is br-e96f84ea-fed2-442f-98a7-54179efe4ea4.
Thank you for reporting the bug.
Unfortunately without clear steps to reproduce it, we cannot track down the origin of the problem.
Please provide a clearer set of step-by-step instructions on how to reproduce the problem.
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the steps are provided
Created attachment 148063 [details]
LO Writer froze when I attempted to add a modification date field in the footer. The program hangs as soon as I select Insert > Field > More Fields and has to be stopped using the Windows Task Manager. As far as I could tell, Writer seems to be in a fairly tight loop as it was not page faulting nor was it doing any IO (there were some page faults when the hang first happened but nothing after a second or two).
The failure is absolutely hard and occurs each time I attempt to add the field.
I notice that a similar failure occurs if I try to add a cross-reference - I've only tried once. I have several other files that trigger similar failures when trying to add a cross-reference. They are much bigger and already contain several cross-references. With these files, I can add cross-refs using LO Writer on Linux Mint. I haven't (yet) tried that with this file, nor do I recall off-hand any details of my Mint installation or of the LO version I have there.
Do you have any registered databases? (apart from the default Bibliography) If you do, does the crash persist if you remove them?
What is a registered database? I don't knowingly have any.
(Sorry to have left response for so long.)
To confirm that I was able to add the modification filed using my Mint version and that my Windows version happily displayed the contents of the field once the file was transferred there.
I'm sat at my Windows machine now and still haven't noted details of the Mint machine. Let me know if you need them.
(In reply to Alan Grunwald from comment #4)
> What is a registered database? I don't knowingly have any.
> (Sorry to have left response for so long.)
Ah, my bad, I forgot to reply to your e-mail here. Open Tools -> Options..., LibreOffice Base -> Datbases. There's a default one, Bibliography, I'm interested if whether anything else is there.
No specific ideas so far, but there've been a few crashes with combination of fields + mail-merge data sources (which would also appear in that list).
I did have a couple of databases listed there. I deleted them both and now I can insert references to my heart's content without any problems.
I just registered the (soon to be) attached database file with Tools > Options ... LibreOffice Base>Databases ... New and the failure returned. I delete/unregistered it again and all is well.
That's me well satisfied, thank you. I hope you're able to track down and fix the underlying cause.
Created attachment 148247 [details]
Database referred to in previous comment
(Sorry; was I able to attach the file to the comment? I wasn't really watching. D'oh!)
I had this db on the desktop. When I registered it the failure returned; when I deregistered it the failure went away again.
I don't recall where the db came from; I have a similarly named .mdb file that I do recall downloading, but don't know how I converted it to .db.
(I'm pretty sure the original _was_ an Access database; this version certainly seems to be an sqlite db. I really do wish I could remember how I converted it. Really, really, really :-)
Could be the same reason - all registered databases will be opened when inserting cross-references: bug 119610.
Alan, there is no crash report with this signature in LO 18.104.22.168 and 22.214.171.124. So can you try it with one of this versions?
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the master build or to RESOLVED WORKSFORME, if the problem went away.
Dieter - I have been OK ever since Jan-11 (my comment 8 above).
Do I need to do something to keep bugzilla happy?
(In reply to Alan Grunwald from comment #11)
> Do I need to do something to keep bugzilla happy?
Yes, change status to RESOLVED WORKSFORME (I did it).
I now know, if there is a next time. Thank you.