yet another report, for the Performance MX mouse in this case in bug
2025980 (leading to confusion which device is truly low in battery, so
there is an impact beyond cosmetics)

** Summary changed:

- Logitech MX Master 3 and 2s are detected as keyboard in gnome-power-statistics
+ A number of Logitech MX mice are detected as keyboards in 
gnome-power-statistics

** Summary changed:

- A number of Logitech MX mice are detected as keyboards in 
gnome-power-statistics
+ A number of Logitech MX mice are detected as keyboards in 
gnome-power-statistics and "upower -d"

** Summary changed:

- A number of Logitech MX mice are detected as keyboards in 
gnome-power-statistics and "upower -d"
+ A number of Logitech MX mice are incorrectly detected as keyboards in 
gnome-power-statistics and "upower -d"

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/2045737

Title:
  A number of Logitech MX mice are incorrectly detected as keyboards in
  gnome-power-statistics and "upower -d"

Status in Upower:
  New
Status in upower package in Ubuntu:
  Confirmed

Bug description:
  My Logitech MX Master 3 is detected as a keyboard in Power Statistics,
  it's not a critical issue as beyond this everything works fine.

  I'm using the Logitech Unifying Receiver to connect my MX Keys
  Keyboard and MX Master 3 Mouse, those are working fine but sometimes I
  get the notification of low battery, but I'm not so sure what is the
  device as it says Keyboard and the mouse is identified by Power
  Statistics as a Keyboard.

  This is the info from Power Statistics window:

  Device: battery_hidpp_battery_o
  Type: Leyboard
  Model: Wireless Mouse MX Master 3
  Serial number: bc-83-96-ed
  Supply: No
  Refreshed: 0 seconds
  Present: Yes
  Rechargable: Yes
  State: Discharging
  Percentage: 50.0%

  
  This is the info related to the Dongle from lsusb:

  ```
  Bus 003 Device 012: ID 046d:c52b Logitech, Inc. Unifying Receiver
  ```

  lshw information:

  ```
    *-input:12
         product: Logitech MX Keys
         physical id: e
         logical name: input33
         logical name: /dev/input/event6
         logical name: input33::capslock
         logical name: input33::compose
         logical name: input33::kana
         logical name: input33::numlock
         logical name: input33::scrolllock
         logical name: /dev/input/mouse2
         capabilities: usb
    *-input:13
         product: Logitech MX Master 3
         physical id: f
         logical name: input34
         logical name: /dev/input/event7
         logical name: input34::capslock
         logical name: input34::compose
         logical name: input34::kana
         logical name: input34::numlock
         logical name: input34::scrolllock
         logical name: /dev/input/mouse3
         capabilities: usb
  ```

  From the information above, this could be related to another package
  (even the kernel?) and not specifically gnome-power-manager

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-power-manager 43.0-1
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec  6 08:33:41 2023
  ExecutablePath: /usr/bin/gnome-power-statistics
  InstallationDate: Installed on 2023-05-04 (215 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=<set>
  SourcePackage: gnome-power-manager
  UpgradeStatus: Upgraded to mantic on 2023-11-03 (33 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/upower/+bug/2045737/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to