Weird one this. Like I need a colour profile or something. Since upgrading to rawhide from F7, I am not seeing certain colours (like light blue on white). Changing the brightness/contrast/colour temperature settings on the monitor does not help. It looked fine in F7. I am using a VGA cable.
Hey I've got this same problem! It's not harmful, really, just weird. Probably you should include some details about the monitor, video card, your machine arch, etc. I'm seeing it on a ppc64 (dual G5 power mac) with Radeon video: VGA compatible controller: ATI Technologies Inc RV350 AP [Radeon 9600] The monitor is a DELL 2007WFP, connected by VGA through a KVM. It's definitely something between the video card and the monitor; screenshots taken on this machine look normal if displayed on other machines.
Oh good :) It's a good thing I don't use any publishing programs much (OO, Gimp, etc) The problem for me is that I cannot see the difference in some docs between commands (with a light blue background) and the surrounding text. Very annoying. 32-bit/Pentium 4 Monitor: Iiyama PLE2200 Card: ATI Radeon 9100 IGP Would be nice if this was fixed, it's surprising how confusing things get when you are slightly colour blind.
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.
Created attachment 242241 [details] /var/log/Xorg.0.log I have no /etc/X11/xorg.conf file.
Created attachment 242351 [details] Xorg.0.log from G5
Created attachment 242361 [details] xorg.conf from G5
Created attachment 242371 [details] xorg.conf from G5 previous xorg.conf was from wrong machine. disregard.
Created attachment 242381 [details] Xorg.0.log from G5 previous Xorg.0.log was from the wrong machine, although the same monitor. Might be interesting to compare probed EDID values?
Files attached.
Created attachment 248241 [details] working logfile Strange. For comparison, here's Xorg.0.log from a _working_ G5.
Created attachment 248351 [details] Xorg.0.log from another G5 This Xorg.0.log file is also from a G5 showing the problem. This is from a fresh scratch install of rawhide/F8 today.
dwmw2: interesting. We've got the same video card and extremely similar (Dell flat-panel) monitors. The most obvious difference is that yours is connected by DVI rather than VGA. I'll try DVI and see if that changes anything.
But I'm not using Dell or Apple.. Does Dell rebadge IIyama monitors?
I have an IBM L200p and using straight dvi produces weird results. Like oddball screen sizes and having to switch to a vtty and back to X before it will display anything.
Switching the driver from radeon to fbdev in my xorg.conf seems to work fine.
can you please test the 6.7.196 driver in F8 updates-testing? and report it it fixes the washed out colours..
# yum --enablerepo=updates-testing upgrade xorg-x11-drv-ati No Packages marked for Update Will try again later.
xorg-x11-drv-ati-6.7.196-1.fc8 has been pushed to the Fedora 8 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update xorg-x11-drv-ati'
Hurrah!
(In reply to comment #19) > Hurrah! Could you elaborate on this a little bit, please? :-) Does it mean, that with the package xorg-x11-drv-ati-6.7.196-1.fc8 your problem was resolved?
WFM - thanks.
xorg-x11-drv-ati-6.7.196-1.fc8 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report.