44 USB Port 22 Power Adapt Combo HotPlug Board

@whitequark github is so slow for me, just the http ui

I spent my time trying to make it better. Not just write code, but find better or at least different ways to do so. Simpler, cleaner, more general, more comprehensible.

What's happening to day is a complete repudiation of everything I was trying to achieve.

RE: https://mastodon.social/@cmconseils/116589464367576074

But we need AI to make the investors happy!!! 📈

(maybe smth is wrong elsewhere that needs fixing...)

Is it just me or is github really slow now

#gnome #gtk

We wanted to get rid of the hard coded users in our nightly image builds so we added a small first-boot app that allows to configure the language, on-screen keyboard layout and user. For that we split some widgets out of mobile settings and @rudraps added #rust bindings for it.

5/x

@craftyguy @oausi @postmarketOS

I think this comment is also a very good opportunity to post https://postmarketos.org/state/ again.

A community of volunteers identified an issue on Friday night and got it fixed in under 24h. Honestly, kudos to everybody involved. Anybody thinking such community of volunteers funded by donations that cover an absolutely tiny fraction of the work done (yet are critical for the sustainability of the project) should not be allowed to make mistakes is in my opinion, breaching the social contract under which the work is done.

I think I found a new funny way to wisely spend your time.

seeing maintainers in lkml replying to sashiko-bot "you're wrong" multiple times

Heads up for edge users, OpenRC may hang on boot or shutdown with Plymouth.

"A fix was submitted to OpenRC, but in the meantime the Plymouth OpenRC integration plugin has been temporarily replaced by a kill-plymouth OpenRC service that runs on boot, just like what used to be the case with pbsplash. This workaround is included in postmarketos-bootsplash 0.5.1."

https://postmarketos.org/edge/2026/05/14/plymouth-openrc-issues/

Edit: The fixed package has been built and is available in the repos. It is now safe to update.

Heads up for edge users, a recent losetup update broke the initramfs.

"This was fixed in postmarketos-initramfs 3.10.2. If you upgraded your system recently and are not running that version, **do not reboot** until you upgrade to postmarketos-initramfs 3.10.2"

It is important to note that the upgraded package is not built yet. If you would like, you can follow https://build.postmarketos.org/#queued to see when it is ready.

https://postmarketos.org/edge/2026/05/15/losetup-option-removal-leading-to-boot-failure/

New stable kernels landed today in Alpine Linux. They address ssh-keysign-pwn (CVE-2026-46333)

- 6.18.31
- 6.12.89
- 6.6.139
- 6.1.173
- 5.15.207

These have been backported all the way down to Alpine Linux 3.16.

Edit: These versions fix ssh-keysign-pwn, not Fragnesia

wondered why vscode was running like total shit after a recent update, then it popped up telling me the extension host crashed and offered to do an extension bisect so im like sure why not

i go through picking can/can't reproduce just based on vibes of how shit it was running

i have 116 extensions installed and THIS was the end result of that, joker moment of a fucking generation. fuck microsoft

(if you reply to this telling me to not use vscode i will probably block you, yes that includes suggesting codium or whatever. i wish this wasn't the workflow i ended up with but it is and now isn't the time for me to switch)

@cas @cxberger that's just not serious work at all

@cas so vscodium won't really do much

@cas

> if you reply to this telling me to not use vscode i will probably block you, yes that includes suggesting codium or whatever

I'm pretty sure vscodium is basically the same as if you got vscode straight from your distro repos (unless your distro just ships the precompiled binaries straight from microsoft, which is a bad idea™)

Not that I looked much into vscodium these past few years.

@cas that's why I stick to b4 0.14 for dear life. 0.14 was the last version to not have huge vibecoded junk

sooo i tried using the new b4 review TUI for my last U-Boot PR and it was a bit of a disaster. I understand the process being a bit clunky to begin with but the whole process of actually setting up a branch was really involved. It failed to update a bunch of series on pathwork, and the b4 ty emails it generated had completely wrong commit SHAs

I get that the intention is primarily patch review but even for that it feels less like a tool i can utilise to automate the process and more like an imposed workflow that offers little flexibility

the thing that really pissed me off in the end though was realising that b4 review was VIBE CODED, kinda explains everything... This tool had so much potential but i struggle to see now how it will deliver when AI is involved in building it

#kernel #maintainer #b4 #mainline #patchwork #foss

@aelin @cas @craftyguy @oausi maybe regular booting of pmOS every few hours would've