After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 650819 - Strange rendering artefacts visible in terminal
Strange rendering artefacts visible in terminal
Status: RESOLVED NOTGNOME
Product: vte
Classification: Core
Component: general
0.24.x
Other Linux
: Normal normal
: ---
Assigned To: VTE Maintainers
VTE Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-05-22 20:17 UTC by Wouter Bolsterlee (uws)
Modified: 2011-05-27 22:09 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Screenshot illustrating the problem (129.53 KB, image/png)
2011-05-22 20:17 UTC, Wouter Bolsterlee (uws)
Details
Another screenshot (6.58 KB, image/png)
2011-05-24 20:42 UTC, Wouter Bolsterlee (uws)
Details

Description Wouter Bolsterlee (uws) 2011-05-22 20:17:36 UTC
Created attachment 188350 [details]
Screenshot illustrating the problem

Since some time, I'm seeing strange rendering artefacts in gnome-terminal. See the attached screenshot to see how it looks like. Sometimes scrolling the widget up and down "fixes" the problem, but after a while the issue starts to show up again.

I'm not sure this is specific to gnome-terminal, so feel free to reassign to another product if this is a known issue. Please let me know if you have any pointers, since I couldn't find anything!
Comment 1 Christian Persch 2011-05-22 22:19:18 UTC
Maybe a graphics driver bug?
Comment 2 Christian Persch 2011-05-24 12:30:47 UTC
The screenshot in bug 650863 looks a bit similar...

Do you run metacity, or gnome-shell? If metacity, is compositing enabled or disabled?
Comment 3 Wouter Bolsterlee (uws) 2011-05-24 20:29:22 UTC
I'm using metacity with the compositor enabled on a Intel graphics card in a desktop computer:

00:02.0 VGA compatible controller: Intel Corporation 82G33/G31 Express Integrated Graphics Controller (rev 02)
Comment 4 Christian Persch 2011-05-24 20:35:26 UTC
Can you check if the same happens with compositor disabled? If not, then -> metacity and you're out of luck since the compositor isn't maintained, afaik.
Comment 5 Wouter Bolsterlee (uws) 2011-05-24 20:42:14 UTC
Created attachment 188523 [details]
Another screenshot

Another screenshot with metacity with compositor disabled. These are a few lines from a gnome-terminal window with top(1) running after disabling the compositor and restarting metacity completely.
Comment 6 Christian Persch 2011-05-24 21:15:47 UTC
<chpe> Company: any idea what could cause a rendering problem like in #650819 ?
<Company> chpe: graphics driver, 1 pixel off in gdk_window_move_region() region, similar problem in X, (RGBA visual in use and) forgetting to clear something
chpe: i can find lots of reasons that might result in output like that :/
<Company> could also be someone getting the rowstride wrong somewhere
<chpe> hmm. I guess transparency / rgba visual does come into it, since I've never seen that problem
Comment 7 Christian Persch 2011-05-24 21:57:57 UTC
<Company> chpe: <ickle> it's a driver bug of some sort, tiling/fencing likely.

So I'm afraid this is NOTGNOME. Sorry!

If the driver version is recent-ish an upstream bug report might make sense, but the original version says you're running GNOME 2.30 and I guess the driver is similaryly old too?
Comment 8 Wouter Bolsterlee (uws) 2011-05-24 22:10:02 UTC
While I'm using Gnome 2.30.x (actually, a 2.30 and 2.32 mix), the XOrg intel graphics driver I'm using isxserver-xorg-video-intel 2.15.0. According to http://intellinuxgraphics.org/2011Q1.html this is a fairly recent stable release, which is recommended for ordinary users according to the instructions on http://intellinuxgraphics.org/download.html.

Any clue where my report is most appropriate? Xorg? Intel driver? GTK+?
Comment 9 Christian Persch 2011-05-27 22:09:21 UTC
To the intel driver delevolpers, I think.