Ubuntu 14.10 sees logitech k810 bluetooth keyboard battery as a system/laptop battery

[Rob Watts]

This is a HP desktop computer using a IOGEAR USB Bluetooth dongle. When I enable the logitech k810 keyboard the OS behaves like it's on battery power.

Inside the power management GUI under "Power Settings" the "What to do when power is critically low" selection is set to Power Off, and I can't select another option.

Here's the output of "upower -d"

rob@hp-ubuntu:~$ upower -d
Device: /org/freedesktop/UPower/devices/battery_hid_00o1fo20o92o1bo18_battery
  native-path: hid-00:1f:20:92:1b:18-battery
  model: Logitech K810
  power supply: no
  updated: Sun 25 Jan 2015 07:02:46 PM CST (5 seconds ago)
  has history: yes
  has statistics: yes
  battery
    present: yes
    rechargeable: yes
    state: discharging
    energy: 0 Wh
    energy-empty: 0 Wh
    energy-full: 0 Wh
    energy-full-design: 0 Wh
    energy-rate: 0 W
    percentage: 85%
    capacity: 100%

Daemon:
  daemon-version: 0.9.23
  can-suspend: yes
  can-hibernate: no
  on-battery: no
  on-low-battery: no
  lid-is-closed: no
  lid-is-present: no
  is-docked: no

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: upower 0.9.23-2ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
Uname: Linux 3.16.0-29-generic x86_64
ApportVersion: 2.14.7-0ubuntu8.1
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Jan 25 18:57:04 2015
InstallationDate: Installed on 2015-01-14 (11 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
SourcePackage: upower
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[scruss (scruss)]

Looks related to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1391555

A fresh reinstall of 14.10 brought this problem back for me; an effective hard lockout because the system interprets my Magic Mouse battery as the laptop's one …

[jonathan stivers (sarafan-redeemer)]

Is there any workaround for this issue? I am have the same outcome with the Logitech K810.