You are not logged in.
Just updated my x86_64 Testing system, and noticed xorg server 1.9 come thru...
upon restart Compiz Fusion's wallpaper system is broken (I was using this instead of Gnome's) - it shows the Gnome desktop wallpaper, and any movement of windows leaves a hideous artifact - ghosting- behind. Just like being drunk, and turning too quickly...only I haven't been drinking ... and the artifact doesn't fade.
Turn off Compiz's wallpaper, and the artifacts disappear. Turn It back on , and the same artifacts are back where they were, but still no compiz wallpaper. Tried loose binding, indirect rendering, adjusting vsync manually.
I have a nVidia 8600GT on Phenom3-845.
Only other reference I have found is Ubu 10.10 having same issue : https://bugs.launchpad.net/ubuntu/+sour … bug/629391
Offline
I have the same problem. Quite annoying, since now all I'm staring at is black workspaces and it's hard for me to know where I am sometimes.
Hopefully this can get fixed soon enough.
[EDIT] Some details on my setup:
NVIDIA 7950GT under i686 arch
extra/xorg-server 1.9.0-1
extra/nvidia 256.53-1
community/compiz-core 0.8.6-2
Last edited by bkuri (2010-10-02 05:41:59)
Dell XPS 13 (9350) // i7 // 16GB // 512GB
Offline
I can confirm this.
I have also not found a solution for it yet.
I also have an nVidia 8600M GT.
The beta drivers seem to have solved some problems with Xorg 1.9, I wonder if this could be solved too?
Maybe I'll try it tomorrow.
Last edited by Stunts (2010-10-01 08:00:03)
Offline
Same here with Nvidia 260GTX
Beta drivers didn't helped.
Offline
Same thing here with ATI HD3470 on i686.
Offline
It's an upstream bug in the xserver.
For those who want to experiment by themselves, here is the patch:
--- a/damageext/damageext.c 2010-10-02 11:18:36.540987984 +0200
+++ b/damageext/damageext.c 2010-10-02 11:19:21.983987987 +0200
@@ -217,7 +217,6 @@ ProcDamageCreate (ClientPtr client)
if (!AddResource (stuff->damage, DamageExtType, (pointer) pDamageExt))
return BadAlloc;
- DamageSetReportAfterOp (pDamageExt->pDamage, TRUE);
DamageRegister (pDamageExt->pDrawable, pDamageExt->pDamage);
if (pDrawable->type == DRAWABLE_WINDOW)
Even though this is manifested with metacity+compositing in my case it looks like that same commit caused this bug also.
Offline
It's an upstream bug in the xserver.
Even though this is manifested with metacity+compositing in my case it looks like that same commit caused this bug also.
Thanks, that works fine.
nvidia (256.53-1) + compizStandAlone
Offline
http://aur.archlinux.org/packages.php?ID=41438
Here is the PKGBUILD and patches...
Offline
Thanks for putting up the fix, combuster. Worked great!
Offline
Worked for me as well, thanks!
#binarii @ irc.binarii.net
Matrix Server: https://matrix.binarii.net
-------------
Allan -> ArchBang is not supported because it is stupid.
Offline
I'm glad it helped...
Offline
what worked for me was to disable the wallpaper feature in ccsm. my wallpaper still shows up though!
Offline
http://aur.archlinux.org/packages.php?ID=41438
Here is the PKGBUILD and patches...
I can also confirm that this PKGBUILD works great. Thanks again, combuster!
Dell XPS 13 (9350) // i7 // 16GB // 512GB
Offline
Hi Guys,
I am trying to use this pkg to resolve the same issue I believe but here is the terminal asking me to remove xorg-server on installation, is that normal??
[sweetth@myhost test]$ sudo pacman -U xorg-server-compositing-fix-1.9.0-1-i686.pkg.tar.xz
resolving dependencies...
looking for inter-conflicts...
:: xorg-server-compositing-fix and xorg-server are in conflict. Remove xorg-server? [y/N]
Offline
Yes, that's normal. It provides a replacement for it.
Last edited by frabjous (2010-10-09 16:58:44)
Offline
great work like a charm, but then when an update for xorg will come, is it going to update normally or would I have to do it manually?
Offline
thanks Combuster... I had same problem and the package build solved it.
Offline
when will it be safe to return to the main xorg-server? I guess I'm asking *How* will we know when it is safe...
Offline
I'll flag it out of date, report here and in comments from AUR.
We'll see if they will merge this patch in 1.9.1, for now it's in master branch, not yet in 1.9 branch...
Offline
Correct me if I'm wrong but isn't this an api change and related to compiz rather than reverting to fix..
Just reading the upstream the latest fix seems to be applied to compiz 0.9.0(though that is a problem in it self as 0.8.6 is latest stable) unless I'm mistaken http://bugs.freedesktop.org/show_bug.cgi?id=30260#c10
Offline
This is not only related to compiz wallpaper plugin, I have metacity with compositing enabled and I had all sorts of artifacts. One of my friends also reported that xcompmngr with compositing is giving him headaches with artifacts.
So in both cases (api change in xserver that needs modifying of all window managers that supports compositing or regression that reflects on all compositing window managers) this must be reverted temporarily untill a permanent solution is found.
Offline
This is not only related to compiz wallpaper plugin, I have metacity with compositing enabled and I had all sorts of artifacts. One of my friends also reported that xcompmngr with compositing is giving him headaches with artifacts.
So in both cases (api change in xserver that needs modifying of all window managers that supports compositing or regression that reflects on all compositing window managers) this must be reverted temporarily untill a permanent solution is found.
I can confirm this. I am using compiz with metacity and my screen does not repaint correctly, it cannot display correctly characters I type in a textarea.
Offline
I've installed the patched package. It does not work for me with intel driver 2.12.0-3. Hope the xorg developers fix that soon.
Offline
You can not have compiz with metacity, both are window managers, you use either one or the other.
If you are using compiz, try with indirect rendering enabled, either with fusion-icon or starting compiz with --indirect-rendering switch.
Offline
PKGBUILD updated, this package is still neded because the patch that reverts the offending commit didn't make it in 1.9.1
If there are any problems after updating please let me know. Works for me...
Offline