If we don't reevaluate patches, they tend to get carried on forever. I'm not saying that part of the patch shouldn't be reinstated, but I cannot reproduce the issue with 2.4.2, they even mention in 459 it may be fixed in 2.4.2. Forcing the GDK backend might "fix" it, but the issue likely lies elsewhere (probably GTK3, as noted in upstream 459). The original reporters all mention it happens with both X11 and Wayland sessions. Bug 1798987 (what the patch originally points to) in particular implies to me more guilt by association than an actual Wayland issue. > anything and allow all installs to work properly. > make it impossible to use - and the patch to the desktop file will not break > problem's don't manifest themselves on every install, but when they do they > issues and was the reason I introduced the patch to the desktop file. > There was even a bug report against the Audacity package recently > incompatibility and the fact that GDK_BACKEND=x11 is needed in the launcher. > There are several upstream issues including > I authored the changes to the spec, link to upstream Wayland issues? The currently packaged version is terribly unstable, where I had no issues using the newer version even under a Wayland session. Here we download the Audacity source code, compile it, package and install it.(In reply to Ian McInerney from comment #22) Make -j 2 & make install-libs install-headers & make distcleanAfter installing Audacity I will give instructions so Audacity can find this local installation, this will be done manually. configure -prefix=$HOME/audacity_build/audacity_deps/usr \
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |