Bug 205315
Summary: | [db4] Unknown instabilities in OpenOffice help. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jake Gage <jake> |
Component: | db4 | Assignee: | Jindrich Novy <jnovy> |
Status: | CLOSED ERRATA | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5 | CC: | a_titov82, caolanm, chkr, craigpemberton, german70, igorm5, jreiser, kmaraas, lsof, michal.k.k.piotrowski, mstuff, pknirsch, stevenrubenstein, thinkingfacts |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-09-08 07:29:26 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jake Gage
2006-09-05 23:29:33 UTC
Can you do... rpm -q db4 I suspect that was has changed is that a new testing db4 is installed. caolanm->jnovy: I bet the new testing db4 causes this. Quite likely a problematic usage in OOo, but do we really have to push this new db4 for FC-5 ? Confirmed it's caused by the db4 leak fix. I'm going to revert the change. Caolan, have you tried to open databases in OOo with db_create(&db, NULL, 0) instead of db_create(&cb, NULL, DB_XA_CREATE)? are you sure that OOo uses Transaction Manager? The latest upstream db-4.4 has the XA part mostly rewritten so that it's likely it's already fixed there. yeah, we almost certainly have the wrong flags for db_create in OOo as you suggested in the leak fixing issue. And for the FC-6 OOo that I'm building at the moment I fix that so all will be well for rawhide. I can make the same fix for FC-5 to avoid this problem (and I've a build in the queue just in case we want to do this), but I'd rather avoid a FC-5 update of OOo unless I have to. Sounds reasonable, unfortunatelly db4 is now released to final so I need to release another db4 FC5 update. But without pushing the db4 to final we wouldn't discover this OOo behaviour in time before the FC6 release. Thanks Jake for reporting! *** Bug 205453 has been marked as a duplicate of this bug. *** *** Bug 205525 has been marked as a duplicate of this bug. *** *** Bug 205550 has been marked as a duplicate of this bug. *** *** Bug 205572 has been marked as a duplicate of this bug. *** FC5 update for this fix should occur in the tomorrows push. (In reply to comment #10) > FC5 update for this fix should occur in the tomorrows push. Ok. Thanks! db4-4.3.29-8.fc5 has been pushed for fc5, which should resolve this issue. If these problems are still present in this version, then please make note of it in this bug report. *** Bug 205579 has been marked as a duplicate of this bug. *** *** Bug 205580 has been marked as a duplicate of this bug. *** Not a problem, Jindrich. Glad to help. Thank you guys for the quick response. You rule. Has this bug been fixed? I have been encountering a similar error in OO Calc. Whenever I try to get help (F1) there is no text in the right hand box, and when I try doing a search or click around the links OO crashes. Felix, have you updated to db4-4.3.29-8.fc5? Initially there was nothing to update, though after I ran 'yum clean all' the package appeared on the update list. So I will see how it goes. *** Bug 205621 has been marked as a duplicate of this bug. *** Help works again. Thanks. Ok, closing ERRATA then. Please reopen if you see this OOo issue again. However based on my latest yum update of FC6T2, the current FC6 package is still: db4-4.3.29-7.fc6 Per duplicate bug 205550 above. Therefore hoping the FC6T2 update isn't far behind the FC5 fix! For FC-6, all should be well with this morning's OOo 2.0.4-3.1 Positively heroic. *** Bug 205709 has been marked as a duplicate of this bug. *** Fixed 205709 for me. Thanks, Steven Rubenstein (205709 reporter) The OOo 2.0.4-3.1 FC6 update ran smoothly all day yesterday and looks to have eliminated the crashes. Thanks for the quick fix guys. *** Bug 206583 has been marked as a duplicate of this bug. *** *** Bug 206233 has been marked as a duplicate of this bug. *** *** Bug 206177 has been marked as a duplicate of this bug. *** *** Bug 206299 has been marked as a duplicate of this bug. *** *** Bug 210811 has been marked as a duplicate of this bug. *** |