Description of problem: Open up Audacity, import an audio file. Try to edit. Find that the cursor (i.e. the black line that shows you where you are in the waveform) doesn't scroll with playback. However, if I click or roll the mouse wheel, the cursor shows up where it should be. If I keep scrolling the wheel or clicking then I can make it more or less keep up with playback. Version-Release number of selected component (if applicable): Fedora 35 Workstation Gnome 41.1 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
That cannot be Xwayland, simply because Audacity in Wayland is using Wayland natively. If you run audacity with the x11 backend (hence in Xwayland, it works fine). $ GDK_BACKEND=x11 audacity So it's either a bug in audacity or in GTK.
Right, I'm moving this to audacity (as Xwayland works), maybe the (dirty) workaround for us downstream is indeed to tweak audacity's desktop file to make it run on X11 (hence Xwayland) instead of using Wayland native?
We used to have that in the desktop file, but it was removed in the update to 2.4.2 (https://bugzilla.redhat.com/show_bug.cgi?id=1836497) as the original creator of the update diff couldn't reproduce the issue it was fixing. We eventually came to the conclusion that it should be reinstated in the desktop file, but I guess that task got lost because the issue got closed automatically by bodhi. I don't quite have time to get to that soon though, so if another person wants to make a PR against the package in src.fp.o, we can merge it in to all the branches.
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
Reopening, this was on F35
*** Bug 2031478 has been marked as a duplicate of this bug. ***
FEDORA-2022-d435c74328 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-d435c74328
FEDORA-2022-857f49ff15 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-857f49ff15
FEDORA-2022-857f49ff15 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-857f49ff15` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-857f49ff15 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-d435c74328 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-d435c74328` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-d435c74328 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-d435c74328 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-857f49ff15 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.