Red Hat Bugzilla – Bug 444318
X crashes when starting compiz while running glxgears
Last modified: 2008-08-02 19:40:37 EDT
Description of problem:
X crashes when starting compiz, when glxgears is running.
I can run glxgears without any problem before or after compiz is started. I can
start or restart compiz just fine if glxgears is not running. But when I first
start glxgears, then start compiz while glxgears is running, X crashes and I can
never get it back: with i915.modeset=0, screen is black (has backlight) but
nothing is running, and I cannot switch to console; with i915.modeset=1, screen
is black too (no backlight), cannot switch to console either. Luckily I can
reboot with ctrl-alt-del.
Version-Release number of selected component (if applicable):
[yuan@mstar ~]$ uname -r
Steps to Reproduce:
1. run glxgears
2. while glxgears is running, run fusion-icon from menu
compiz start successfully
Before I start compiz, I have metacity running, composition enabled.
My xorg.conf is very simple:
[yuan@mstar ~]$ cat /etc/X11/xorg.conf
# Option "AllowEmptyInput" "True"
# Option "AutoAddDevices" "True"
# Option "AutoEnableDevices" "True"
# Option "Intel-BatchBuffer" "True"
Option "DRI2" "True"
Thanks for the bug report. We have reviewed the information you have provided
above, and there is some additional information we require that will be helpful
in our diagnosis of this issue.
Please attach your X server config file (/etc/X11/xorg.conf) and X server log
file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file
attachments using the bugzilla file attachment link below.
Could you please also try to run without any /etc/X11/xorg.conf whatsoever and
let X11 autodetect your display and video card? Attach to this bug
/var/log/Xorg.0.log from this attempt as well, please.
We will review this issue again once you've had a chance to attach this information.
Thanks in advance.
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
Reporter, could you please reply to the previous question? If you won't reply in
one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
Since there are insufficient details provided in this report for us to
investigate the issue further, and we have not received feedback to the
information we have requested above, we will assume the problem was not
reproducible, or has been fixed in one of the updates we have released for the
Users who have experienced this problem are encouraged to upgrade to the latest
update of their distribution, and if this issue turns out to still be
reproducible in the latest update, please reopen this bug with additional
Closing as INSUFFICIENT_DATA.