Description of problem: Version-Release number of selected component (if applicable): gnome-clocks-3.36.2-2.fc32.x86_64 How reproducible: Always Steps to Reproduce: 1. Log into wayland session 2. Open Clocks 3. Try to add new city. Repeat on both monitors Actual results: There is one monitor where it doesn't work Expected results: Should work on all monitors obviously ;) Additional info: Originally reported in https://bugzilla.redhat.com/show_bug.cgi?id=1331044
Obvious workaround: Don't use Wayland. I know it's better and the future but I got quite some annoying issues with it, therefore I still use x11.
Found the upstream issue and asked for clarification there. Can someone easily try to reproduce this issue on another Fedora Linux or with another Clocks version? (I'm still with F32 at the moment.)
Should be fixed with Gnome Clocks 3.38 and later. It's not too long until F32 hits EOL and I think it's not really worth it to fix it that late. Issue can be closed once the fix is confirmed on F33.
Works for me. ❯ rpm -q gnome-clocks gnome-clocks-3.38.0-1.fc33.x86_64 ❯ cat /etc/fedora-release Fedora release 33 (Thirty Three)
Thank you! Closing as Wontfix for F32.