You are not logged in.

Pages: 1

#1 2024-06-01 05:26:50

wonderfox
Member
Registered: 2024-01-13
Posts: 9

a bluetooth keyboard won't connect

I was trying to connect my bluetooth keyboard with blueman and it says "input-output error". sometimes I get the message that its been connected but it won't type. pairing was successful but nothing beyond it works
I'm sorry for the missing logs, I just don't know where I can find them
help me please

(it worked on other distributions so the problem is not the keyboard)

Offline

#2 2024-06-01 06:53:37

aljustiet
Member
Registered: 2024-02-09
Posts: 89
Website

Re: a bluetooth keyboard won't connect

wonderfox wrote:

I was trying to connect my bluetooth keyboard with blueman and it says "input-output error". sometimes I get the message that its been connected but it won't type. pairing was successful but nothing beyond it works
I'm sorry for the missing logs, I just don't know where I can find them
help me please

(it worked on other distributions so the problem is not the keyboard)

Try to run evtest, and see whether your keyboard is detected or not.

Offline

#3 2024-06-01 10:03:10

wonderfox
Member
Registered: 2024-01-13
Posts: 9

Re: a bluetooth keyboard won't connect

aljustiet wrote:

Try to run evtest, and see whether your keyboard is detected or not.

I tried to and it didn't detect it. That's the out4ut:

No device specified, trying to scan all of /dev/input/event*
Not running as root, no devices may be available.
Available devices:
Select the device event number [0-0]:

Last edited by wonderfox (2024-06-02 08:15:07)

Offline

#4 2024-06-01 15:31:44

aljustiet
Member
Registered: 2024-02-09
Posts: 89
Website

Re: a bluetooth keyboard won't connect

wonderfox wrote:
aljustiet wrote:

Try to run evtest, and see whether your keyboard is detected or not.

I tried to and it didn't detect it. That's the out4ut:
```
No device specified, trying to scan all of /dev/input/event*
Not running as root, no devices may be available.
Available devices:
Select the device event number [0-0]:
```

It says that you're not running it as root, then try run it as root. (doas/sudo ...)

Offline

#5 2024-06-02 05:42:13

wonderfox
Member
Registered: 2024-01-13
Posts: 9

Re: a bluetooth keyboard won't connect

aljustiet wrote:

It says that you're not running it as root

oh I misread it as one shouldn't run it as root

No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:      Lid Switch
/dev/input/event1:      Sleep Button
/dev/input/event10:     Asus WMI hotkeys
/dev/input/event11:     ETPS/2 Elantech Touchpad
/dev/input/event12:     Video Bus
/dev/input/event13:     Video Bus
/dev/input/event14:     HDA Intel PCH Mic
/dev/input/event15:     HDA Intel PCH Headphone
/dev/input/event16:     HDA Intel PCH HDMI/DP,pcm=3
/dev/input/event2:      Power Button
/dev/input/event3:      AT Translated Set 2 keyboard
/dev/input/event4:      USB Receiver USB Receiver
/dev/input/event5:      SONiX USB Keyboard
/dev/input/event6:      SONiX USB Keyboard Consumer Control
/dev/input/event7:      SONiX USB Keyboard System Control
/dev/input/event8:      Asus Wireless Radio Control
/dev/input/event9:      PC Speaker

AT Translated Set 2 keyboard - is it this one?

Last edited by wonderfox (2024-06-02 08:14:46)

Offline

#6 2024-06-02 05:49:19

wonderfox
Member
Registered: 2024-01-13
Posts: 9

Re: a bluetooth keyboard won't connect

this time it showed the following notification:
Failed to reach blueman-manager
It seems like blueman-manager could no get activated via D-Bus. A typical cause for this is a broken graphical setup in the D-Bus activation environment that can get resolved with a call to dbus-update-activation-environment. typically issued from xinitrc (respectively the Sway config or similar).

I don't run Sway, I run Mate
I tried running `dbus-update-activation-environment`, the command was not found

Offline

#7 2024-06-02 07:19:17

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 75,979

Re: a bluetooth keyboard won't connect

Please use [code][/code] tags, bbs predates mardown by approximately your lifetime. Edit your post in this regard.

Then please post your complete system journal for the boot: 

sudo journalctl -b | curl -F 'file=@-' 0x0.st

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#8 2024-06-02 08:17:04

wonderfox
Member
Registered: 2024-01-13
Posts: 9

Re: a bluetooth keyboard won't connect

seth wrote:

Edit your post in this regard.

done

seth wrote:

Then please post your complete system journal for the boot:

here it is: http://0x0.st/Xqi2.txt

Offline

#9 2024-06-02 13:35:13

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 75,979

Re: a bluetooth keyboard won't connect

Jun 02 08:37:46 archangel blueman-manager[23005]: Traceback (most recent call last):
Jun 02 08:37:46 archangel blueman-manager[23005]:   File "/usr/lib/python3.12/site-packages/blueman/main/Manager.py", line 149, in on_dbus_name_appeared
Jun 02 08:37:46 archangel blueman-manager[23005]:     bt_status_action.change_state(GLib.Variant.new_boolean(self.Applet.GetBluetoothStatus()))
Jun 02 08:37:46 archangel blueman-manager[23005]:                                                            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Jun 02 08:37:46 archangel blueman-manager[23005]:   File "/usr/lib/python3.12/site-packages/gi/overrides/Gio.py", line 349, in __call__
Jun 02 08:37:46 archangel blueman-manager[23005]:     result = self.dbus_proxy.call_sync(self.method_name, arg_variant,
Jun 02 08:37:46 archangel blueman-manager[23005]:              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Jun 02 08:37:46 archangel blueman-manager[23005]: gi.repository.GLib.GError: g-io-error-quark: Timeout was reached (24)

And 

Jun 02 08:39:10 archangel blueman-manager[23005]: blueman-manager 08.39.10 WARNING  ManagerDeviceList:421 _monitor_power_levels: Failed to get power levels, probably a LE device.
Jun 02 08:39:16 archangel bluetoothd[504]: profiles/input/device.c:hidp_add_connection() Rejected connection from !bonded device /org/bluez/hci0/dev_54_46_6B_46_82_3B

1. don't use blueman for the moment, disable the service and reboot.
Then try https://wiki.archlinux.org/title/Bluetooth#Pairing w/ bluetoothctl only, specifically https://wiki.archlinux.org/title/Blueto … up_in_scan because of the suggesting warning.

2. There seeems to be an unused wlan chip, what if you rfkill that?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#10 2024-06-02 14:56:08

wonderfox
Member
Registered: 2024-01-13
Posts: 9

Re: a bluetooth keyboard won't connect

so, I succeeded in pairing and connecting it

[CHG] Device 54:46:6B:46:82:3B Connected: yes
[CHG] Device 54:46:6B:46:82:3B Connected: no

I immediately thought it was the keyboard, and then I connected it:

Attempting to connect to 54:46:6B:46:82:3B
[CHG] Device 54:46:6B:46:82:3B Connected: yes
[Bluetooth 3.0 Keyboard]# [CHG] Device 54:46:6B:46:82:3B Paired: yes
[Bluetooth 3.0 Keyboard]# Connection successful
[Bluetooth 3.0 Keyboard]# [CHG] Device 54:46:6B:46:82:3B ServicesResolved: yes

but then I couldn't type on it. the key pressing did nothing

I didn't have to do stuff from the second link because it showed up in the first link try and also it said 

Failed to disable unit: Unit file blueman.service does not exist.

so I just killed -9 blueman

Offline

#11 2024-06-02 16:55:51

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 75,979

Re: a bluetooth keyboard won't connect

Does the keyboard show up in either
1. xinput
2. sudo libinput list-devices | grep Device:
after connecting it?

Edit:

AT Translated Set 2 keyboard - is it this one?

Probably not, what vendor/model is this?
Also you can compare the outputs pre/post connecting the keyboard.

Edit #2: and pelase post the journal after connecting the keyboard.

Last edited by seth (2024-06-02 16:57:55)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#12 2024-06-03 09:16:18

aljustiet
Member
Registered: 2024-02-09
Posts: 89
Website

Re: a bluetooth keyboard won't connect

wonderfox wrote:
aljustiet wrote:

It says that you're not running it as root

oh I misread it as one shouldn't run it as root

No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:      Lid Switch
/dev/input/event1:      Sleep Button
/dev/input/event10:     Asus WMI hotkeys
/dev/input/event11:     ETPS/2 Elantech Touchpad
/dev/input/event12:     Video Bus
/dev/input/event13:     Video Bus
/dev/input/event14:     HDA Intel PCH Mic
/dev/input/event15:     HDA Intel PCH Headphone
/dev/input/event16:     HDA Intel PCH HDMI/DP,pcm=3
/dev/input/event2:      Power Button
/dev/input/event3:      AT Translated Set 2 keyboard
/dev/input/event4:      USB Receiver USB Receiver
/dev/input/event5:      SONiX USB Keyboard
/dev/input/event6:      SONiX USB Keyboard Consumer Control
/dev/input/event7:      SONiX USB Keyboard System Control
/dev/input/event8:      Asus Wireless Radio Control
/dev/input/event9:      PC Speaker

AT Translated Set 2 keyboard - is it this one?

I think it's the SONiX USB Keyboard.

Offline

#13 2024-06-05 16:35:54

wonderfox
Member
Registered: 2024-01-13
Posts: 9

Re: a bluetooth keyboard won't connect

seth wrote:

Does the keyboard show up in either
1. xinput
2. sudo libinput list-devices | grep Device:
after connecting it?

it shows up in neither

seth wrote:

Edit #2: and pelase post the journal after connecting the keyboard.

here it is: http://0x0.st/XqdG.txt

Offline

#14 2024-06-05 16:36:56

wonderfox
Member
Registered: 2024-01-13
Posts: 9

Re: a bluetooth keyboard won't connect

aljustiet wrote:

I think it's the SONiX USB Keyboard.

it's not, the keyboard in question does not connect by USB and this one showed up in xinput before connecting the bluetooth one

Offline

#15 2024-06-05 17:00:28

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 75,979

Re: a bluetooth keyboard won't connect

Jun 05 19:30:02 archangel blueman-manager[13163]: blueman-manager 19.30.02 WARNING  ManagerDeviceList:421 _monitor_power_levels: Failed to get power levels, probably a LE device.
Jun 05 19:30:30 archangel sudo[13605]: wonderfox : TTY=pts/1 ; PWD=/home/wonderfox/Videos/Детки из класса 402/Season 1 ; USER=root ; COMMAND=/usr/bin/libinput list-devices
Jun 05 19:30:30 archangel sudo[13605]: pam_unix(sudo:session): session opened for user root(uid=0) by wonderfox(uid=1000)
Jun 05 19:30:31 archangel sudo[13605]: pam_unix(sudo:session): session closed for user root
Jun 05 19:30:51 archangel rtkit-daemon[694]: Supervising 6 threads of 4 processes of 1 users.
Jun 05 19:30:51 archangel rtkit-daemon[694]: Supervising 6 threads of 4 processes of 1 users.
Jun 05 19:31:28 archangel bluetoothd[591]: profiles/input/device.c:control_connect_cb() connect to 54:46:6B:46:82:3B: Host is down (112)
Jun 05 19:31:28 archangel blueman-manager[13163]: blueman-manager 19.31.28 WARNING  ManagerDeviceMenu:145 fail      : fail g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.Failed: blueman.bluez.errors.DBusFailedError:  br-connection-create-socket
Jun 05 19:31:28 archangel blueman-manager[13163]:  (0)
Jun 05 19:31:28 archangel blueman-manager[13163]: blueman-manager 19.31.28 WARNING  ManagerDeviceMenu:197 _handle_error_message: bluetoothd reported input/output error. Check its logs for context.
Jun 05 19:31:28 archangel blueman-manager[13163]: blueman-manager 19.31.28 WARNING  ManagerDeviceList:421 _monitor_power_levels: Failed to get power levels, probably a LE device.
Jun 05 19:31:28 archangel systemd[658]: Started dbus-:1.5-org.freedesktop.Notifications@69.service.
Jun 05 19:31:53 archangel bluetoothd[591]: profiles/input/device.c:hidp_add_connection() Rejected connection from !bonded device /org/bluez/hci0/dev_54_46_6B_46_82_3B
Jun 05 19:32:13 archangel sudo[13681]: wonderfox : TTY=pts/1 ; PWD=/home/wonderfox ; USER=root ; COMMAND=/usr/bin/libinput list-devices
Jun 05 19:32:13 archangel sudo[13681]: pam_unix(sudo:session): session opened for user root(uid=0) by wonderfox(uid=1000)
Jun 05 19:32:13 archangel sudo[13681]: pam_unix(sudo:session): session closed for user root
Jun 05 19:32:18 archangel rtkit-daemon[694]: Supervising 6 threads of 4 processes of 1 users.
Jun 05 19:32:18 archangel rtkit-daemon[694]: Supervising 6 threads of 4 processes of 1 users.
Jun 05 19:32:18 archangel rtkit-daemon[694]: Successfully made thread 13695 of process 10889 owned by '1000' RT at priority 10.
Jun 05 19:32:18 archangel rtkit-daemon[694]: Supervising 7 threads of 5 processes of 1 users.
Jun 05 19:32:22 archangel bluetoothd[591]: profiles/input/device.c:control_connect_cb() connect to 54:46:6B:46:82:3B: Host is down (112)
Jun 05 19:32:22 archangel blueman-manager[13163]: blueman-manager 19.32.22 WARNING  ManagerDeviceMenu:145 fail      : fail g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.Failed: blueman.bluez.errors.DBusFailedError:  br-connection-create-socket
Jun 05 19:32:22 archangel blueman-manager[13163]:  (0)
Jun 05 19:32:22 archangel blueman-manager[13163]: blueman-manager 19.32.22 WARNING  ManagerDeviceMenu:197 _handle_error_message: bluetoothd reported input/output error. Check its logs for context.
Jun 05 19:32:32 archangel bluetoothd[591]: profiles/input/device.c:control_connect_cb() connect to 54:46:6B:46:82:3B: Host is down (112)
Jun 05 19:32:32 archangel blueman-manager[13163]: blueman-manager 19.32.32 WARNING  ManagerDeviceMenu:145 fail      : fail g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.Failed: blueman.bluez.errors.DBusFailedError:  br-connection-create-socket
Jun 05 19:32:32 archangel blueman-manager[13163]:  (0)
Jun 05 19:32:32 archangel blueman-manager[13163]: blueman-manager 19.32.32 WARNING  ManagerDeviceMenu:197 _handle_error_message: bluetoothd reported input/output error. Check its logs for context.
Jun 05 19:32:40 archangel bluetoothd[591]: profiles/input/device.c:control_connect_cb() connect to 54:46:6B:46:82:3B: Host is down (112)
Jun 05 19:32:40 archangel blueman-manager[13163]: blueman-manager 19.32.40 WARNING  ManagerDeviceMenu:145 fail      : fail g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.Failed: blueman.bluez.errors.DBusFailedError:  br-connection-create-socket
Jun 05 19:32:40 archangel blueman-manager[13163]:  (0)
Jun 05 19:32:40 archangel blueman-manager[13163]: blueman-manager 19.32.40 WARNING  ManagerDeviceMenu:197 _handle_error_message: bluetoothd reported input/output error. Check its logs for context.
Jun 05 19:32:48 archangel bluetoothd[591]: profiles/input/device.c:control_connect_cb() connect to 54:46:6B:46:82:3B: Host is down (112)
Jun 05 19:32:48 archangel blueman-manager[13163]: blueman-manager 19.32.48 WARNING  ManagerDeviceMenu:145 fail      : fail g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.Failed: blueman.bluez.errors.DBusFailedError:  br-connection-create-socket
Jun 05 19:32:48 archangel blueman-manager[13163]:  (0)
Jun 05 19:32:48 archangel blueman-manager[13163]: blueman-manager 19.32.48 WARNING  ManagerDeviceMenu:197 _handle_error_message: bluetoothd reported input/output error. Check its logs for context.
Jun 05 19:32:50 archangel systemd[658]: Started dbus-:1.5-org.freedesktop.Notifications@70.service.
Jun 05 19:32:50 archangel blueman-manager[13163]: blueman-manager 19.32.50 WARNING  ManagerDeviceList:421 _monitor_power_levels: Failed to get power levels, probably a LE device.
seth wrote:

1. don't use blueman for the moment, disable the service and reboot.

https://stackoverflow.com/questions/706 … uetoothctl
https://bbs.archlinux.org/viewtopic.php?id=278996

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

Pages: 1

Board footer

Powered by FluxBB