| Summary: | Wireless mouse cut sleep mode while moved or turned off | ||
|---|---|---|---|
| Product: | [Unmaintained] Bluedevil | Reporter: | Aldux <aldosantarelli> |
| Component: | daemon | Assignee: | David Rosca <nowrep> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | CC: | alade1518, me, plasma-bugs-null |
| Priority: | NOR | ||
| Version First Reported In: | 5.16.5 | ||
| Target Milestone: | --- | ||
| Platform: | Kubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Aldux
2020-07-14 21:56:56 UTC
Logitech M185 is a wireless mouse indeed, but I checked its produce page and it nowhere mentions the Bluetooth; it seems like it only supports a USB transceiver: https://wwwtest.logitech.com/en-us/products/mice/m185-wireless-mouse.910-002225.html > Connectivity > > Connection Type: 2.4 GHz wireless connection > Wireless range: 33 ft (10 m) > Connect / Power: Yes, on/off switch So, this bug report has nothing to do with Linux Bluetooth stack in general or Plasma/Bluedevil in particular. Devices connected via USB are generally allowed to wake the system up from sleep, unless you override that with some kernel parameters or by writing in /sys/class/something. I bet you'd still want the mouse to be able to wake your system up when you actually move or click it though. Waking up on disconnect sounds like a device issue, and only Lenovo could possibly fix that with an update to their transceiver's firmware (spoiler alert: they probably wouldn't care). In general, there are no strict rules which types of events should emit a "wake up" signal on USB bus, so all vendors and models of mice implement it in slightly different ways; it's just inconsistent and cursed. |