Closed mike-lloyd03 closed 2 months ago
Hi @mike-lloyd03
One thing I noticed is that libinput seems to think I have a bluetooth keyboard connected (M720 Triathalon Keyboard) but I only have a bluetooth mouse connected.
M720 Triathalon Keyboard
?I only have a Bluetooth mouse connected. I have never connected a Bluetooth keyboard. I'm expecting the built in keyboard (this is a laptop) to be recognized. I see three "Razer Razer Blade" devices in the devices list, two of which have keyboard capability.
If you know the keyboard device name and listed in libinput list-devices, please try the following configuration.
https://github.com/iberianpig/fusuma-plugin-sendkey#specify-keyboard-by-device-name
plugin: executors: sendkey_executor: device_name: 'YOUR KEYBOARD NAME'
That seems to be working for now. I'll follow up if things change. Sorry I missed this in the readme.
Thanks so much.
So I'm still having issues with Fusuma after waking from sleep. The daemon is still running but it's not detecting any inputs. I think the issue might be related to having multiple devices with the same name. libinput
shows three devices named 'Razer Razer Blade'. Can I specify the device by another identifier? /dev/input/event15
is the device location for my keyboard.
You're right, it might be difficult to identify if there are multiple devices with the same name. However, the device ID may change at startup, so it shouldn't depend on device ID.
For now, I'll try to reproduce the problem and determine a solution with test code.
Sounds good. Thank you.
It seems that installing the fusuma-plugin-remap may help resolve this issue by automatically creating a virtual device. You can find more information here: https://github.com/iberianpig/fusuma-plugin-remap.
If you continue to experience problems, please let us know.
I've been using fusuma for a few months now with no issues. But about a week ago, I had a crash related to
baloo_file_extractor
and ever since then, fusuma has been hit or miss. I normally have it start on login with an autostart script. But sometimes it just doesn't work. Running fusuma manually at the command line returns:After doing a three finger swipe I get:
and the program terminates.
Other times, however, fusuma seems to run normally and I can't quite figure out what the cause is. In fact, I just tried it again right now and it works. But other times, I get nothing.
One thing I noticed is that
libinput
seems to think I have a bluetooth keyboard connected (M720 Triathalon Keyboard) but I only have a bluetooth mouse connected.