Created attachment 386190 [details] Screenshot immediately after logon Description of problem: The background (set to partially transparent) of both the upper and lower panel are corrupted. Sometimes one, sometimes the other, sometimes both, sometimes (rarely) neither. Version-Release number of selected component (if applicable): 2.28.0 How reproducible: Somewhat. Corruption is very frequent, but it is different each login. Steps to Reproduce: 1. Log on 2. Observe top and bottom panels 3. Actual results: Noisy or blocky image on panel Expected results: Smooth background color Additional info: Screenshot attached. When different workspaces are selected, the same corruption appears on each workspace. When applications are active, the button for the application with the focus is correct in the lower panel, but inactive applications retain the corrupted background. This is fairly recent so probably associated with a recent update.
I've have the same issue. This issue happens on my system if I update from xorg-x11-server-xorg-1.7.1.7.fc12.i686 to any of the latest recent updates. When I use the later updates (e.g: 1.7.4.3.fc12.i686 - currently in testing repo), if I have a background selected for the panel or I use any transparency with a solid color, then the graphics corruption appears on the panel. Icons and buttons on the panel show with no corruption. (Using the Nouveau driver for display)
Thank you for taking the time to submit this 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 the following files as individual uncompressed file attachments using the bugzilla file attachment link above: X server config file ( /etc/X11/xorg.conf ), if you have one Boot-time messages ( /var/log/dmesg ) X server log file ( /var/log/Xorg.*.log ) We will review this issue again once you've had a chance to attach this information. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Created attachment 386629 [details] requested data
Created attachment 386630 [details] Requested data Xorg.0.log
Created attachment 386631 [details] Requested data Xorg.1.log
Created attachment 386632 [details] Requested data Xorg.2.log
Created attachment 386633 [details] Requested data Xorg.3.log
Created attachment 386634 [details] Requested data Xorg.4.log
Created attachment 386635 [details] Requested data Xorg.5.log There is no xorg.conf
Created attachment 386737 [details] Requested info - dmesg Using xorg-x11-server-xorg-1.7.4-1.fc12.i686
Created attachment 386738 [details] Requested info - Xorg.0.log Using xorg-x11-server-xorg-1.7.4-1.fc12.i686
Created attachment 386739 [details] Requesed Info: Xorg.1.log Using xorg-x11-server-xorg-1.7.4-1.fc12.i686
Created attachment 386740 [details] Requested info - Xorg.2.log Using xorg-x11-server-xorg-1.7.4-1.fc12.i686
Created attachment 386741 [details] Requested info - Xorg.3.log Using xorg-x11-server-xorg-1.7.4-1.fc12.i686
Created attachment 386742 [details] Requested info - Xorg.4.log Using xorg-x11-server-xorg-1.7.4-1.fc12.i686
Created attachment 386743 [details] Requested info - Xorg.5.log Using xorg-x11-server-xorg-1.7.4-1.fc12.i686
Created attachment 386744 [details] Requested info - Xorg.9.log Using xorg-x11-server-xorg-1.7.4-1.fc12.i686 No /etc/X11/xorg.conf here either. Graphics card is a nVidia GT6600 AGP using the Nouveau graphics driver. Pentium 4, 3.4GHz (old Prescott). 2GB RAM. Generic CRT display.
Keep in mind that xorg-x11-server-xorg-1.7.1-7.fc12.i686 works fine for me with no corruption of the panel. It's only the version(s) after that which cause the issue for me.
Happening here too, on my desktop at work and at home. Both have Nvidia cards, both running Nouveau graphics driver, and neither have xorg.conf files.
(In reply to comment #18) > Keep in mind that xorg-x11-server-xorg-1.7.1-7.fc12.i686 works fine for me with > no corruption of the panel. It's only the version(s) after that which cause > the issue for me. Just adding: I have just installed the nVidia proprietary drivers. This issue does not happen with the nVidia proprietary drivers.
*** Bug 558088 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 552741 ***