The release notes advertise a privilege 0.26.0 deliberately does not grant #138
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: unom/punktfunk#138
Reference in New Issue
Block a user
#136 revoked
CAP_SYS_NICEacross all five Linux channels, because holding it makes the host unidentifiable to KWin and kills desktop streaming. It correctedCHANGELOG.md. It did not touch the user-facing notes, which still say:That was true of
0.26.0-1and is now precisely the opposite of true.It matters beyond pedantry: without the capability the priority ladder falls back to default, which is 0.25.0's behaviour exactly. So the notes were advertising a speed-up nobody actually gets — the same class of false claim as the gamescope packages in #135, found the same way.
What changed
The PyroWave bullet now leads with what genuinely landed — two encoder handles, the capture buffer headroom — and describes the priority switch as wired-but-dormant, with the reason. The lever really is wired natively on Linux for the first time; that part stands and stays.
A new
Fixedentry for the KDE breakage itself:Worth telling users even though the release was never announced:
0.26.0-1packages did reach the registries, and anyone who pulled one has a desktop session failing with a missing-screencast error that survives a clean reinstall. It also explains the dormancy the bullet above now refers to.Deliberately not a
## Before you updateaction. Upgrading strips the capability by itself on every channel, so there is nothing for a reader to do — and that section is for things that need them to act.Commit count 47 → 52.
Verification
Voice check clean — 0 internal-vocabulary hits above
## For developers. Notes are 67 lines.Sequencing
v0.26.0is tagged, published and unannounced. This is the last piece: the tag now gets re-pointed onto a main tip carrying #134 (Windows dead_code), #135 (gamescope build deps + the tag-time hard gate), #136 (theCAP_SYS_NICErevocation) and this. Then the rpm/deb legs re-run, the gamescope packages get verified to exist, and the announce goes out.The user-facing v0.26.0 notes said, of the PyroWave GPU-priority lever: "it is now, and the package grants the host the permission that switch needs" That was true of 0.26.0-1 and is now the opposite of true. Granting CAP_SYS_NICE made the host unidentifiable to KWin and killed desktop streaming on every KDE box across all five Linux channels, so 0.26.0-2 revokes it everywhere and must keep doing so. The lever is wired natively on Linux for the first time — that part stands — but it is dormant on an ordinary install, and the notes have to say so rather than advertise a speed-up nobody gets. CHANGELOG.md was already corrected in #136 (the 0.26.0-2 note under PW1 and the qualifier on the owed A/B). This is the user-facing half, which #136 did not touch: * the PyroWave bullet now leads with what DID land (two encoder handles, the capture buffer headroom) and describes the priority switch as present but dormant, with the reason. * a new Fixed entry for the KDE breakage itself. Worth telling users even though the release was never announced: 0.26.0-1 packages did reach the registries, and anyone who pulled one has a desktop session that fails with a missing-screencast error surviving a clean reinstall. It also explains the dormancy the bullet above now refers to. Deliberately NOT written as a "Before you update" action: upgrading strips the capability by itself on every channel, so there is nothing for a reader to do. Commit count 47 -> 52. Voice check clean (0 internal-vocabulary hits above "## For developers"); notes 67 lines.