[BUG] No Interactions on Ubuntu 21.10 #175
Comments
|
Hi @eiswind - thanks for the report - so you had Ubuntu 21.04 running with Projecteur and updated to 21.10 - did I get that right? |
|
Yes. I had some older version of projecteur on 21.04, updated to 0.9.2 when I found that it doesn't work anymore, but that did not help ... :) Let be know if I can be of any assistance. |
|
same thing happening on NixOS with gnome 41.1 (on wayland) with 0.9.2 as well as #173 , x11 works though. |
|
I just double checked with 21e5e60 and the cursor still does not move. If it is something like that, an option to keep the os device of the mouse and disable the virtual mouse would be a simple workaround. EDIT: some more links: |
|
Ok so this might be relevant: in when running now comparing to I have no particular idea what could break it but for me only in |
|
Any news at this point. Would love to use your tool but unfortunately it's not working (same as above) in ubuntu 21.10 :-/ |
|
Yes, sorry I couldn't allocate time for Projecteur. So it seems it is a two-folded problem.
I will need to install 21.10 in a VM and do some issue tracking. A question for users on X11 on Ubuntu 21.10:
|
|
Ah thanks |
Good to know, of course the nice feature of mapping custom inputs is disabled 😞 - so this is only kind of a workaround. Seems one issue is around the area of grabbing all the device input and feeding it (mapped) to a virtual uinput device. That definitely narrows down my issue tracking. |
|
indeed, but it is far better than a pointer that does not move 😅 |
|
Now that Ubuntu 22.04 is released I will check with that release and see if anything from earlier versions changed in regards to the Edit: @eiswind In case you updated already to 22.04 (I haven't yet) - is the issue the same on 22.04? |
|
It is definitely related on how to |
|
I know such time problems too well...... So thanks a million that the tool exists at all with such comprehensive functionality! Yes, I can confirm that in a regular 22.04-setup (no vm, fresh install yesterday). On 18.04 it works out of the box with your binary. On 22.04 the above workaround is necessary. However, it is strange that everything worked during the very first start-up on 22.04. Then I switched to Win10 (dual boot machine), installed the respective app and configured the device. Back in 22.04 no movement anymore. The Pointer with all features is displayed though. Maybe this is a useful additional information or just coincidence? |
|
Thanks @jahnf for the wonderful work. Hopefully I can continue working on Projecteur, it would be great to have it running on Ubuntu 22.04 100%. I'm not a developer, but if I can collaborate with something, with testing or with any situation, I'm attentive. This is the only alternative to bring Logitech Spotlight to life on Linux-Ubuntu. When executing: SO: Ubuntu 22.04 |
|
@khalil-i-o, thats a great idea. @jahnf: You are very welcome to contact me too if testing is necessary. |
|
TL;DR; I did some investigation and found out something interesting. BUT: If you change the line in the record file of the virtual device at position I don't know if this helps figuring out what the actual problem is, but I hope it helps a little ;) Oh, BTW: running fedora 37 workstation on gnome 43.2 with wayland and rpm-installation. EDIT: I seems there is a problem with key-codes above 562 (0x232). I.e. changing Projecteur/src/virtualdevice.cc Line 76 in 323532f KEY_BRIGHTNESS_MENU (649 / 0x289). It makes also no sense, that it "breaks" at this position. There are no keycodes defined between 562 / 0x232 and 575 / 0x23f. linux/input-event-codes.h
EDIT2: I think I got it:
long story short: We will need two virtual devices, one for the virtual mouse and one for the keyboard. I don't know, what the difference between EDIT3: Everything with key-ids between EDIT4: Changing the keycodes to the mentioned above brings back the mouse-functionality but disables all keymappings (for obvious reasons). skipping them brings the mappings back to EDIT5: I tried the following code: // Set all key code bits on virtual device
const bool keyboard = true;
const bool mouse = true;
const bool upper_keys = true;
if (keyboard) {
for (int i = 1; i < BTN_MISC; ++i) {
ioctl(fd, UI_SET_KEYBIT, i);
}
}
if (mouse) {
for (int i = BTN_MISC; i < KEY_OK; ++i) {
ioctl(fd, UI_SET_KEYBIT, i);
}
}
if (keyboard) {
for (int i = KEY_OK; i < KEY_MACRO1; ++i) {
ioctl(fd, UI_SET_KEYBIT, i);
}
}
if (upper_keys) {
for (int i = KEY_MACRO1; i < KEY_CNT; ++i) {
ioctl(fd, UI_SET_KEYBIT, i);
}
}keyboard with anything else (current state: all true): (KMU, KM, KU)
only keyboard: (K)
mouse with or without upper_keys: (MU, M)
everything false or only upper_keys: (U, ø)
conclusion: mouse and keyboard must not be used in the same virtual device if the mouse-button and keymappings should work. upper_keys crash the keyboard. I didn't check the spotlight functionality on all 8 combinations, it behaves different and there are probably some independent issues with wayland. |
|
Wow thank you @Blaimi for the detailed investigation - that is very useful - I will use your input to create a fix!! |
|
@Blaimi @benneti @eiswind @markoott If possible please test a version build from the https://github.com/jahnf/Projecteur/tree/bugfix/input-virtualdevice branch. Thank you very much in advance Also as artifacts available attached to this action run: https://github.com/jahnf/Projecteur/actions/runs/4285629256 |
|
sorry for the late reply, tested it now on several occasions and so far the new branch is working great for me with gnome+wayland. |
Description
I installed projecteur-0.9.2_ubuntu-21.04-x86_64.deb, and updated my machine to 21.10.
w/o Projecteur running I can move the mouse and use the next/back button.
when I start projecteur, the highlight apperears when I press the button, but I cannot move it at all, also back/next shows no action.
Happens both on wayland and x11.
Desktop/Linux Environment (please complete the following information):
Linux Distribution and Version: [e.g. Ubuntu 18.04]
ubuntu 20.10
Desktop/Window Manager and Version [e.g. GNOME 3.28, KDE 5.4...]
gnome 40.4.0 on wayland or x11
Did you built Projecteur yourself?:
[y/n]no(If yes: Please run cmake for existing build directories, to ensure the generated version info is up to date)
What is the output of
projecteur -f?: ...Projecteur 0.9.2
git-branch: master
git-hash: 82d9cfa
compiler: GNU 10.2.1
qt-version: (build: 5.15.2, runtime: 5.15.2)
device-scan: (errors: 0, devices: 1 [readable: 1, writable: 1])
What is the output of
projecteur -d?: ...Projecteur 0.9.2; device scan
+++ name: 'SPOTLIGHT'
userName: 'Logitech Spotlight (Bluetooth)'
vendorId: 046d
productId: b503
phys: 64:6e:e0:5a:27:e1
busType: Bluetooth
devices: /dev/input/event21, /dev/input/event20
readable: true
writable: true
The text was updated successfully, but these errors were encountered: