Bug 159478 - OpenOffice 1.1.3 has problem with r128 driver
OpenOffice 1.1.3 has problem with r128 driver
Status: CLOSED CURRENTRELEASE
Product: Fedora
Classification: Fedora
Component: xorg-x11 (Show other bugs)
3
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Caolan McNamara
: Regression
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-06-02 16:12 EDT by Ankur Jain
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-06-10 06:06:11 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Ankur Jain 2005-06-02 16:12:36 EDT
Description of problem:
If I use "r128" as the video driver for the system, I cannot launch openoffice
as a non-root user. A segmentation fault occurs everytime. But the root can
launch openoffice and use it.
If we change the video driver to "vesa" then everything works fine. I can launch
and use openoffice using root/non-root account as well.

Version-Release number of selected component (if applicable):
OpenOffice 1.1.3

How reproducible:
Everytime

Steps to Reproduce:
1. Login as normal (non root) user. (assuming currently using "r128" as video
driver)
2. Issue the command ooffice from the terminal.
3. Segmentation fault occurs.
4. Change the video driver in xorg.conf to "vesa" from "r128"
5. Logout and Restart X
6. Login as normal, root account
7. Issue the command ooffice again.
8. Openoffice is started perfectly.

Actual results:


Expected results:


Additional info:
Comment 1 Caolan McNamara 2005-06-03 03:22:35 EDT
Can you get a backtrace from OOo (e.g.)
gdb /usr/lib/ooo-1.1/program/soffice.bin
(gdb) run -writer
(gdb) bt
and paste in the results here.

This is awesomely likely to not be an OOo problem, 
try running glxgears, and the testprogram at
http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=139712 and report what happens 

Note You need to log in before you can comment on or make changes to this bug.