[fglrx] X crashes when I click on desktop near right side [AMD Feature#7647] [EPR#260224]

Hi kkhww1902,

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with the latest development release of Ubuntu? (ISOs are available from cdimage.ubuntu.com)

If it remains an issue, could you also attach a new /var/log/Xorg.0.log?
Thanks in advance.

The output of lspci -vvnn would also be worth having.

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

  http://bugs.launchpad.net/ubuntu/+source/fglrx-installer

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: http://cdimage.ubuntu.com)
 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.]

Still happens in Intrepid. :-( Attaching Xorg.0.log .

Attaching the output of `lspci -vvnn`.

BTW, the problem is completely reproducible.

[Reported to AMD]

Oh, forgot to mention I have a dual head setup, and I am using the "Extra" visual effects.

I've the same problem. I'm using a dual-head setup.
I'm going to attach my 'lspci -vvnn' and Xorg.log.0.

Why would a bug that causes a repeatable crash ever be marked as "Wishlist" ?

Considering the VT switch/suspend business in the log, this might be related to https://bugs.launchpad.net/fglrx/+bug/197209

Why X is trying to suspend, of course, I have no idea.

I have this bug too, with an interesting spin: Sometimes, when the crash happened, it happens again every time I login, and shortly after the Ubuntu theme starts getting played, and causes a hard freeze (Hard system restart required).

To work around this, I have found it useful to rename or delete:

~/.gconfd/saved_state (stops the hard freeze; without this one, x gets restarted instead)
~/.compiz/session (this stops the crashing)

I also tried deleting these files while narrowing down the cause. I cannot reinstate the crashing at this time, so I can only say these *might* also be involved, simply because I tried deleting them at some point. However, I can say with a certain amount of confidence that no other files need be deleted to work around.

~/.dbus
~/.ICEauthority
~/.Xauthority
~/.config/tracker

Thanks for making Ubuntu! What a joy to work with.

Carlo

This bug was fixed in the package fglrx-installer - 2:8.600-0ubuntu1

---------------
fglrx-installer (2:8.600-0ubuntu1) jaunty; urgency=low

  * New upstream release. (Closes LP: #313027, #314600)
    - Fixes LP: #253988, #179042, #241176, #284408, #287229, #296497,
      #288620, #289628
  * README.Debian: Update the update procedure a bit

 -- Bryce Harrington <email address hidden> Tue, 17 Mar 2009 15:40:42 -0700

With Jaunty I don't use fglrx anymore, and the opensource driver doesn't have this problem. Does anyone with a new card that uses fglrx still see this issue in Jaunty?

Thank you for reporting this issue about a driver from the
linux-restricted-modules package. lrm-2.4.24 was shipped with Ubuntu
8.04 which reached end-of-life for desktop support on May 12th, 2011.

For that reason, this bug report is being closed at this time. I'm
marking it wontfix because what you describe is probably a valid issue,
but there are no plans to work on lrm 2.4.24 bugs further.

The issue may be resolved in a newer version. If not, aside from filing
a new bug report, another angle may be to file it directly with the
driver vendor.