Bugzilla – Bug 1219523
MuseScore (mscore) no longer plays scores after tumbleweed update
Last modified: 2024-02-08 06:25:14 UTC
After updating Tumbleweed yesterday, snapshot 20240131 -> 20240201 MuseScore no longer plays a score. It also dumped when trying to close mscore. MuseScore in Flatpak works fine I did a snapper undochange to revert to the status at snapshot 20240131 and MuseScore now works again so I suspect that there was something in snapshot 20240201 that is causing the problem.
I confirm the bug. I did not install from flatpak, though I did install https://github.com/musescore/MuseScore/releases/download/v4.2.0/MuseScore-4.2.0.233521125-x86_64.AppImage Neither the above 4.2.0 nor 4.2.1 appimages play sounds. I started playback, that does not move forward but icon did changed to playing, and "wpctl status" does not show musescore as client. My opinion is that might be pipewire's fault or some libjack.so.0 library. Unfortunately i had not configured snapper, so I have no available snapshots and cannot revert back, through some rollback.
Reading https://github.com/musescore/MuseScore/issues/21358, it might be due to pipewire-1.0.2-1.1 and musescore client communication.
(In reply to Jimis Hol from comment #2) > Reading https://github.com/musescore/MuseScore/issues/21358, it might be due > to > pipewire-1.0.2-1.1 and musescore client communication. From the last comment in that bug report I understand an update of pipewire will solve this. I saw that 1.0.3 is already in Factory, so it will be in one of the coming snapshots.
(In reply to Cor Blom from comment #3) > From the last comment in that bug report I understand an update of pipewire > will solve this. I saw that 1.0.3 is already in Factory, so it will be in > one of the coming snapshots. I do not use factory repository. Yesterday I saw an upgrade to pipewire_1.0.2-1.3 that did not fix the issue. So, till 1.0.3 version one might have to use flatpak.
Just tested tw 20240206 with pipewire 1.0.3 and musescore plays score for me. So will mark this as fixed
Thanks for the testing and the confirmation that it's fixed with 1.0.3!