abrt 1.0.0 detected a crash. Attached file: backtrace cmdline: /usr/lib64/openoffice.org3/program/scalc.bin -calc file:///home/TanyaEgorova/%D0%A0%D0%B0%D0%B1%D0%BE%D1%87%D0%B8%D0%B9%20%D1%81%D1%82%D0%BE%D0%BB/%D0%9E%D1%82%D1%87%D0%B5%D1%82..xlsx component: openoffice.org executable: /usr/lib64/openoffice.org3/program/scalc.bin kernel: 2.6.31.6-166.fc12.x86_64 package: openoffice.org-calc-1:3.1.1-19.14.fc12 rating: 4 reason: Process was terminated by signal 6
Created attachment 379579 [details] File: backtrace
This is actually a crash (well unexpected exception getting thrown) from voikko::PropertyManager::readFromRegistry) which is the Finnish spellchecking extension. Might not be voikko's fault, but it is suspicious.
*** Bug 549288 has been marked as a duplicate of this bug. ***
*** Bug 549287 has been marked as a duplicate of this bug. ***
I've reported the bug upstream, https://sourceforge.net/tracker/?func=detail&aid=2919454&group_id=156731&atid=800960 As the holiday season is coming up, it's possible this might take a while to get fixed. Anyone who doesn't need Finnish spell checking in OpenOffice can work around this bug by removing the openoffice.org-voikko package.
Bug reporter: can you describe how to reproduce this bug? It might be useful in finding out which exception is thrown and why.
Harri Pitkänen has provided a partial fix to this problem in openoffice.org-voikko SVN, see the upstream bug report. It seems like the root cause of this problem is corrupted configuration files. I'll quote from Harri's post: "This bug appears to be caused by broken configuration. I was able to reproduce it by commenting out some parts of config.xcs and config.xcu before installing the extension. The error handling was slighly broken which lead to the crash." ... "For Fedora I would worry more about the reason for the broken configuration in these bug reports. Is it possible that config.xcs/config.xcu are not always installed or the configuration is broken afterwards? Maybe SELinux or something is preventing the registry from being updated correctly. I have not yet heard about similar problems from other distributions." Caolan: Any ideas? I could actually build new packages from the latest SVN revision for Rawhide and F12 as the changes from 3.1 have been quite small, but I'm not quite convinced yet if I should ship SVN checkouts on F12...
"Is it possible that config.xcs/config.xcu are not always installed or the configuration is broken afterwards?" Its quite possible that there are a massive pile of extensions installed and something went wrong there, but there's no evidence of anything like that. The only info we have is what is shown above. "Maybe SELinux or something is preventing the registry from being updated correctly.", Nah that would seem very unlikely "I have not yet heard about similar problems from other distributions." There's only been the one report in Fedora, so not a lot of data points there.
openoffice.org-voikko-3.1-2.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/openoffice.org-voikko-3.1-2.fc12
I've set Bodhi to close this bug once the above package is in stable. If we don't get a confirmation from the original reporter or more reports like this, getting a real fix in place will be difficult.
openoffice.org-voikko-3.1-2.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update openoffice.org-voikko'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2010-1080
openoffice.org-voikko-3.1-2.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.
openoffice.org-voikko-3.1.1-1.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/openoffice.org-voikko-3.1.1-1.fc11
openoffice.org-voikko-3.1.1-1.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.