No power indicator for Logitech MX Anywhere 2 wireless mouse

[rjb]

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu
Description: Ubuntu 16.04.2 LTS
Release: 16.04

2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center
gnome-power-manager:
  Installiert: 3.18.0-1ubuntu1
  Installationskandidat: 3.18.0-1ubuntu1
  Versionstabelle:
 *** 3.18.0-1ubuntu1 500
        500 http://ch.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
        100 /var/lib/dpkg/status

3) What you expected to happen
I would expect to have a battery symbol in the top right corner for the mouse as well as battery statistics as for internal laptop battery or previous Logitech MX Anywhere mouse.

4) What happened instead
No battery shown and statistics window only showing internal laptop battery.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gnome-power-manager 3.18.0-1ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-41-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Mar 15 19:44:21 2017
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-power-statistics
InstallationDate: Installed on 2016-05-15 (303 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: gnome-power-manager
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

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

[Sebastien Bacher (seb128)]

Thank you for your bug report. Could you add the output of the 'upower --dump' command with your mouse connected?

[rjb (ron-buehler)]

Hi Sebastien

Meanwhile I use 18.04 LTS where the problem is solved.
Therefore I have no possibility to provide you with this information.
However, I see that somebody else is affected by the same bug - possibly that person can provide the required information.

[Sebastien Bacher (seb128)]

Thanks for the reply, it's probably one of the issues fixed with newer kernel/upower versions, if it's working in the current LTS then let's close the bug, we don't plan to SRU those improvements to xenial at this point