With ATI/AMD proprietary fglrx driver enabled, using the command "gnome-display-properties" the system stops responding

[Fabio Colombo]

I have this flashes on the screen when ATI/AMD proprietary fglrx driver is enabled. Clicking on the "display" from the menu or give the command from terminal give me flashes on the screen and the application crashes and I have to kill it.

From the terminal I got this output:

blackdiamond@blackdiamond-desktop:~$ gnome-display-properties

(gnome-display-properties:4005): Gtk-WARNING **: Ignoring the separator setting

(gnome-display-properties:4005): libglade-WARNING **: could not find a parent that handles internal children for `vbox'

Bye and thanks,

Fabio

[Fabio Colombo (stratosphere1982)]

Obviously disabling the driver it works all fine.

[Sebastien Bacher (seb128)]

gnome-desktop is the about GNOME dialog and a lib

[Sebastien Bacher (seb128)]

the issue is rather a closed source binary driver one

[João Pinto (joaopinto)]

(most of the times) I can reproduce this problem. I am using fglrx with an ATI Radeon HD 4670, the application does not crash, it does hang, looking at the top, the Xorg is using >90% when this happens, killing the gnome-display-properties application will free the CPU.

[Andriy (apa3a)]

I see a similar situation, the only difference is that for me only the preferences dialog hangs. Wonder if this is because I have a two-core processor. When the problem happens one of the CPUs goes to 100%, but the other one is still available. I think I can reproduce the problem any time.

I have somewhat different line numbers in the messages:

$ gnome-display-properties

(gnome-display-properties:5143): Gtk-WARNING **: Ignoring the separator setting

(gnome-display-properties:5143): libglade-WARNING **: could not find a parent that handles internal children for `vbox'

[Jonathan Reed (jdreed)]

I have an identical experience to what Andriy described. If fglrx is loaded, attempting to run gnome-display-properties (via System->Preferences->Display or the command line) causes Xorg to use 100% of one core (on a Core 2 DUO E8400). I'm able to reproduce the problem with fglrx on a ATI Radeon 2400 HD and an Radeon 3450 HD, on two different machines. The problem occurs regardless of whether one is running Compiz or Metacity, and the only solution seems to be to reboot the machine. Kernel logs contain nothing useful from the fglrx module.

I realize the implications of using a binary driver, but if there's a good place to document this particular failure, it should probably be documented.

[Jonathan Reed (jdreed)]

Oops, I should have included relevant version information

MIKE-WAZOWSKI:~> lsb_release -rd
Description: Ubuntu 9.04
Release: 9.04

MIKE-WAZOWSKI:~> apt-cache policy gnome-control-center
gnome-control-center:
  Installed: 1:2.26.0-0ubuntu3
  Candidate: 1:2.26.0-0ubuntu3
  Version table:
 *** 1:2.26.0-0ubuntu3 0
        500 http://ubuntu.media.mit.edu jaunty/main Packages
        100 /var/lib/dpkg/status

MIKE-WAZOWSKI:~> apt-cache policy xorg-driver-fglrx
xorg-driver-fglrx:
  Installed: 2:8.600-0ubuntu2
  Candidate: 2:8.600-0ubuntu2
  Version table:
 *** 2:8.600-0ubuntu2 0
        500 http://ubuntu.media.mit.edu jaunty/restricted Packages
        100 /var/lib/dpkg/status

[Eric Binette (lord-dagobert)]

Same problem here
I have a ATI HD3850
Intel E8400
Ubuntu 9.04

I have fix the problem by installing drivers version 9.9 from ATI website.

[João Pinto (joaopinto)]

This is also fixed on Karmic, probably it makes sense to close the bug report ?

[Pedro Villavicencio (pedro)]

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!.