<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-5" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
bump.<br>
any news on this?<br>
I'm having the same issue in Om2009<br>
<br>
Paul Fertser wrote:
<blockquote cite="mid:m263fhmxep.fsf@home.pavel.comp" type="cite">
<pre wrap="">Robin Paulson <a class="moz-txt-link-rfc2396E" href="mailto:robin.paulson@gmail.com"><robin.paulson@gmail.com></a> writes:
</pre>
<blockquote type="cite">
<pre wrap="">2009/5/26 Thomas White <a class="moz-txt-link-rfc2396E" href="mailto:taw@bitwiz.org.uk"><taw@bitwiz.org.uk></a>:
</pre>
<blockquote type="cite">
<pre wrap="">I found that as well. Is anyone able to comment on what HAL is being used for
in SHR-Unstable? If it's simply been pulled in as a dependency (e.g. for
X.org) and isn't actively being used (e.g. by X.org for input management),
then it can be removed without breaking anything, which makes the problem go
away.
</pre>
</blockquote>
<pre wrap="">hal appears to be a dependency of xserver-kdrive-fbdev and
xserver-security-policy; is it actually critical for these packages,
or is thomas' assessment correct?
i'm getting the same problem of reported charge
</pre>
</blockquote>
<pre wrap=""><!---->
This is a problem that needs to be fixed. For the time being it can be
easily workarounded by using "internal" method for the battery applet,
but a proper long-term solution is yet to be found.
For that one needs to contact HAL guys and ask them about how exactly
they recommend to use their battery-monitoring interfaces, both from
upper level (how an application should deal with current situation
where we have 1 apm emulation for the battery, one usb power supply
(that according to the hal sources is also considered a battery) and
one "real" battery) and a lower layer (that "real" battery monitoring
doesn't work because E's battery gadget assumes the presence of some
sysfs properties that our driver lacks, OTOH i couldn't find any
document describing which sysfs nodes really must be present to be
compliant and which are optional).
</pre>
</blockquote>
</body>
</html>