Open Office does not start when using fglrx ATI driver.

Bug #155372 reported by Nikola M on 2007-10-21
Affects Status Importance Assigned to Milestone
linux-restricted-modules-2.6.22 (Ubuntu)
Unassigned (Debian)
Medium (Fedora)
Unknown (Ubuntu)

Bug Description

Open office cannot be started after install of fglrx ATI driver
with Restricted devices manager.
Ubuntu installed:
Xubuntu Gutsy final 7.10 amd64, installed from alternate CD.

Hardware involved:
CPU: Amd AthlonX2 dual core
Motherboard: Amd 690G chipset (integrated Ati X1250 graphics)

If using fglrx driver, OOo splash screen appeares and then nothing starts.
If using vesa driver OOo starts and works.

Steps to reproduce:
Install Xubunu 7.10 amd64
Openoffice is working (vesa drivers by default, flickering)
Install fglrx ATI proprietary driver with "Restricted devices manager"
Openoffice apps does not start.

Wanted behavior:
Open office should work no matter what graphics driver is in use,
or fglrx ATI driver should not disable Open office.

Chris Cheney (ccheney) wrote :

On your system what does the line in file




Chris Cheney

Changed in
assignee: nobody → ccheney
status: New → Incomplete
Changed in
status: Unknown → Confirmed
Changed in
status: Unknown → New
Nikola M (nikolam) wrote :

But even when I put yes, nothing happens. ;(

I tried yesterday to install xgl and compiz on 7.10 install.
After that, Open office starts and works (but it still does not open blank document on startup).
When I removed xgl and compiz, OpenOffice does not work again.

So it is definitely something between OpenOffice and fglrx ATI driver..

Nikola M (nikolam) on 2007-10-25
Changed in
status: Incomplete → Confirmed
Changed in
status: New → Confirmed
Changed in
status: Confirmed → Unknown
Nikola M (nikolam) wrote :

I just installed fglrx driver from ATI site (8.40.4)
And OpenOffice works. (Also, totem starts to work)
So it seems that something is wrong with default 64-bit fglrx (8.37.6) driver in 7.10

Changed in
status: Unknown → Confirmed
Chris Cheney (ccheney) on 2007-11-15
Changed in
status: Confirmed → Invalid
Changed in
assignee: ccheney → nobody
status: Confirmed → New
Timo Aaltonen (tjaalton) on 2008-01-15
Changed in linux-restricted-modules-2.6.22:
status: New → Confirmed
Changed in
status: New → Invalid
Bryce Harrington (bryce) wrote :

[This is an automated message]

As of Intrepid (8.10), we have a dedicated package 'fglrx-installer' for fglrx bugs, which now includes a process for upstreaming bugs to AMD.

To transition your bug into the new fglrx-package, we need your help. Please do the following:

 a. Verify the bug occurs in Intrepid.
     (Intrepid ISOs:
 b. If you haven't already, please include in the bug:
     * Your /var/log/Xorg.0.log
     * The output of `lspci -vvnn`
     * Steps to reproduce the issue
 c. Click 'Also affects distribution'
 d. Set 'Source Package Name' to 'fglrx-installer'
 e. Click Continue

Thank you. This will assist us in reviewing and upstreaming your fglrx bug, as appropriate.

[We'll expire the fglrx bugs in l-r-m-* in a month or so.]

Jonathan Thomas (echidnaman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in linux-restricted-modules-2.6.22 (Ubuntu):
status: Confirmed → Invalid
Changed in (Debian):
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.