Debian Patches
Status for muse/4.3.0-2
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| 0001-Use-a-more-consistent-versioning.patch | Use a more consistent versioning. | Alessio Treglia <alessio@debian.org> | not-needed | 2018-12-16 | ||
| 0005-Python-3-porting.patch | Port scripts to Python 3 This patch is the result of running 2to3 over the Python scripts that are included in the binary package. =================================================================== |
Stuart Prescott <stuart@debian.org> | no | upstream | 2023-09-17 | |
| 0008-Fix_x86_build.patch | Add cstdint header to dsp.cpp to fix x86 build | Dennis Braun <snd@debian.org> | yes | 2023-09-17 | ||
| 1000-Add_a_field_code_to_desktop_exec.patch | Add a field code to desktop exec | Debian Multimedia Maintainers <debian-multimedia@lists.debian.org> | yes | 2026-10-22 | ||
| 1001-Fix_startup_crash_on_non-amd64.patch | Fix SIGSEGV on startup on all non-amd64 architectures PosToolbar::PosToolbar() called QPixmap::fill(Qt::transparent) while a QPainter was still active on the same pixmap. QPixmap::fill() internally starts a second QPainter on the same device, which re-begins the raster paint engine and leaves the outer painter with a NULL engine state; the following QPainter::drawPolygon() then SIGSEGVs. This made musE crash during startup on all non-amd64 architectures (Debian autopkgtest check-muse-application-loop). The first QPixmap::fill() in the constructor runs before the QPainter exists and is intentionally left unchanged; only the mid-paint fills are replaced by clearing through the active painter. |
Dennis Braun <snd@debian.org> | yes | 2026-10-25 |