Red Hat Bugzilla – Bug 437241
yum update broke desktop effects
Last modified: 2008-03-18 14:53:09 EDT
Description of problem:
I just did a yum update on my Fedora 8 box and lost my desktop effects. When I
try to re-enable them, I get an error box that says "Desktop effects could not
be enabled." Prior to the yum update, they worked fine.
Version-Release number of selected component (if applicable):
Thinkpad T60 with integrated Intel graphics set; stock Intel drivers
Steps to Reproduce:
1. enable desktop effects
no desktop effects
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.
Same update batch broke desktop effects for me too, but it turned out to be
kernel-18.104.22.168-12.fc8 not xorg-x11-server-Xorg-22.214.171.124-42.fc8 package.
Downgrading xorg-x11-server-Xorg to 126.96.36.199-40.fc8.x86_64 didn't make any
difference, but booting back with kernel-188.8.131.52-137.fc8 made desktop effects
work again with both the old and newer xorg-x11-server-Xorg.
Fedora 8 x86_64 with all updates on a Dell XPS M1210 with Intel integrated card
and stock drivers.
reassigning this to kernel since that seems to be the culprit. I tried deleting
my xorg.conf, and that didn't help.
I guess this is a duplicate of #436871, though I haven't been able to try the
new kernel (184.108.40.206-34.fc8) yet.
Sorry I meant #433728
This seems to be a duplicate of #437234.
Fixed by kernel 220.127.116.11-34.
*** This bug has been marked as a duplicate of 433728 ***