Bug 214947

Summary: CPU slowdown caused by compiz causes screensaver not to go into suspend mode
Product: [Fedora] Fedora Reporter: Vladimir Kotal <vlada>
Component: compizAssignee: Kristian Høgsberg <krh>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 6CC: esteban.xandri, mcepl, ncunning, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-10-23 21:48:00 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:
Attachments:
Description Flags
Xorg log file none

Description Vladimir Kotal 2006-11-10 08:02:06 UTC
Description of problem:
After compiz was enabled some of the screensavers cause high CPU load which
prevents entering suspend mode.

Version-Release number of selected component (if applicable):
compiz-0.0.13-0.32.20060817git.fc6

How reproducible:
enable Desktop effects (compiz) and observe screensaver behavior

Steps to Reproduce:
1. enable Desktop effects
2. wait for some CPU-intensive screensaver to come up
  
Actual results:
screensaver runs even after suspend period is over

Expected results:
display should enter suspend period after suspend period has ended

Additional info:
some screensavers are ok and allow entering suspend mode

Comment 1 Vladimir Kotal 2006-11-10 08:02:53 UTC
Created attachment 140867 [details]
Xorg log file

Comment 2 Vladimir Kotal 2006-11-10 08:03:42 UTC
The problem with CPU load after compiz is enabled is an issue by itself.

Comment 3 Matěj Cepl 2007-10-23 21:48:00 UTC
For official Red Hat Enterprise Linux support, please log into the Red Hat
support website at http://www.redhat.com/support and file a support ticket, or
alternatively contact Red Hat Global Support Services at 1-888-RED-HAT1 to speak
directly with a support associate and escalate an issue.

Closing and waiting on opening of the new bug by the support team