Bug 594726 - intel [945GME/965GM] Fontdisplay in xterm and gnome-terminal broken with compiz enabled
Summary: intel [945GME/965GM] Fontdisplay in xterm and gnome-terminal broken with comp...
Status: RESOLVED DUPLICATE of bug 597596
Alias: None
Product: openSUSE 11.3
Classification: openSUSE
Component: X.Org (show other bugs)
Version: Factory
Hardware: Other Other
: P3 - Medium : Major (vote)
Target Milestone: ---
Assignee: Stefan Dirsch
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-08 09:23 UTC by Andreas Jaeger
Modified: 2010-06-02 14:31 UTC (History)
4 users (show)

See Also:
Found By: Product Management
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Jaeger 2010-04-08 09:23:41 UTC
Entering text in xterm or gnome-terminal gives a broken display, sometimes black squares instead of characters, sometimes bars.
Comment 1 Andreas Jaeger 2010-04-08 11:36:32 UTC
Note: If I disable compiz, it seems to work fine.

I also have the problem that if I switch between two tabs in Firefox that after the tab switch the content is not redrawn and the old contents is displayed.  After a resize operation it is updated correctly.

This error is also fixed with disabling compiz.

So, it looks to me like AIGLX is broken in the Intel driver.
Comment 2 Stefan Dirsch 2010-04-08 13:05:49 UTC
This likely is a compiz or Mesa bug.
Comment 4 Andreas Jaeger 2010-06-02 12:27:35 UTC
similiar on Intel system with GM965 graphics card - here I see the problem in the gnome-terminal: Sometimes refreshes do not happen (type "ls" several times or switch between consoles) but are redrawn later.

This makes compiz completely unusable.

This is a regression from 11.2, therefore adjusting severity.
Comment 5 Andreas Jaeger 2010-06-02 12:29:08 UTC
Looks like a duplicate of 597596 - correct?
Comment 6 Andreas Jaeger 2010-06-02 12:46:08 UTC
YEs, duplicate

*** This bug has been marked as a duplicate of bug 597596 ***