Bug 769943

Summary: Gnome Freezes
Product: [Fedora] Fedora Reporter: Erasmo Acosta <eacosta>
Component: gnome-shellAssignee: Richard Hughes <hughsient>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 16CC: browning48ky, collura, hughsient, maxamillion, otaylor, samkraju, ssm3Tjololo, walters
Target Milestone: ---   
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-02-13 14:38:52 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Erasmo Acosta 2011-12-22 19:44:45 UTC
Description of problem:
The screen freezes and becomes unresponsive. I notices this happens when the VMWare player is up and I'm interacting with it. I noticed this only happens on my desktop, not on my laptop (both are on F16 x86_64). I have no evidence to back this up, but I suspect the Intel HD Graphics Driver.

Only the desktop seems freeze. I can still manipulate the Virtual Machine thru VNC. I can CTRL-ALT-F2 to a console, login and collect debug information.

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


How reproducible: Not 100%


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Erasmo Acosta 2011-12-23 14:58:47 UTC
Please advise on what would you like me to gather to help debug this.

Comment 2 Erasmo Acosta 2011-12-26 23:01:16 UTC
I did more research. If I kill the gnome-shell process, everything goes back to normal. I don't have to CTRL-ALT-BACKSPC

Comment 3 Erasmo Acosta 2012-01-31 21:44:51 UTC
Has someone taken a look at this bug? I experience it frequently. Can you tell me what kind of info I should collect when the freeze happens?

Comment 4 Scott Smith 2012-05-21 16:15:20 UTC
I had this issue as well. I managed to "fix" it by changing computers :/ I think it was an issue with my graphics card/driver. I was unable to diagnose anything even with extensive help in #gnome, #fedora, etc. There are no errors in any logs that I could see...Sometimes it would fix itself, it seemed like a massive amount of lag; even though I have 8GB of ram.

Comment 5 Fedora End Of Life 2013-01-16 13:45:41 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 '16'.

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 16'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 16 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 to click on 
"Clone This Bug" 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 6 Fedora End Of Life 2013-02-13 14:38:54 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.