Hide Forgot
Description of problem: After upgrading to latest xorg-x11-server 1.9.5-1.fc14, and moving a gnome terminal window around for a while, hitting the screen borders there is sever corruption both of window contents and of the decoration. The corruption is *not* present with the original xorg-x11-server-1.9.0-15.fc14.src.rpm Version-Release number of selected component (if applicable): xorg-x11-server-1.9.5-1.fc14 How reproducible: 100% Steps to Reproduce: 1. Install fc14 in a vmware virtual machine. 2. run yum update 3. Move a gnome-terminal window around for a while Actual results: Corruption in the window contents and border Expected results: No corruption in the window contents and border. Additional info: I've narrowed the regression down to dropping the -Os in the CFLAGS when building the xorg-x11-server src.rpm. On xorg-x11-server-1.9.0-15.fc14.src.rpm the optimization level is there, but on xorg-x11-server-1.9.5-1.fc14.src.rpm that particular CFLAG is gone. However, that only cures the symptoms. The real bug is present somewhere either in the xserver package or in gcc shipped with fc14. I've verified that if -Os is dropped, the problem also appears in vanilla xorg-server-1.9.0 Thanks, Thomas
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, if available), * X server log file (/var/log/Xorg.*.log*; check with grep Backtrace /var/log/Xorg* which logs might be the most interesting ones, send us at least Xorg.0.log) * output of the dmesg command, and * system log (/var/log/messages) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above. However, I have my doubts there will be much work spent on fixing this in F14 which will be EOSed soon anyway. We will review this issue again once you've had a chance to attach this information. Thanks in advance.
Note that a fix for fc 14 is already mentioned in the bug report. You only need to release an update with an altered compilation flag. This is a pretty severe bug since it should affect most Xorg drivers using software rendering, and it is probably spilling over to fc15/fc16 as well, but I haven't checked yet. I will attach the needed info in a later update.
(In reply to comment #2) > This is a pretty severe bug since it should affect most Xorg drivers using > software rendering, and it is probably spilling over to fc15/fc16 as well, but > I haven't checked yet. Do so, please. Frankly, I don't expect much effort on fixing F14 bugs at this moment (F14 is going to be EOSed in two months or so). Reproduction on F16beta (http://fedoraproject.org/get-prerelease) with the same logs requested in comment 1 could actually make a difference. Thank you for filing the bug.
(In reply to comment #3) > (In reply to comment #2) > > This is a pretty severe bug since it should affect most Xorg drivers using > > software rendering, and it is probably spilling over to fc15/fc16 as well, but > > I haven't checked yet. > > Do so, please. Frankly, I don't expect much effort on fixing F14 bugs at this > moment (F14 is going to be EOSed in two months or so). Reproduction on F16beta > (http://fedoraproject.org/get-prerelease) with the same logs requested in > comment 1 could actually make a difference. > > Thank you for filing the bug. Since I've already spent a couple of hours tracking down the cause and providing a fix right in your hand, If you don't believe it's going to see any attention, I'm afraid I can't spend anymore time on this. We'll just have to recommend our users not to use FC14, and if they hit this in later fedora distros, I'll point them to this bug. Thanks, Thomas
the problem is a the change in glibc memcpy behaviour. I think there is a patch upstream we could backport to avoid overlapping memcpys. I expect the gcc flags just allow more memcpys to go to glibc instead of being trapped in gcc builtins.
After discussing it a little bit we have a suspicion that this could be acutally a duplicate of bug 730797 which is ON_QA. Could you please test the update suggest there and tell us whether it helped? Thank you
Matej, I'll try to test as soon as time allows. /Thomas
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached 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 to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping