Closed visualcortexlab closed 1 month ago
I expect that this is another aspect of the changes to bluez. What version of bluez are you running?
Try switching off your mouse and running ls -l /dev/hidraw*
. Then switch the mouse on and run ls again. If no new node shows up then the bluez you are running has special code to keep the node around, but Solaar does not receive any notification that the mouse has reconnected so it cannot reinitialize the mouse.
dpkg -l | grep bluez
ii bluez 5.77-1 amd64 Bluetooth tools and daemons ii bluez-firmware 1.2-9 all Firmware for Bluetooth devices ii bluez-obexd 5.77-1 amd64 bluez obex daemon rc libkf5bluezqt-data 5.115.0-2 all data files for bluez-qt
(before turning off the mouse) └─────────[08:12:33] --> ls -l /dev/hidraw* crw------- 1 root root 244, 0 Oct 11 16:38 /dev/hidraw0 crw------- 1 root root 244, 1 Oct 11 16:38 /dev/hidraw1 crw------- 1 root root 244, 2 Oct 11 16:38 /dev/hidraw2 crw------- 1 root root 244, 3 Oct 11 16:38 /dev/hidraw3 crw------- 1 root root 244, 4 Oct 11 16:38 /dev/hidraw4 crw-rw----+ 1 root root 244, 5 Oct 15 07:36 /dev/hidraw5 crw------- 1 root root 244, 6 Oct 15 08:31 /dev/hidraw6
(with mouse turned OFF) └─────────[09:08:29] --> ls -l /dev/hidraw* crw------- 1 root root 244, 0 Oct 11 16:38 /dev/hidraw0 crw------- 1 root root 244, 1 Oct 11 16:38 /dev/hidraw1 crw------- 1 root root 244, 2 Oct 11 16:38 /dev/hidraw2 crw------- 1 root root 244, 3 Oct 11 16:38 /dev/hidraw3 crw------- 1 root root 244, 4 Oct 11 16:38 /dev/hidraw4 crw------- 1 root root 244, 6 Oct 15 08:31 /dev/hidraw6
(with mouse turned back ON) └─────────[09:08:35] --> ls -l /dev/hidraw* crw------- 1 root root 244, 0 Oct 11 16:38 /dev/hidraw0 crw------- 1 root root 244, 1 Oct 11 16:38 /dev/hidraw1 crw------- 1 root root 244, 2 Oct 11 16:38 /dev/hidraw2 crw------- 1 root root 244, 3 Oct 11 16:38 /dev/hidraw3 crw------- 1 root root 244, 4 Oct 11 16:38 /dev/hidraw4 crw-rw----+ 1 root root 244, 5 Oct 15 09:08 /dev/hidraw5 crw------- 1 root root 244, 6 Oct 15 08:31 /dev/hidraw6
middle mouse config was lost, had to re launch Solaar a few times before the middle button option was showing up. after a few attempts I could re configure the middle button again.
some output from dmesg (whilst turning mouse OFF/ON - channel switch): [310902.184511] input: MX Anywhere 3S Mouse as /devices/virtual/misc/uhid/0005:046D:B037.0010/input/input48 [310902.184740] hid-generic 0005:046D:B037.0010: input,hidraw6: BLUETOOTH HID v0.03 Mouse [MX Anywhere 3S] on 4c:79:6e:dc:05:27 [311077.349941] input: MX Anywhere 3S Mouse as /devices/virtual/misc/uhid/0005:046D:B037.0011/input/input50 [311077.350251] hid-generic 0005:046D:B037.0011: input,hidraw5: BLUETOOTH HID v0.03 Mouse [MX Anywhere 3S] on 4c:79:6e:dc:05:27 [311112.957557] tun: Universal TUN/TAP device driver, 1.6 [313133.293347] input: MX Anywhere 3S Mouse as /devices/virtual/misc/uhid/0005:046D:B037.0012/input/input52 [313133.293556] hid-generic 0005:046D:B037.0012: input,hidraw5: BLUETOOTH HID v0.03 Mouse [MX Anywhere 3S] on 4c:79:6e:dc:05:27
[318636.215933] input: MX Anywhere 3S Mouse as /devices/virtual/misc/uhid/0005:046D:B037.0014/input/input55 [318636.216072] hid-generic 0005:046D:B037.0014: input,hidraw5: BLUETOOTH HID v0.03 Mouse [MX Anywhere 3S] on 4c:79:6e:dc:05:27 [318665.638979] input: MX Anywhere 3S Mouse as /devices/virtual/misc/uhid/0005:046D:B037.0015/input/input57 [318665.639104] hid-generic 0005:046D:B037.0015: input,hidraw5: BLUETOOTH HID v0.03 Mouse [MX Anywhere 3S] on 4c:79:6e:dc:05:27
btw, this seems to be the mouse node? crw-rw----+ 1 root root 244, 5 Oct 15 09:08 /dev/hidraw5
This doesn't look like the bluez problem.
Please quit out of Solaar and run as solaar -ddd
. It will produce a lot of debugging output. Post the output from just before the screensaver starts to a few seconds after coming back from the screensave.
Btw, I was just thinking, when I say "back from the screensaver" I meant "this morning when I got to my computer (and of course unlocked it from the screensaver), but I wonder whether the actual trigger is a "sleep mode" the Mouse could have, and have nothing to do with xscreensaver... I just tried, for example, running the screensaver ("Preview" from the xscreensaver UI) and the mouse works just fine when coming back from it.
The problem is most likely related to sleep/suspend. Post output of solaar -ddd
from before the suspend til the system is fully back. Manual triggering of suspend should work the same as suspend due to inactivity.
here's the output 10:38 was suspended
The mouse worked perfectly fine once back from Suspend.. so here's my question, does Solaar neds to be running in the background all the time? Cause the way I've been using it was:
1// launch 2// setup my middle mouse prefs 3// quit Solaar
with this test I ran just now solaar has been running all the time and mouse worked just fine (and middle button too).
Yes, Solaar needs to be running all the time, precisely so that it can re-apply settings when devices come back from power-saving modes. The devices do not save most of their settings in permanent storage so they lose changes when they power down.
Yes, Solaar needs to be running all the time, precisely so that it can re-apply settings when devices come back from power-saving modes. The devices do not save most of their settings in permanent storage so they lose changes when they power down.
ooooh.... than I'm sorry for initiating all this thread in first place and thank you so much for all your help. (and for this tool!!)
no Bug there then. thanks!
Information
solaar --version
orgit describe --tags
if cloned from this repository):uname -srmo
):KERNEL VERSION HERE
solaar show
:~/.config/solaar/config.yaml
(or~/.config/solaar/config.json
if~/.config/solaar/config.yaml
not present):The mouse is losing its configuration (or perhaps more correctly - not being reconfigured) when waking from the ScreenSaver Describe the bug A clear and concise description of what the bug is.
To Reproduce 1 // "wake up the computer" from the screen saver... the config is no longer active and Solaar UI is reduced to a few parameter (screenshot will come next time this happens as is now back to normal" Switching the mouse off and back on doesn't solve the issues, however..
To FIX the issues ... rotating the mouse channel from 1 back to 1 (then 2 , 3 and back to 1) seems to solve the UI problem and I can then re-setup the middle mouse button as per my preference.