Bug 120154

Summary:	Power profiles set wrong on pulling plug
Product:	[openSUSE] SUSE Linux 10.1	Reporter:	Michael Stather <kontakt>
Component:	Mobile Devices	Assignee:	Danny Kukawka <dkukawka>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	behlert, dkukawka
Version:	Alpha 1
Target Milestone:	---
Hardware:	Other
OS:	All
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Michael Stather 2005-10-04 15:46:21 UTC

When I start up my notebook with AC on, the power state is displayed correctly
as "AC". Then the following happens: If I pull the plug the icon changes to
"battery". If I reconnect the AC nothing happens, if I pull it again the state
changes back to "AC" (even if the AC isn´t attached) and then it stays there no
matter what I do. I haven´t seen this behaviour with 9.3
There are no messages from powersaved in the logs (I changed the CPUFREQ
governor to userspace for SpeedStep to work)

Comment 1 Stefan Behlert 2005-10-04 15:49:16 UTC

Holger, can it be that Danny's HAL-fixes are not in 10.1 alpha1?

Comment 2 Michael Stather 2005-10-04 15:55:24 UTC

I just checked and it even occurs with the default CPUFREQ governor

Comment 3 Holger Macht 2005-10-05 09:37:26 UTC

The governor has nothing to do with this issue. The hal fix for this issue is
not included in 10.1 alpha1. It will be included in the next release or even
with the you update for 10.0. 

I think this is a WONTFIX then, but I am not sure. Stefan?

Comment 4 Forgotten User ZhJd0F0L3x 2005-10-05 10:01:29 UTC

Assign it to the responsible hal-bug-fixer :-) We will fix it, so it is not WONTFIX

Comment 5 Holger Macht 2005-10-05 10:10:07 UTC

Therefore assigning to Danny...

Comment 6 Stefan Behlert 2005-10-05 13:41:23 UTC

If the problem exists in SL10.0 - and it seems to me it does - then we should 
even create a YOU.

Comment 7 Forgotten User ZhJd0F0L3x 2005-10-05 16:23:14 UTC

so what? 10.0 is long since fixed, but 10.1 isn't

Comment 8 Danny Al-Gaaf 2005-10-06 13:11:24 UTC

IMO ihis is a duplicate or effect of bug #117964. This is not fixed currently 
also if *somebody* closed the related bug. I had no time last week to release 
the you update. I plan this for next week. 

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