Red Hat Bugzilla – Bug 591007
[abrt] crash detected in SwNumRule::SetInvalidRule
Last modified: 2010-05-18 07:39:57 EDT
abrt detected a crash.
Attached file: backtrace
cmdline: /usr/lib/openoffice.org3/program/swriter.bin -writer file:///data/marvell/plugd/guruplugD+cam/EI_Marvell_PlugD-IPCamera_SoW_v0.9.doc
reason: Process was terminated by signal 11
Created attachment 413060 [details]
Are you able to reproduce this ? It looks like exporting a given document to .odt, do you have the original document ?
(In reply to comment #2)
> Are you able to reproduce this ? It looks like exporting a given document to
> .odt, do you have the original document ?
No, I can't reproduce it now. But on that particular day, it happened a couple of times. Unfortunately my ABRT was not working (because a few packages were missing) that day. I just set it up today and thought to report this crash.
Actually I was comparing two '.doc' files. It happened when my machine was idle. When it happened for the first time I was away from the machine and it was locked automatically. When I unlocked it, I found OpenOffice had disappeared. The next time it happened when I was discussing with my colleague and machine was left idle. However, it wasn't locked by the time.
I wasn't sure about why this happened or if it has anything to do with OpenOffice/Linux/'.doc' file itself. But I thought the crash info might tell you guys something about. OpenOffice has never crashed after that.
Hope this helps.
OK, then it was automatic save of the combined document that trigerred the crash. Do you happen to have these two documents yet? If yes, you can try an experiment: do the comparison just like before and save the resulting document as a new document with ODT format. In the case writer crashed, could you attach the two documents here?
Can't reproduce, could workaround though. Submitted possible patch upstream for consideration.