Bug 436633

Summary:	Sleep no longer available (in Gnome GUI) in 2.6.24.3-12
Product:	[Fedora] Fedora	Reporter:	Stephen Warren <swarren>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	8
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-04-11 05:03:53 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Stephen Warren 2008-03-08 18:29:52 UTC

Description of problem:

When logged into Gnome, the Gnome System menu has a "Shutdown" option, which
displays a dialog box showing options suspend/hibernate/restart/cancel/shutdown.

When running kernel 2.6.24.3-12.fc8.i686, the suspend button is hidden (and
whatsmore, in an ugly way that leaves a weird-sized gap instead of filling the
space with the remaining buttons)

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

kernel-2.6.24.3-12.fc8.i686

How reproducible:
Always (tried a couple times only)

Steps to Reproduce:

1. Boot into said kernel
2. Log into Gnome
3. System -> Shutdown
4. Look at the dialog box
  
Actual results:

No suspend button

Expected results:

Should see a suspend button.

Additional info:

Booting back into kernel-2.6.23.15-137.fc8.i686 solves the issue.

Personally, I never actually use suspend, so it's not a big deal for me.
However, I assume lots of other people do...

Hardware: Dell Inspiron 9300 laptop.

Comment 1 Stephen Warren 2008-03-08 18:42:01 UTC

A fresh reboot appears to solve the issue; the menu item is there again. Maybe
this is intermittent. Perhaps the bluetooth problems I was having screwed
something up?

Comment 2 Stephen Warren 2008-04-11 05:03:53 UTC

I haven't seen this in a while. I guess it was some intermittent glitch. I'll
close the bug.