-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Projecteur doesn't seem to work all that well on Gnome with Wayland on Fedora #170
Comments
Hello mrshu, Thank for your report. |
Thanks for the reply @jahnf ! I have indeed tried to use With regards to enabling the Let me just stress out once more than this doesn't preclude me from using Projecteur in any way -- it works very well with Xorg -- it's just something I thought would be best to share in here :) |
Alright, I am planning to install a Fedora 34 in a VM and try to first reproduce and see how this might be fixed with Qt5. |
Thanks @jahnf, I'd be happy to do any field testing you might find useful as well! |
Hi, I can confirm the issue. Desktop/Linux Environment (please complete the following information):
own Qt6 build
aur/projecteur-git
aur/projecteur
Additoinal information: |
@Gusser93 Are you using Wayland or Xorg? |
Sorry, I'm using Wayland. |
As a workaround you could use the following: This works at lease in a virtual machine with Fedora 34 I tried yesterday. |
@jahnf sadly, it doesn't seem to work all that well for me on the Fedora box I run -- the zoom button does indeed respond but moving the presenter doesn't seem to move the zoomed part, and the other two buttons do not seem to work either. |
When I closed the application, though, I did receive the following error log:
Could it be that my setup is rather strange? |
@mrshu I run Fedora 34, with Gnome and Wayland, and am seeing similar results. Mouse cursor (now zoom window) stops moving once Projecteur is started, and forward/backwards stops responding. Zoom window does appear, but is slow to initialise - I am guessing this might be due to ( if? ) the program has to take a screenshot first - maybe that is why it takes a second to appear? Program output...
Journal states...
I tried coding up a PyUSB module, to research a bit, I added some udev rules, to allow my user to interact with the USB device, and I am intercepting the data, but I have been unable to reverse the mouse coordinates data I am receiving, to anything meaningful I can use as reliable x,y coordinates (does anyone here know how the spotlights coordinates data is packed?). Anyway, while able to receive from the unit, I too was unable to send keys and clicks directly to other apps, I decided to use ydotool to handle that part, which works great and is fast enough (by sort-of circumventing the security model of Wayland, and running ydotoold as root) - I guess Projecteur could do something similar? Cheers, really wish we could get this running on Wayland! |
Thank you for all your feedback, Some details are just differently (or sometimes not implemented at all) on Qt side due to the different workings and restrictions of Wayland. In any case, every detail or hint is appreciated. About the zoom: |
Cheers @jahnf - Thank you so much for Projecteur! Some suggestions, if you like...
*: I note that ksnip has added Wayland support for kde and gnome, and its screenshots seem very snappy - I just converted from flameshot to ksnip to test it, and there is a notable difference - it is also Qt5 based, so maybe there is something that can be learnt here? |
Hi @jahnf , we should implement Reference: |
I briefly tested the program with Fedora 34 today. There are three different issues with Projecteur in wayland.
I have opened a new meta issue for discussing these problems (#174 ). |
Link to a related issue: githubuser0xFFFF/Qt-Advanced-Docking-System#288 |
Just as another Wayland data point: On Debian Bookworm (Projecteur built from today's master), the overlay on my three-monitor system (GNOME, horizontal monitor arrangement, middle monitor holds the menu bar) works as follows:
It seems that the left two monitors are treated differently than the third? Anyway, using |
Description
While trying out Projecteur on Gnome with Wayland on Fedora, I came across a couple of issues. Projecteur is still very useful and I use it with Gnome on X.org with a great success but seeing how Wayland will probably be the only reasonable option in the future, I wanted to note my experience here.
Thanks!
To Reproduce
Just starting projecteur and clicking the main "zoom" button multiple times ends up generating the following log:
While all this is happening, the pointer doesn't respond to movement and it also seems that further clicking only generates the
Wayland does not support QWindow::requestActivate()
message.Expected behavior
I would expect Projecteur to work the same way as it does on X.org (i.e. clicking and moving with the pointer would work out of the box).
Desktop/Linux Environment (please complete the following information):
n
projecteur -f
?:projecteur -d
?: ...The text was updated successfully, but these errors were encountered: