| Summary: | [Nvidia/prop] text rendering glitches with nvidia drivers under xcompmgr | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | xorg | Reporter: | Jason Faulkner <jasonlf> | ||||||
| Component: | Server/General | Assignee: | Xorg Project Team <xorg-team> | ||||||
| Status: | RESOLVED DUPLICATE | QA Contact: | Xorg Project Team <xorg-team> | ||||||
| Severity: | normal | ||||||||
| Priority: | high | CC: | adrian, ajax, aplattner, john5788 | ||||||
| Version: | git | Keywords: | cleanup0407 | ||||||
| Hardware: | x86 (IA32) | ||||||||
| OS: | Linux (All) | ||||||||
| URL: | http://j.oldos.org/xorg.png | ||||||||
| Whiteboard: | |||||||||
| i915 platform: | i915 features: | ||||||||
| Attachments: |
|
||||||||
|
Description
Jason Faulkner
2004-08-31 11:20:45 UTC
I also get something related to this in XChat... http://j.oldos.org/xchat.png I too having problems with nvidia and composite. the problem happens in RC1 RC2 and still happens in RC3. I have done some testing, switching on and off options in xorg.conf, and the problems is directly linked to nvidia drivers. I have tried three diffrent versions of nvidia drivers, and problem is still there. Importent to note is that it ONLY happens when i enable composite in xorg.conf and using _close_ nvidia drivers! It is not related to xcompmgr. this is an image explaining the problem: http://www.brad-x.com/screengallery/displayimage.php?album=4&pos=7 Alex V. bornio@gmail.com please do not attach multiple issues to the same bug unless you're sure they're caused by the same underlying problem. we'd rather have multiple bugs for the same behaviour than one bug describing multiple problems, because it's much much harder to close the latter. bugzilla is not a forum. the original report here (cursor issues in firefox) is a duplicate of bug #1159, so i'm repurposing this bug for the text display problem. does this occur under all xcompmgr modes? (-a, -n, -c, -s) The text gliches happen even without xcompmgr running. I'm making this a blocker. I've pretty well done an informal poll, and this seems to affect all NVIDIA card users who I've talked to. Hopefully one of the people having the problem who took part in the poll, will write a patch to fix the issue and attach it to the bug report while patches are still being accepted. It's never to late to vote with patches, just attach the bugfix to the report using the bugzilla file attachment feature above. Time is running out however, RC4 was just tagged in CVS, and the final release will probably be tagged in a day or two unless some glaring issue gets in the way. mass component shift / reassign for proprietary nVidia driver bugs. *** Bug 1159 has been marked as a duplicate of this bug. *** This bug probably wont be investigated until it's assigned to someone from Nvidia. The Driver/nVidia component should be owned by Nvidia rather than xorg-team. (In reply to comment #9) > This bug probably wont be investigated until it's assigned to someone > from Nvidia. The Driver/nVidia component should be owned by Nvidia > rather than xorg-team. it is owned by nvidia, bugzilla's just stupid and doesn't reassign things properly. correctness problems in closed drivers are not blockers. Does this problem still reproduce with the 1.0-8756 driver? If so, please attach an nvidia-bug-report.log. Created attachment 5625 [details]
nvidia-bug-report.log with 1.0.8756
artifacts in firefox still occur with 1.0.8756
Adrian, Can you please attach a screenshot to the bug? The other posters' screenshots seem to have disappeared. I still get this problem with xorg-7.0-r1 and the nvidia drivers v 1.0.8762. I'll attach another screenshot. Created attachment 6219 [details]
artifacts in firefox
We managed to reproduce this with the VESA driver, which means this is most likely a Firefox bug. Unassigning and moving to Server/general just to be safe. Sorry about the phenomenal bug spam, guys. Adding xorg-team@ to the QA contact so bugs don't get lost in future. surely this should probably then be a firefox bug? I'm going to go out on a limb and call this a dupe of #8871. *** This bug has been marked as a duplicate of bug 8871 *** Is it possible for a bug to be a dupe of a bug that was filed about 7000 bugs later? Yes, if the primary bug has more useful information. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
