Post #2785700

2026-03-17 16:04 UTC

@postmarketOS@social.treehouse.systems how does "No debugging audio when you need to make a phone call and no fussing with a broken web browser" follow from "the system boots successfully"? The system may boot successfully with a broken audio and/or a broken web browser. I'm curious and didn't find it in the blog post

Replies (4)

@alexia@app.wafrn.net 2026-03-17 16:05

the idea is that faults like this can be discovered before an update is applied as it's much easier to replicate and test the images, and a partial-upgrade state (which might break something like audio) is entirely avoided as updates are effectively atomic

Open ##2785701
@weirdtreething@donotsta.re 2026-03-17 16:43

@YaLTeR@mastodon.online @postmarketOS@social.treehouse.systems If an update breaks something such as audio, you have the option to roll back to the previous version without the issue.

Open ##2785707
@UndeadLeech@fosstodon.org 2026-03-17 16:52

@YaLTeR@mastodon.online @postmarketOS@social.treehouse.systems Well the audio would have to work reliably in the first place. 😅

Open ##2785708
@pabloyoyoista@social.treehouse.systems 2026-03-17 20:23

@YaLTeR@mastodon.online part of it is that we have an unexpectedly high number of audio failures consequence of partially-applied state and buggy upgrades. Why it's always audio 🤷 You can still get an update with broken audio if Pipewire or ALSA broke for your device. But then it should be reproducible in all upgrades/installs, which has really not been the case so far, speeding up fixes @postmarketOS@social.treehouse.systems

Open ##2785709