Bug 494359
Summary: | OpenOffice Impress, xrandr, presenter plugin == crash of OOo | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jan Wildeboer <jwildebo> |
Component: | openoffice.org | Assignee: | Caolan McNamara <caolanm> |
Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 10 | CC: | caolanm, mkranz |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-04-17 22:17:59 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
Jan Wildeboer
2009-04-06 14:37:45 UTC
What's the video driver ? (hackarounds might include a. export SAL_IGNOREXERRORS=1 b. export SAL_DISABLE_CAIROTEXT=1 c. tools->options-view and toggling off "hardware acceleration" (i.e. cairo drawing) Your first suggestion already works! As this is on a small netbook (Acer Aspire One A110L) I will not dive into removing hardware acceleration support. I will test more and should this be sufficient, I am a happy Fedora User again :-) Jan The first one just makes OOo ignore any X errors and carry on, so its possibly something of the nature of a mismatching depth on drawing or sommat like that. Knowing the hardware driver might help, i.e. run /usr/lib/openoffice.org3/program/crash_report -stack /dev/null to collect possibly useful info FWIW checked on 32bit openoffice.org-core-3.0.1-15.3.fc10.i386 with i915 intel driver and got working dual head with XRandr without XErrors on showing a simple presentation. I'm going to close this one for now, unless there is some more information that would help reproduce it. Its probably some depth mismatch issue I'd guess, hopefully sorted out in 3.1 for F-11 |