-
Notifications
You must be signed in to change notification settings - Fork 89
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
Switching screen does not work on Wayland #99
Comments
Hi @thomwiggers, and thanks for reporting this bug. First a couple of questions:
We can fix the error that is reported in your log, but I'm not even sure that it is related to the bug you have. It is an error in the handling of the event after a window is (un)maximised, and should really have no impact except on disabling the screen saver. I suppose that playing videos does not work with Wayland either. Is XWayland enabled? What happens if you launch The recommended way of installing on Linux is pip, as I have no control at all on AUR packages. In case the previous doesn't work, can you try installing from pip? In particular, the current version is 1.2.0 since February 7th so I'm not sure what the 1.2.0-1 version from AUR, updated on January 4th can be (I'm assuming the "1.20.0-1" is a typo and you meant "1.2.0-1"). |
1.20 was indeed a typo. I'm running Gnome 3 on GDM on Wayland.
Using I'm not sure what you mean by "the current version is 1.2.0 since February 7th", because Github shows that 1.2.0 was available in September. |
In Wayland, fail the the enabling/disabling of screensavers with a simple warning.
Thanks for the clarifications. Nevermind the dates, the github releases got me confused because I forgot to convert the latest tags to releases. (Still not sure what the
|
The I disagree that you should necessarily specify However, that is off topic for this issue. As far as I could tell, the documentation does not mention that Wayland is poorly supported. With regards to what I was trying to do: just launching Pympress already starts popping up the traceback, probably as it is trying to set full screen and move the windows to specific displays (which doesn't work without XWayland). Pressing I haven't tested it, but I think the warning could be more helpful, "unsupported OS" is extremely vague (especially since it's the WM, not the OS that's not supported). |
I'd rather we don't need to recompile gtk or gobject at every pympress install. This leads to bloat, out of date libraries, extends the install requirements to a compilation toolchain and the development headers of a bunch of other packages, etc etc. It's not worth it, and that's literally why there is the Nevertheless, I started a discussion on that at #100 (we need at least to fail in a more graceful way than For wayland support:
Finally, on the bug. Is |
No,
|
The problem here is that, under Wayland, |
I think Wayland support is (supposed to be) better in Gtk 4, but the list of breaking changes is very long (see #267) so it’s unlikely I have the time to port pympress any time soon. Also I’d have to figure out what the implications are for currently supported platforms (e.g. does Gtk 4 compile on Windows? Is there support for shipping the Gtk 4 dlls in an installer ? etc.) So unfortunately we’re kind of stuck with sub-optimal Wayland support for now. |
From Gtk docs:
Does |
Actually my system now ships wayland as opposed to 4 years ago and I’ve been able to test things. Closing as Wayland does not support the concept of moving windows, so switching screens make no sense. I’ll add a best-effort auto-fullscreen for wayland. |
Includes: - Refactoring of ScreenArea with Monitor as a child class - use fullscreen_at_monitor() to provide on-startup fullscreen - disable swap-screens functionality as it can not be provided, see #99
In Wayland, fail the the enabling/disabling of screensavers with a simple warning.
Environment
Pympress
Expected behaviour
Steps to reproduce
s
Problem
Switching screens doesn't work. The following appears in the log, and also appears at pympress startup:
The text was updated successfully, but these errors were encountered: