Bug 808237

Description of problem:
A couple of days ago I updated the kernel of my HTPC (nVidia ION) to the 3.3.0-4 release. This kernel comes with amongst many things one particular new feature: the capability of reading the battery of my Logitech MediaBoard Pro bluetooth keyboard (Whoohoow!)
Now I am genuinely happy with this new feature, as I always had to guess the battery level of this device. However it has a serious side-effect.
The battery is registered, as per standard, in /sys/class/battery/hid-MAC_ADDR-... Gnome picks up this battery and shows it in the shell. When I then turn off the keyboard, it either reads 0 or disappears from the system interface (didn't verify), making Gnome think it has reached a critical level. The actions available for Gnome to execute when reaching such a level are either suspend or power off (why is there no "do nothing" option in the menu?! It's Linux!). Result: as soon as I turn off the external keyboard, Gnome suspends.

Version-Release number of selected component (if applicable):
kernel-3.3.0-4.fc16.x86_64
gnome-shell-3.2.2.1-1.fc16.x86_64

How reproducible:
Log in to Gnome using your bluetooth keyboard with battery reporting. Then turn it off (and perhaps on again).

Steps to Reproduce:
1. Boot 3.3 kernel
2. Turn on Logitech MediaBoard Pro
3. log in to the system in Gnome
4. Turn keyboard off
  
Actual results:
A system going into suspend or shutting down, depending on the settings, unable to get it out as the bluetooth keyboard is not working when suspended

Expected results:
A system that lives happily ever after

Additional info:
If the problem seems difficult to fix, I would be satisfied with having the "no action" option in the dropdown list in power settings -> when battery level critical. This at least works around the major issue while you have time to come up with a more sustainable solution. :-)