Bug 773562 - Plugging in power cable temporarily freezes interface
Summary: Plugging in power cable temporarily freezes interface
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gdm
Version: 16
Hardware: i686
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-12 09:34 UTC by Christopher Svanefalk
Modified: 2013-02-13 21:59 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-13 21:59:22 UTC
Type: ---


Attachments (Terms of Use)
lspci output (2.00 KB, application/octet-stream)
2012-01-12 09:34 UTC, Christopher Svanefalk
no flags Details
lspci -vv output (13.36 KB, application/octet-stream)
2012-01-12 09:35 UTC, Christopher Svanefalk
no flags Details

Description Christopher Svanefalk 2012-01-12 09:34:06 UTC
Description of problem:

Plugging a power cable into the system causes the interface to go into soft-freeze (background processes still appear to be running) for approximately 10-15 seconds. During this period, the interface is completely unresponsive, and does not respond to any input, apart from allowing the mouse pointer to move around.

Background processes still seem active. For example, a YoutTube video playing in Chrome will continue to play normally, even though the browser itself can not be manipulated.

Version-Release number of selected component (if applicable): Fedora 16, latest updates as of January 12, 2012.


How reproducible: Every time


Steps to Reproduce:
1. Plug power cable into system
  
Actual results:

Soft-freeze

Expected results:

normal operation

Additional info:

I am running an HP Probook 4510s. Lspci and lspci -vv output is in attachement, and my smolt profile is here:

http://www.smolts.org/show?uuid=pub_37b46c83-d6c8-497a-8a72-88acd0eceb84+

other info available on request.

Comment 1 Christopher Svanefalk 2012-01-12 09:34:39 UTC
Created attachment 552359 [details]
lspci output

Comment 2 Christopher Svanefalk 2012-01-12 09:35:02 UTC
Created attachment 552360 [details]
lspci -vv output

Comment 3 Fedora End Of Life 2013-01-16 17:23:15 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 4 Fedora End Of Life 2013-02-13 21:59:25 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.


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