User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.4) Gecko/20100622 Fedora/3.6.4-1.fc13 Firefox/3.6.4 when Compiz is switched on, xterm starts to corrupt everything inside it's window. However, If another windows moves over the xterm and away again (backingstore) the corruption is fixed. Reproducible: Always Steps to Reproduce: 1. Enable compiz 2. Start XTerm 3. type something. Sometimes it takes 2 or 3 commands before it goes Actual Results: Corrupted, unreadable xterm Expected Results: Nice and clean XTerm [ra@morticia ~]$ rpm -q xterm xterm-256-1.fc13.i686 I rebuild the xterm in Rawhide (the f14 one) with no change.
Created attachment 431861 [details] Screenshot of XTerm corrupted
Created attachment 431862 [details] Another screenshot
Using gnome on a fully updated F13 machine.
I'm seeing something similar with compiz. When typing in xterm, I'm getting these vertical bars to the left of the letters. Works fine w. metacity (compositing on or off).
Oh, yes. FC13, 64-bit, fully updated.
of interest, if I drag to resize the xterm, the "glitches" while typing go away. If I then drag to resize the xterm to the original size, there are also no longer any glitches.
I've to add a "me too" to this bug. My config is : F13 64bits, compiz, emerald, all packages up to date as of Aug, 8th 2010. Switching back to KDE default window manager (kwin --replace) and newly started xterm are Ok. I can also confirm that resize horizontally the xterm window (expand from 80 chars wide to 81 and then back to 80) fixes the problem. I attach two small screenshots I took, of a "vi" window containing characters that help show the problem. Using gimp to measure the window shows a difference of 2 pixels of the width of the inner rectangle in which characters are drawn.
Created attachment 437470 [details] this one is showing badness in characters.
Created attachment 437472 [details] This one is OK, horizontal resizing was done before.
I "fixed" (workaround) the XTerm issue by creating a file in my home named .Xdefaults and inserted the following text in it : ! For XTerm.... We need to do that because when using the default borderWidth ! (1), then compiz is confused, and Window width is not accurate (off by 2). XTerm*borderWidth: 0 This is merge with my other X resources at session opening time and prevent xterm from creating an inner colored rectangle which is by default 1 pixel. /me now wondering if the bug is in Xterm or not... Paul
Just tried the workaround mentioned in comment 10. This workaround "works" for me as well.
Same bug affects Ubuntu as well: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/635258
The bug appears to have been introduced by: http://git.compiz.org/compiz/core/commit/?h=compiz-0.8&id=6d4833f0e3217c63f516acbdc90796b4d78eecfb The bug is fixed either by reverting that commit or changing the added lines to: w->width = attr.width + (attr.border_width * 2); w->height = attr.height + (attr.border_width * 2); I'm currently unable to get to http://bugs.opencompositing.org/ so I have not filed an upstream bug report.
Patch has been committed upstream: http://git.compiz.org/compiz/core/commit/?h=compiz-0.8&id=0f95c41a0aa175ddf7947ba18b01f746c95594a9
I was able to fix this issue by doing the following: Applying upstream fix mentioned above Changing all references to gdk_display to gdk_display_get_default in BUILD/compiz-0.8.6/gtk/window-decorator/gtk-window-decorator.c and rebuilding with rpmbuild -bb SPEC/compiz.spec I am currently using the rpm and don't see the error, however, I do not know if this introduces new errors.
*** Bug 627116 has been marked as a duplicate of this bug. ***
compiz-0.8.6-5.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/compiz-0.8.6-5.fc14
compiz-0.8.6-6.fc14 has been pushed to the Fedora 14 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 compiz'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/compiz-0.8.6-6.fc14
Created attachment 464350 [details] Black blocks instead of characters
I am having black blocks instead of characters, as show in the screenshot, however this are removed with a minimize/restore. Maybe it is a driver bug.
(In reply to comment #20) > > Maybe it is a driver bug. I'm unable to reproduce the bug with the updated package, what driver are you using?
(In reply to comment #21) > (In reply to comment #20) > > > > > Maybe it is a driver bug. > > > I'm unable to reproduce the bug with the updated package, what driver are you > using? r300g
compiz-0.8.6-6.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
I'll re-open this bug report because the issue is still present in F13. I have tried the already built compiz package which contains the correct patch: https://koji.fedoraproject.org/koji/buildinfo?buildID=205340 and it works perfect. Please can you push it out as an official update for F13? Thank you very much in advance!
compiz-0.8.6-2.fc13 has been submitted as an update for Fedora 13. https://admin.fedoraproject.org/updates/compiz-0.8.6-2.fc13
(In reply to comment #24) > I'll re-open this bug report because the issue is still present in F13. > > I have tried the already built compiz package which contains the correct patch: > https://koji.fedoraproject.org/koji/buildinfo?buildID=205340 > and it works perfect. Please can you push it out as an official update for F13? > > Thank you very much in advance! Pushed to testing https://admin.fedoraproject.org/updates/compiz-0.8.6-2.fc13
compiz-0.8.6-2.fc13 has been pushed to the Fedora 13 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 compiz'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/compiz-0.8.6-2.fc13
compiz-0.8.6-2.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.