Bug 855940 - display corruption on intel GM45
Summary: display corruption on intel GM45
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 17
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-10 16:44 UTC by udo.rader
Modified: 2013-08-01 07:03 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-08-01 07:02:49 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
lspci -vvvvn output (977 bytes, application/octet-stream)
2012-09-10 16:44 UTC, udo.rader
no flags Details
xorg.conf (1.14 KB, text/plain)
2012-09-10 16:45 UTC, udo.rader
no flags Details
Xorg.0.log (89.31 KB, text/plain)
2012-09-10 16:46 UTC, udo.rader
no flags Details
foto of display corruption (116.50 KB, image/jpeg)
2012-09-10 16:47 UTC, udo.rader
no flags Details
another foto showing the failure with google-chrome (122.25 KB, image/jpeg)
2012-09-10 17:08 UTC, udo.rader
no flags Details

Description udo.rader 2012-09-10 16:44:06 UTC
Created attachment 611500 [details]
lspci -vvvvn output

following some recent update in the past weeks, my Intel GM45 based Lenovo W500 laptop shows display corruption after a workday or so, see attached screenshot.

The "white striped" areas in the attached foto (thunderbird) show the effect, as well as the partially unreadable text line.

I see the same in any application (google-chrome, terminal, ...), sometimes text or images just "disappear" only to reoccur after pressing some arbitrary key or moving around with the mouse.

Neither switching to a text console nor logging out and in solves the problem, only rebooting the laptop gets it back to normal.

The logfiles (Xorg.log, dmesg) don't show anything suspicious, see attachments.

The "only" pecularity maybe is that I happen to have an xorg.conf file because my external monitor is not correctly detected (and has not for a long time, I think even pre FC13 or so).

Comment 1 udo.rader 2012-09-10 16:45:28 UTC
Created attachment 611501 [details]
xorg.conf

Comment 2 udo.rader 2012-09-10 16:46:11 UTC
Created attachment 611502 [details]
Xorg.0.log

Comment 3 udo.rader 2012-09-10 16:47:07 UTC
Created attachment 611503 [details]
foto of display corruption

Comment 4 udo.rader 2012-09-10 17:08:45 UTC
Created attachment 611508 [details]
another foto showing the failure with google-chrome

Comment 5 Fedora End Of Life 2013-07-04 01:57:14 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 6 Fedora End Of Life 2013-08-01 07:03:06 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.


Note You need to log in before you can comment on or make changes to this bug.