Bug 138294

This works fine for me. What events are you getting on plug/unplug?

I just tested it by running acpi_listen.

I get no events at all with AC adapter jack/unjack.

I do get battery install events, but not battery remove events.

I do get lid-switch events (both lid down, and lid up).  It doesn't
say which _way_ the lid went, though.

This is on a Fujitsu P2120 laptop with ACPI.

$ acpi_listen
ac_adapter AC 00000080 00000000
battery BAT0 00000080 00000001
battery BAT0 00000080 00000001
ac_adapter AC 00000080 00000001
battery BAT0 00000080 00000001
battery BAT0 00000080 00000001

I'm getting the events. Assigning to kernel, looks like kernel/bios
interactions.

This problem has carried into FC3 final. I get this problem as well,
but when I remove the power cord, I get battery install events

battery BAT0 00000080 00000001

as well as some cpu throttling events. Putting the cord back gives me
the same event. Interesting thing to note: If I remove the widget from
the panel (right-click, remove from panel) then add it back to the
panel, the widget shows the correct state (AC or Battery). /proc AC
state shows the proper status. 

I've noticed the same problem with FC2 (I'm currently at
2.6.9-1.9_FC2/i686) on an IBM ThinkPad A22p laptop.  The battery
events are being logged to /var/log/acpid and indicate that the
battery monitor applet is being notified (notifying client
3141[1000:500]; 3141 is the pid of /usr/libexec/battstat-applet-2).

This happens to me too with FC4 (2.10.1)

here's my acpi_listen output

*unplug*
battery BAT1 00000080 00000001
processor CPU0 00000080 00000001
*plug*
battery BAT1 00000080 00000001
processor CPU0 00000080 00000000
battery BAT1 00000081 00000001
battery BAT1 00000080 00000001

cat /proc/acpi/ac_adapter/ACAD/state returns the correct value (on-line/off-line) 
as does cat /proc/acpi/battery/BAT1/state


I have a compaq R3000 laptop

This feature worked correctly for me on Ubuntu 5.04

An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which
may contain a fix for your problem.   Please update to this new kernel, and
report whether or not it fixes your problem.

If you have updated to Fedora Core 4 since this bug was opened, and the problem
still occurs with the latest updates for that release, please change the version
field of this bug to 'fc4'.

Thank you.

Still occurs for me on FC4, kernel 2.6.12-1.1398_FC4

and i tried to change the version field but could not

Ok, I've seen this happen myself too now. As the kernel is reporting the right
things to userspace, this must be a bug in the gnome-applet not realising the
state change.

I've seen it do really bizarre things, where the state is inverted and thinks
its on battery, and survives at 0% for hours (basically until I turn it off).

Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.

Thank you!

The information we've requested above is required in order
to review this problem report further and diagnose/fix the
issue if it is still present.  Since there haven't been any
updates to the report in quite a long time now after we've
requested additional information, we're assuming the problem
is either no longer present in our current OS release, or
that there is no longer any interest in tracking the problem.

Setting status to CANTFIX, however if you still
experience this problem after updating to our latest Fedora
Core release and are still interested in Red Hat tracking
the issue, and assisting in troubleshooting the problem,
please feel free to provide the information requested above,
and reopen the report.

Thank you in advance.

(this message is mass message)