Bug 745463 (Video)

Summary: Artefacts in Gnome3, KDE, LXDE after period of time
Product: [Fedora] Fedora Reporter: Radamanf <radamanf>
Component: gnome-desktop3Assignee: Richard Hughes <hughsient>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 17CC: hughsient
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-01 17:04:57 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
KDE rendering
none
smoltprofile
none
Xorg.0.log
none
Xorg.1.log
none
Xorg.9.log
none
Gnome3 Artifacts
none
Gnome 3 Artefacts Second
none
dmesg output
none
dgm/0.log
none
dgm/0-greeter.log
none
dgm/0-slave.log
none
dgm/1-greeter.log
none
glxinfo
none
Screen with no errors, to make shure that Initially I got fine working screen
none
New screen, none

Description Radamanf 2011-10-12 12:55:29 UTC
Description of problem:
Initially all is fine, then after couple of hours on some windows start to appear artefacts/alterations/marks/scratches call whatever you like (really annoying)

Working for a couple of hours in Gnome 3 desktop

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. 
Working for a couple of hours in Gnome 3 desktop
2.
Use many windows at the same time
3.
Switch between them occasionally

(Everyday work on Linux, bloody ridiculous Gnome 2 was much better)

  
Actual results:
Cracks alterations by drawing windows

Expected results:
Good looking windows (readable info no artefacts)

Additional info:
Attached Print screen, not altered in GIMP as it is on my screen

Comment 1 Radamanf 2011-11-23 10:53:54 UTC
This bug is also actual for KDE 4.6.5

But with KDE is not such critial because it renders every window that you are selecting and content became normal again, apart from web pages!
Since I've installed Fedora 15 all this crap started to happen, it's like some lazy rendering model which is working badly.

Linux 2.6.41.1-1.fc15.x86_64 x86_64

Display Info
Vendor:   Tungsten Graphics, Inc
  Model:   Mesa DRI Mobile IntelĀ® GM45 Express Chipset 
  Driver:   2.1 Mesa 7.11

Comment 2 Radamanf 2011-11-23 10:55:19 UTC
Created attachment 535418 [details]
KDE rendering

Comment 3 Radamanf 2011-11-23 10:56:53 UTC
This can be a problem with software rendering or OpenGL, I've installer cairo-dock with OpenGL support and it was crashed the system, KDE stop responding just mouse still moving and nothing else, so I should kill X

Comment 4 Radamanf 2012-02-15 17:35:40 UTC
Those Artefacts keep bothering me, can you please help me?

I'll attach some files required for you be reading this article http://fedoraproject.org/wiki/How_to_debug_Xorg_problems

Comment 5 Radamanf 2012-02-15 17:36:32 UTC
Created attachment 562277 [details]
smoltprofile

Comment 6 Radamanf 2012-02-15 17:37:25 UTC
Created attachment 562278 [details]
Xorg.0.log

Comment 7 Radamanf 2012-02-15 17:38:05 UTC
Created attachment 562279 [details]
Xorg.1.log

Comment 8 Radamanf 2012-02-15 17:39:14 UTC
Created attachment 562280 [details]
Xorg.9.log

Comment 9 Radamanf 2012-02-15 17:40:46 UTC
Created attachment 562281 [details]
Gnome3 Artifacts

Comment 10 Radamanf 2012-02-15 17:45:01 UTC
Created attachment 562282 [details]
Gnome 3 Artefacts Second

Initially everything looks good, no any artefacts, but after some time images got refreshed and redrawn with them, looks awful and very annoying. Can this be fixed be changing video drivers??

Comment 11 Radamanf 2012-02-15 17:48:53 UTC
/etc/X11/xorg.conf - does not exist in system.

Comment 12 Radamanf 2012-02-15 17:49:35 UTC
Created attachment 562283 [details]
dmesg output

Comment 13 Radamanf 2012-02-15 17:54:31 UTC
Created attachment 562284 [details]
dgm/0.log

Comment 14 Radamanf 2012-02-15 17:55:05 UTC
Created attachment 562285 [details]
dgm/0-greeter.log

Comment 15 Radamanf 2012-02-15 17:55:36 UTC
Created attachment 562286 [details]
dgm/0-slave.log

Comment 16 Radamanf 2012-02-15 17:56:11 UTC
Created attachment 562287 [details]
dgm/1-greeter.log

Comment 17 Radamanf 2012-02-17 14:18:04 UTC
Created attachment 563914 [details]
glxinfo

Comment 18 Radamanf 2012-03-07 11:09:05 UTC
Created attachment 568250 [details]
Screen with no errors, to make shure that Initially I got fine working screen

Comment 19 Radamanf 2012-07-26 14:00:03 UTC
Created attachment 600513 [details]
New screen,

Appears in this case font data are corrupted in memory, I've even restarted Firefox and this screen is captured after FF restart. I hope after whole restart it will dissapear.

Comment 20 Fedora End Of Life 2012-08-07 16:19:56 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 21 Radamanf 2012-08-08 12:59:32 UTC
This BUG is still present. I've updated to Fedora 17 (latest currently). It's not gone anywhere. Do you guys need some more details about my hardware? You can give me some commands and I can send output to you.

Comment 22 Fedora End Of Life 2013-07-04 05:49:59 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 23 Fedora End Of Life 2013-08-01 17:05:04 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.