So I got the next error while trying to restart blueman-manager (I had no problems yesterday with bluetooth)
blueman-manager
(blueman-manager:133443): Gtk-WARNING **: 10:54:48.897: Theme parsing error: gtk.css:73:10: 'overflow' is not a valid property name
(blueman-manager:133443): Gtk-WARNING **: 10:54:48.921: Theme parsing error: gtk.css:4091:13: negative values are not allowed.
(blueman-manager:133443): Gtk-WARNING **: 10:54:48.934: Theme parsing error: gtk.css:7855:13: negative values are not allowed.
(blueman-manager:133443): Gtk-WARNING **: 10:54:48.935: Theme parsing error: gtk.css:8039:19: negative values are not allowed.
(blueman-manager:133443): Gtk-WARNING **: 10:54:48.936: Theme parsing error: gtk.css:8317:21: negative values are not allowed.
(blueman-manager:133443): Gtk-WARNING **: 10:54:48.936: Theme parsing error: gtk.css:8318:24: negative values are not allowed.
blueman-manager 10.54.49 ERROR Manager:147 on_dbus_name_appeared: Default adapter not found, trying first available.
blueman-manager 10.54.49 ERROR Manager:151 on_dbus_name_appeared: No adapter(s) found, exiting
I tried to change to other theme as suggested on this solution: Theme parsing error: gtk.css:--after installing code-oss
And tried to restart blueman-manager, that’s when I got:
blueman-manager
(blueman-manager:115306): Gtk-WARNING **: 10:48:27.194: Theme parsing error: gtk.css:73:10: 'overflow' is not a valid property name
blueman-manager 10.48.27 ERROR Manager:147 on_dbus_name_appeared: Default adapter not found, trying first available.
blueman-manager 10.48.27 ERROR Manager:151 on_dbus_name_appeared: No adapter(s) found, exiting
Do you need any more information from my end? Please let me know
journalctl --boot 0 --dmesg --no-hostname --no-pager --grep "bluetooth"
See this:
So that leads me directly to this old bug: https://bugzilla.kernel.org/show_bug.cgi?id=215167
$ errno 110
ETIMEDOUT 110 Connection timed out
Basically, it means that the device is not fully initialized when the driver connects to it and the driver doesn’t wait long enough.
Maybe reloading the driver:
sudo systemctl stop bluetooth.service
sudo modprobe -rv btusb && sleep 10 && sudo modprobe -v btusb
sudo systemctl start bluetooth.service
Let a second terminal open and monitor dmesg:
sudo d…
Ok so this is the output of the commands you mentioned:
journalctl --boot 0 --dmesg --no-hostname --grep "bluetooth"
Jul 14 09:36:47 kernel: usb 2-7: Product: Bluetooth Radio
Jul 14 09:37:03 kernel: Bluetooth: Core ver 2.22
Jul 14 09:37:03 kernel: NET: Registered PF_BLUETOOTH protocol family
Jul 14 09:37:03 kernel: Bluetooth: HCI device and connection manager initialized
Jul 14 09:37:03 kernel: Bluetooth: HCI socket layer initialized
Jul 14 09:37:03 kernel: Bluetooth: L2CAP socket layer initialized
Jul 14 09:37:03 kernel: Bluetooth: SCO socket layer initialized
Jul 14 09:37:03 kernel: Bluetooth: hci0: RTL: examining hci_ver=06 hci_rev=000b lmp_ver=06 lmp_subver=8723
Jul 14 09:37:03 kernel: Bluetooth: hci0: RTL: rom_version status=0 version=1
Jul 14 09:37:03 kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8723b_fw.bin
Jul 14 09:37:03 kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8723b_config.bin
Jul 14 09:37:03 kernel: bluetooth hci0: Direct firmware load for rtl_bt/rtl8723b_config.bin failed with er>
lines 1-12
Let me check the solution to that old bug
The output of the second terminal is the following:
[ 7474.522848] [UFW BLOCK] IN=wlp2s0 OUT= MAC=01:00:5e:00:00:01:28:3a:4d:9b:13:46:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=0 PROTO=2
[ 7502.152965] usbcore: deregistering interface driver btusb
[ 7512.607204] usbcore: registered new interface driver btusb
[ 7512.829802] Bluetooth: hci0: RTL: examining hci_ver=06 hci_rev=000b lmp_ver=06 lmp_subver=8723
[ 7512.830789] Bluetooth: hci0: RTL: rom_version status=0 version=1
[ 7512.830793] Bluetooth: hci0: RTL: loading rtl_bt/rtl8723b_fw.bin
[ 7512.840508] Bluetooth: hci0: RTL: loading rtl_bt/rtl8723b_config.bin
[ 7512.840628] bluetooth hci0: Direct firmware load for rtl_bt/rtl8723b_config.bin failed with error -2
[ 7512.840645] Bluetooth: hci0: RTL: cfg_sz -2, total sz 22496
[ 7513.276813] Bluetooth: hci0: RTL: fw version 0x0e2f9f73
[ 7513.386322] Bluetooth: MGMT ver 1.22
[ 7513.419154] NET: Registered PF_ALG protocol family
[ 7513.548277] Bluetooth: RFCOMM TTY layer initialized
[ 7513.548292] Bluetooth: RFCOMM socket layer initialized
[ 7513.548297] Bluetooth: RFCOMM ver 1.11
[ 7600.477616] [UFW BLOCK] IN=wlp2s0 OUT= MAC=01:00:5e:00:00:01:28:3a:4d:9b:13:46:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=0 PROTO=2
[ 7648.315458] input: Bose SLIII (AVRCP) as /devices/virtual/input/input13
[ 7726.531669] [UFW BLOCK] IN=wlp2s0 OUT= MAC=01:00:5e:00:00:01:28:3a:4d:9b:13:46:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=0 PROTO=2
[ 7852.489637] [UFW BLOCK] IN=wlp2s0 OUT= MAC=01:00:5e:00:00:01:28:3a:4d:9b:13:46:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=0 PROTO=2
[ 7978.540534] [UFW BLOCK] IN=wlp2s0 OUT= MAC=01:00:5e:00:00:01:28:3a:4d:9b:13:46:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=0 PROTO=2
[ 8104.596414] [UFW BLOCK] IN=wlp2s0 OUT= MAC=01:00:5e:00:00:01:28:3a:4d:9b:13:46:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=0 PROTO=2
[ 8230.549554] [UFW BLOCK] IN=wlp2s0 OUT= MAC=01:00:5e:00:00:01:28:3a:4d:9b:13:46:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=0 PROTO=2
Yes, after trying to execute blueman-manager it actually did the work. However the error regarding GTK with the theme parsing persist (in my despair I went back to my previous theme), should I change it?
blueman-manager
(blueman-manager:227554): Gtk-WARNING **: 11:43:33.431: Theme parsing error: gtk.css:73:10: 'overflow' is not a valid property name
(blueman-manager:227554): Gtk-WARNING **: 11:43:33.454: Theme parsing error: gtk.css:4091:13: negative values are not allowed.
(blueman-manager:227554): Gtk-WARNING **: 11:43:33.472: Theme parsing error: gtk.css:7855:13: negative values are not allowed.
(blueman-manager:227554): Gtk-WARNING **: 11:43:33.472: Theme parsing error: gtk.css:8039:19: negative values are not allowed.
(blueman-manager:227554): Gtk-WARNING **: 11:43:33.473: Theme parsing error: gtk.css:8317:21: negative values are not allowed.
(blueman-manager:227554): Gtk-WARNING **: 11:43:33.473: Theme parsing error: gtk.css:8318:24: negative values are not allowed.
Otherwise, as you said, I think the solution was reloading the driver
system
17 July 2023 07:48
6
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.