Bug 581291 - X slows down due to looping approx. 30 seconds after logging-in
Summary: X slows down due to looping approx. 30 seconds after logging-in
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-11 15:29 UTC by Peter Levart
Modified: 2018-04-11 17:40 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-04 23:29:49 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
the /var/log/Xorg.0.log file (2.34 MB, text/plain)
2010-04-11 15:29 UTC, Peter Levart
no flags Details

Description Peter Levart 2010-04-11 15:29:49 UTC
Created attachment 405826 [details]
the /var/log/Xorg.0.log file

Description of problem:

approx. 30 seconds after logging-in, the system becomes very unresponsive (even mouse cursor barely moves, hopping with huge steps). The situation lasts for couple of minutes than the system becomes responsive again and works O.k. until next reboot.

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

xorg-x11-drv-intel-2.9.1-1.fc12.x86_64

How reproducible:

Always

Steps to Reproduce:
1. Have the Intel DG45ID motherboard with integrated 4500HD graphics
2. Install Fedora 12 Live KDE x86_64
3. Log-in
  
Actual results:

The slow-down is a result of some kind of nearly infinite loop (which finally stops after some minutes) that prints lots of repeated blocks of text into the Xorg.0.log file (2.5 Mbytes)

Expected results:

No such crazy behavior...

Additional info:

See attached Xorg.0.log.
Was using F11 before with no such behavior.

Comment 1 Bug Zapper 2010-11-03 17:23:10 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  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 '12'.

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 12'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 12 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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 2 Peter Levart 2010-11-04 07:24:12 UTC
This seems to be fixed already. I'm still running F12 on the same HW and this is not happening any more for a long time.

Comment 3 Matěj Cepl 2010-11-04 23:29:49 UTC
Thank you for letting us know.


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