On 03/11/2021 15:02, Frederic Muller wrote:
On 11/3/21 13:28, Ed Greshko wrote:
On 03/11/2021 14:18, Frederic Muller wrote:
Hi!
A few days ago (maybe 5?) bluetooth got updated on F35 and since then my Logitech mouse doesn't work right out of the boot...meaning:
1. I start the machine, the BT interface tells me the mouse is connected, but neither the pointer nor the buttons work
2. I need to systematically disconnect + reconnect OR remove the device and add it back to make it work.
Other BT devices I use (a Logitech keyboard and a speaker) work normally.
I haven't file a bug yet but was wondering if anyone else had the issue and eventually some advice on the proper course of action from there.
My Logitech keyboard uses the Unified Receiver so I can't comment on your issue.
I would check the journal and compare the sequence of the initial failing connection and the successful connection later.
Ed
--
I forgot to add I use piper to configure my Logitech mouse which when the mouse seems connected (BT says so) but doesn't work, piper says there is no device, whereas when everything is working, piper do find the mouse.
The packages update was on 2021-10-31 and those were the packages:
bluez
bluez-cups
bluez-libs
bluez-obexd
Now journal says:
1. At boot time:
Nov 03 08:59:43 romeo kernel: input: MX Master 3 Keyboard as /devices/virtual/misc/uhid/0005:046D:B023.0002/input/input25
Nov 03 08:59:43 romeo kernel: input: MX Master 3 Mouse as /devices/virtual/misc/uhid/0005:046D:B023.0002/input/input26
Nov 03 08:59:43 romeo kernel: hid-generic 0005:046D:B023.0002: input,hidraw1: BLUETOOTH HID v0.15 Keyboard [MX Master 3] on 60:57:18:7e:78:85
Nov 03 08:59:43 romeo bluetoothd[834]: profiles/input/hog-lib.c:set_report_cb() Error setting Report value: Unexpected error code
Nov 03 08:59:43 romeo kernel: logitech-hidpp-device 0005:046D:B023.0002: Device not connected
Nov 03 08:59:43 romeo gnome-shell[1789]: Could not open device /dev/input/event18: Could not get device info for path /dev/input/event18: No such file or directory
Nov 03 08:59:43 romeo gnome-shell[1789]: Could not open device /dev/input/event19: Could not get device info for path /dev/input/event19: No such file or directory
2. When disconnecting and reconnecting (which sometimes doesn't work as well)
Nov 03 09:01:15 romeo bluetoothd[834]: src/device.c:load_gatt_db() No cache for FC:5E:D2:E1:3D:D8
Nov 03 09:01:18 romeo bluetoothd[834]: profiles/input/hog-lib.c:set_report_cb() Error setting Report value: Unexpected error code
Nov 03 09:01:18 romeo kernel: logitech-hidpp-device 0005:046D:B023.0003: Device not connected
Nov 03 09:01:27 romeo systemd[1]: libvirtd.service: Deactivated successfully.
Nov 03 09:01:27 romeo systemd[1]: libvirtd.service: Unit process 1833 (dnsmasq) remains running after unit stopped.
Nov 03 09:01:27 romeo systemd[1]: libvirtd.service: Unit process 1835 (dnsmasq) remains running after unit stopped.
Nov 03 09:01:27 romeo audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=libvirtd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 03 09:01:34 romeo kernel: logitech-hidpp-device 0005:046D:B023.0004: HID++ 4.5 device connected.
Nov 03 09:01:35 romeo upowerd[858]: treating change event as add on /sys/devices/virtual/misc/uhid/0005:046D:B023.0004/power_supply/hidpp_battery_0
Nov 03 09:01:35 romeo kernel: input: Logitech Wireless Mouse MX Master 3 as /devices/virtual/misc/uhid/0005:046D:B023.0004/input/input29
Nov 03 09:01:35 romeo kernel: logitech-hidpp-device 0005:046D:B023.0004: input,hidraw1: BLUETOOTH HID v0.15 Keyboard [Logitech Wireless Mouse MX Master 3] on 60:57:18:7e:78:85
Nov 03 09:01:35 romeo systemd-logind[999]: Watching system buttons on /dev/input/event19 (Logitech Wireless Mouse MX Master 3)
Nov 03 09:01:40 romeo systemd[2303]: app-gnome-gnome\x2dbluetooth\x2dpanel-3083.scope: Consumed 8.197s CPU time.
Is that helpful?
I have never used piper. Is there a reason you used it as opposed to the bluetooth tools?
As for your journal output. The boot time output doesn't reflect that the mouse is being detected. There is only info on the
keyboard.
I forgot that I do have a laptop and a Logitech BT mouse M557. The laptop is running F35 and there is no problem with
the connection at boot time. My journal reports.
Nov 03 15:21:55 acer.greshko.com systemd[1024]: Reached target Bluetooth.
Nov 03 15:21:55 acer.greshko.com kernel: Bluetooth: HIDP (Human Interface Emulatio
n) ver 1.2
Nov 03 15:21:55 acer.greshko.com kernel: Bluetooth: HIDP socket layer initialized
Nov 03 15:21:55 acer.greshko.com kernel: hid-generic 0005:046D:B010.0001: unknown
main item tag 0x0
Nov 03 15:21:55 acer.greshko.com kernel: input: Bluetooth Mouse M557 Mouse as /dev
ices/pci0000:00/0000:00:1d.2/usb7/7-1/7-1:1.0/bluetooth/hci0/hci0:11/0005:046D:B01
0.0001/input/input19
Nov 03 15:21:55 acer.greshko.com kernel: input: Bluetooth Mouse M557 Consumer Cont
rol as /devices/pci0000:00/0000:00:1d.2/usb7/7-1/7-1:1.0/bluetooth/hci0/hci0:11/00
05:046D:B010.0001/input/input20
Nov 03 15:21:55 acer.greshko.com kernel: input: Bluetooth Mouse M557 Keyboard as /
devices/pci0000:00/0000:00:1d.2/usb7/7-1/7-1:1.0/bluetooth/hci0/hci0:11/0005:046D:
B010.0001/input/input23
Nov 03 15:21:55 acer.greshko.com kernel: hid-generic 0005:046D:B010.0001: input,hi
draw0: BLUETOOTH HID v10.01 Mouse [Bluetooth Mouse M557] on 00:1d:d9:ef:d1:7b
When you reboot, and before you reconnect, what do you get when using
bluetoothctl and issue the devices, and paired-devices commands.
--
On Facebook it is called Vaguebooking.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
