Bug 697309

Summary:	Fedora 15 - Power Off Error
Product:	[Fedora] Fedora	Reporter:	Colin Keeny <colin.keeny>
Component:	powerpc-utils-papr	Assignee:	David Woodhouse <dwmw2>
Status:	CLOSED WORKSFORME	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	15	CC:	dwmw2, jskala, tony
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:	2011-04-17 22:06:11 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 Colin Keeny 2011-04-17 16:43:23 UTC

Description of problem: 
When attempting to shut off laptop (click username > alt + 'power off...'), computer doesn't shut down. Instead, it logs off the current account and returns to initial Fedora log in screen. Tried to click the power off icon while in Fedora log in screen and nothing happens. 


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


How reproducible:
Click username > alt + 'power off...'


Steps to Reproduce:
1. Click username
2. Hold down alt + 'power off...'

  
Actual results:
Logs off current account and returns to initial Fedora log in screen.

Expected results:
Should log off account and shut off computer.

Additional info: None

Comment 1 Colin Keeny 2011-04-17 17:18:34 UTC

NOTE: This error only seems to happen after closing the laptop lid while logged in. Computer goes into suspend mode until reopened. I have reproduced this error several times through this method, but the lid must be closed for several hours.

However, recent attempts to reproduce this error have failed. Though, I have not left the lid closed for several hours.

I will attempt to reproduce this error again by closing the lid of my laptop while logged in... and not awakening laptop for several hours.

Comment 2 Colin Keeny 2011-04-17 22:06:11 UTC

The error seems to have been addressed in the recent update.