Piotr wrote: >> dbus-monitor --system >> >> and switch mouse on/off to reconnect. Tell us what you see. > > I see the change was logged when I connected BT mouse (see > dbus-monitor.log) > > >> If mouse is >> correctly discovered and selected by BT you have to look at higher level >> - the X system. >> First check if you have events captured by X perhaps with >> >> xev > > xev gives me nothing when I use the BT mouse. > > What next?
Excellent work Piotr. You see all works fine until systemd gets in the game. As I refused to use systemd I can't help much, but this needs to be investigated > path=/org/freedesktop/systemd1/unit/sys_2ddevices_2dpci0000_3a00_2d0000_3a00_3a1d_2e0_2dusb2_2d2_5cx2d1_2d2_5cx2d1_3a1_2e0_2dbluetooth_2dhci0_2dhci0_3a9_2edevice; > interface=org.freedesktop.DBus.Properties; member=PropertiesChanged string > "org.freedesktop.systemd1.Unit" array [ > dict entry( > string "ActiveState" > variant string "inactive" > ) > dict entry( > string "SubState" > variant string "dead" > ) Here you see sender=:1.0 -> destination=(null destination) signal time=1527752498.410215 sender=:1.0 -> destination=(null destination) serial=4147 path=/org/freedesktop/systemd1; interface=org.freedesktop.systemd1.Manager; member=UnitRemoved Can you try booting without systemd ? You need sysvinit and add init=/lib/sysvinit/init to your kernal command line. When system is up check ps -A | head -3 PID TTY TIME CMD 1 ? 00:00:33 init 2 ? 00:00:01 kthreadd Otherwise you should look for why systemd is not doing this right. regards