Bug 209441 - starting desktop-effects crashes system at high resolutions
starting desktop-effects crashes system at high resolutions
Product: Fedora
Classification: Fedora
Component: compiz (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Kristian Høgsberg
Depends On:
  Show dependency treegraph
Reported: 2006-10-05 09:00 EDT by Brian G. Anderson
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:
Last Closed: 2006-10-05 12:00:45 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Brian G. Anderson 2006-10-05 09:00:22 EDT
Description of problem:
I have a ATI card (FireGL Mobility T3  [M10 NT]), which I usually run at
1600x1200.  I started desktop-effects, all the window borders disappeared and
then the system locked hard.  I had to reboot the machine.

Version-Release number of selected component (if applicable):
xorg-x11-drv-ati.i386                    6.6.2-4.fc6 
compiz.i386                              0.0.13-0.31.20060817gi

How reproducible:

Steps to Reproduce:
1. Start X at 1600x1200 resolution and desktop-effects not enabled
2. start desktop-effects and enable
Actual results:
all the window borders disappear and the the system locks requiring a reboot.

Expected results:
Enabled desktop effects

Additional info:
If I reduce the resolution to 1024x768 then I can enable the desktop effects. 
When I restart X, it comes up at 1600x1024 with compize working fine.
Comment 1 Kristian Høgsberg 2006-10-05 10:59:40 EDT
Are you running at least xorg-x11-server-Xorg-1.1.1-43.fc6?  If not, please
updgrade to that version and see if it fixes the lockup, thanks.
Comment 2 Brian G. Anderson 2006-10-05 11:42:02 EDT
I was running xorg-x11-server-Xorg-1.1.1-43.fc6 when the error occurred, but
xorg-x11-server-Xorg-1.1.1-44.fc6 has come through and that seems to have fixed
the problem.
Comment 3 Kristian Høgsberg 2006-10-05 12:00:45 EDT
Great, thanks for confirming this.

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