Bug 131847

Summary:	annoying error message
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Miikka Valkeapää <miikka1973>
Component:	KDE	Assignee:	Danny Al-Gaaf <dalgaaf>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	kde-maintainers
Version:	Final
Target Milestone:	---
Hardware:	i386
OS:	Other
Whiteboard:
Found By:	Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Miikka Valkeapää 2005-11-01 19:23:11 UTC

Every time when booting into system I get the following error message:

"error - KPowersave

The Powersave daemon is not running.

Starting it will improve performance:

/usr/sbin/rcpowersaved start"


When I issue the command: 

"/usr/sbin/rcpowersaved start" 

I get: "daemon already running"


How to get  rid  of this???

Comment 1 Dirk Mueller 2005-11-01 19:29:04 UTC

autologin enabled?

sounds like a race... kpowersave really shouldn't produce this popup

Comment 2 Danny Al-Gaaf 2005-11-01 20:59:38 UTC


*** This bug has been marked as a duplicate of 121965 ***

Comment 3 Lewis Rosenthal 2005-11-23 13:53:59 UTC

(In reply to comment #1)
> autologin enabled?
> 
> sounds like a race... kpowersave really shouldn't produce this popup
> 
Dirk, has a bug been filed against this condition (i.e., kpowersave error when autologin is enabled)? I came across this last night, and it drove me nuts (along with what I've posted in Bug #133411). It looks like kpowersave needs a little more time (or, perhaps more appropriately, rcpowersaved needs a little more time) than is being given to it when not stopping at the login screen.

Lewis

PS - Danny, this should not be marked as a dup *IF* this condition only occurs when autologin is enabled, and I would then suggest changing the name of this bug.

Comment 4 Lewis Rosenthal 2005-11-23 13:57:36 UTC

(In reply to comment #3)

> PS - Danny, this should not be marked as a dup *IF* this condition only occurs
> when autologin is enabled, and I would then suggest changing the name of this
> bug.
> 
Oops!!! My error; I should have read Bug #121965 more thoroughly. Yes, this is indeed a dup.

Apologies for the bug spam, everyone.

Lewis