Created attachment 660454 [details] screenshot with errors in top bar (accessab.) and background image Description of problem: First, the fedora logo is not visible at the gdm login for 90% of the logins. Instead there are some rectangels, squares etc. puzzled at this place. Second, the accessibility icons are sometimes black squares and are only visible when you mouseover. Sometimes there are also fragments instead of chars in the username, calendar/time and activities text. Third, the dialog to change the background image is producing rubbish half the time i use it. no matter what image i chose. I dont know if it is connected, but I have those 2 errors in /var/log/messages kernel: [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12! and gdm-simple-slave[710]: WARNING: Failed to give slave programs access to the display. Trying to proceed. Version-Release number of selected component (if applicable): $ gnome-shell --version GNOME Shell 3.6.2 How reproducible: Don't know. Currently the fedora logo is missing 90% of the time, the other bugs happen around 50% of the time. Steps to Reproduce: 1. - 2. - 3. - Actual results: graphics bugs Expected results: no graphics bugs :) Additional info: added two screenshots
Created attachment 660455 [details] screenshot with glyph and icon bugs in the top bar
All Problems are still there after Fedora 18 release and a fresh install. Hardware is working fine under Fedora 17 and Windows.
Have a look in /var/log/Xorg.0.log I have these messages from the same time as the message appears in dmesg: [ 97766.969] (II) RADEON(0): radeon_dri2_schedule_flip:665 fevent[0x6e5f750] [ 97767.076] (II) RADEON(0): radeon_dri2_flip_event_handler:1069 fevent[0x6e5f750] width 2560 pitch 10240 (/4 2560) [ 97773.012] (II) RADEON(0): radeon_dri2_schedule_flip:665 fevent[0x97ce6d0] [ 97773.112] (II) RADEON(0): radeon_dri2_flip_event_handler:1069 fevent[0x97ce6d0] width 2560 pitch 10240 (/4 2560) [ 97773.117] (II) RADEON(0): radeon_dri2_schedule_flip:665 fevent[0xb91b610] [ 97773.213] (II) RADEON(0): radeon_dri2_flip_event_handler:1069 fevent[0xb91b610] width 2560 pitch 10240 (/4 2560) (I nave no idea if my problem is related to your problem.)
Alt + F2 + 'r' fixes all issues until reboot
This might be related. There are patches. I've not tried them. <https://bugzilla.kernel.org/show_bug.cgi?id=49981>
I did not encounter this bug for 2 weeks. Chances are good it is fixed.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.