Bug 352013

Summary:	gnome won't recognize my machine (MSI PR200) as a laptop
Product:	[openSUSE] openSUSE 10.3	Reporter:	Jan Matejek <jmatejek>
Component:	GNOME	Assignee:	Rodrigo Moya <rodrigo>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Major
Priority:	P5 - None	CC:	vuntz
Version:	Final
Target Milestone:	---
Hardware:	x86-64
OS:	openSUSE 10.3
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	lshal output

Description Jan Matejek 2008-01-07 14:35:56 UTC

the "battery" tab in power management settings is not present.
also the notification icon always shows the "power plug" icon. when on battery, the tooltip shows "running on battery" (at least some of the time) but the icon does not change.

power management is also missing from YaST

KPowersave works just fine. gnome-power-manager in ubuntu works just fine.
(except for various ACPI bugs that i'm reporting elsewhere)

Comment 1 JP Rosevear 2008-01-07 15:28:14 UTC

We're not really patching much in 10.3 for g-p-m in 2.20.0, perhaps ubuntu has 2.20.1 or something with some bug fixes from upstream.  Or possibly the properties g-p-m uses from hal are not working properly (not sure kpowersave uses hal directly atm).

Comment 2 Vincent Untz 2008-02-18 15:47:45 UTC

Can you run "lshal | grep battery" in a terminal and copy the output here?

Comment 3 Jan Matejek 2008-02-20 09:47:22 UTC

this command gives no output.

full output of lshal is attached.
I guess that this is related (if not duplicate) to #334005 - but as noted before, KDE's kpowersave works fine for me.

Comment 4 Jan Matejek 2008-02-20 09:48:02 UTC

Created attachment 195885 [details]
lshal output

Comment 5 Vincent Untz 2008-02-20 10:27:16 UTC

Indeed, looks like a duplicate of bug 334005, I'll close the bug as such. If you have time, please try what Alexey proposed in the bug.

I don't know kpowersave, so I don't know why it worked. Maybe it's using APM instead of ACPI, though.

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