Re: Battery display generates ACPI events (stops X from powering off display)

Gautam Iyer <[email protected]>
Newsgroups gmane.comp.gnome.apps.gkrellm
Message-ID <[email protected]>
On Fri, Aug 03, 2007 at 09:57:54AM -0500, Bill WIlson wrote:

> > Aha. So doing this showed that gkrellm reads
> > 
> >     /proc/acpi/ac_adapter/AC0/state
> > 
> > Now just cat'ing that file generates the above ACPI event and cause X to
> > wake my monitor up from sleep.
> > 
> > Any idea what I can do about this? This certainly looks like a bug to
> > me. But I'm not sure where to report it. Linux kernel?
> > 
> > Also, as a work-around, is there some quick hack I can do to gkrellm to
> > avoid it reading that file? I'm getting quite tired of my scripts that
> > kill gkrellm after 10 mins of inactivity...
> 
> You can apply this patch to the setup_ac_adapter() function in
> src/sysdeps/linux.c to make gkrellm quit reading that file:

Thanks. This stops gkrellm from reading the offending file.

> The ac_adapter file has not always been available for some
> laptop/kernel versions, so gkrellm already tries as a backup to assume
> on line state from BAT0 file charging states when the ac_adapter file
> is missing.  So the battery monitor has a good chance of continuing to
> work fine for you

Almost :). The battery level is correct, but gkrellm now seems to think
that my system is always unplugged.

I can live with that though...

> It does seem like an acpi bug to me.  Maybe you could get some help
> from one of the acpi mailing lists at http://acpi.sourceforge.net.

Yep. I'll pester them. I notice that I have an option to not compile
ac_adapter support in my kernel. Maybe I should just do this instead of
patching gkrellm. Other programs (e.g. hald) do the same to my system...

Thanks

GI

-- 
'MCSE' -- Minesweeper Consultant & Solitaire Expert
_______________________________________________
Gkrellm mailing list
[email protected]
http://lists.jutley.org/cgi-bin/mailman/listinfo/gkrellm
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.