casey (head firmly patted)

@cas@treehouse.systems
2.8K Followers
788 Following
5.4K Posts

🏳️‍🌈 lesbian hacker in Berlin!

heavily involved in #LinuxMobile and @postmarketOS. Don't dm me for support, ping me in a public matrix channel.

I maintain U-Boot for Qualcomm devices and do other cool embedded stuff @ Linaro

"you are never beating the down bad allegations" ~ @isa

This account is mostly for technical topics, my personal account is @casey

pronounsshe
GitHubhttps://github.com/kcxt
Matrixcaleb:postmarketos.org
Websitehttps://connolly.tech
i'm also happy and excited to announce that we've signed a partnership with @LinaroLtd to collaborate on the integration of the Qualcomm QCS6490 processor in the MNT Reform series of devices, including Pocket, Next, and especially our future mini tablet. more about this soon!

We often talk about the scouting rule of “always leave the campsite cleaner than you found it”, or in a software context “always leave the code a little bit better than you found it”.

If you see duplication in the code, then remove that before you leave the method. If you see poor variable names then fix those before you leave.

What we don’t talk about as much is how a culture of branching and Pull Requests (PR’s) actively discourages making small changes for that purpose. If I want to rename a method to make it clearer and know that making that little change is going to require real effort to go through a review process and manual merges, then I’m more likely to decide to just live with the original name, even if it is is poor.

Whereas if I can make that little refactoring and directly check it into mainline then it’s a very low effort change that contributes to the quality of the product. It’s become easy to do the right thing.

How many things do we have like this, that actively discourage us from doing the right thing?

thanks everyone who helped make the new #postmarketOS release! they just get better and better every time.

i continue to be more and more hopeful that we will deliver on our mission to build a production ready OS, made by and for the community that continue to contribute (whether through code, reports, debugging, or donations).

we are not stopping with systemd... next up will be factory reset support, update rollbacks, EFI on qualcomm phones, immutability, and huge tooling improvements

embedded edition is also on my mind, we need better ways to build and maintain embedded systems and we absolutely have the raw ingredients

https://postmarketos.org/blog/2025/06/22/v25.06-release/

v25.06: the one with systemd

Aiming for a 10 year life-cycle for smartphones

postmarketOS
so #gpn23 was absolutely incredible,, this one feels so lucky to get to spend time with so many cool people :3
do i buy a döner or cook when i get back?
döner
67.7%
cook
27.4%
i don't care
4.8%
Poll ended at .
lesbians in berlin? more likely than you think .... when this ICE arrives

Is there a good writeup / overview on how cameras on mainline #mobilelinux work and where you can tweak things?

I'm asking because the back camera on my #pixel3a flashes and the picture sometimes freezes and I would like to look into fixing this. I just have no Idea how cameras work on linux and I'm unsure where to start.

#postmarketOS

@david_chisnall @dvandal @strlcat @davidgerard@circumstances.run I have poured most hours of my last 10 years of life into listening to users and pushing things forward on Wayland even if I personally wouldn't need the feature. I really saddens me that someone would think that Wayland developers don't care.

We do care, but we only have a finite amount of time in our volunteer life. Yes, we don't copy-paste solutions from X11: we try to fully understand the problem space and do better. This does mean that coming to us with technical solutions rather than use-cases tends to be met with "please, explain why you need to do this?".

I don't really know what you mean when you say that we silence criticism. I've read enough in the past years to guarantee that it's not silenced. I appreciate constructive criticism better than rants, rants tend to demoralize me.

I am also saddened about the conspiracy that big corp deprecates X11 against the community's will. There is no single company with a monopoly here, please take a bit of time to look at Wayland developers' employers. Personally, I'm ex-SourceHut and now just a volunteer (my day job is unrelated: SNCF Réseau).

I've never said that X11 was deprecated, and I always tell people to use whatever works best for them. The only reason why X11 has less activity nowadays is because X11 lacks volunteers. (We severely lack volunteers on the Wayland side too.)

People, distros, communities move away from X11 if/when they collectively decide that they should. Nobody's pulling the strings here.

Microplastics or something #gpn23
×

In 1984 Apple introduced the Macintosh with 128K of memory. The primitive 1.0 version of the Finder acknowledged that when sorting a list it made sense to sort it case insensitively for humans, versus sorting on the raw bytes of the name like a computer.

This morning I attempted to delete `bookmarks.html` from a sea of files starting with uppercase letters in GNOME Files. It wasn't with the 'B' files, instead it was after 'Zed'.

Edit: this is a musl issue, not a GNOME one (see reply)

#UX

Thanks to pointers from @loke my file sorting issues are due to musl libc.

https://wiki.musl-libc.org/open-issues.html#Locale_limitations
https://www.openwall.com/lists/musl/2017/11/26/9

There was an announcement a month ago about improving this:

"Thanks to a grant from NLnet, I'm starting on a project to overhaul the locale support in musl. This will be in collaboration with folks from postmarketOS, a project which is well-positioned to provide testing and feedback by virtue of their using musl in an
end-user-facing setting."

https://www.openwall.com/lists/musl/2025/05/05/5

musl libc - Open Issues

@wezm that's very weird. The sorting is actually locale dependent in GNOME Files, but with an English locale selected you should be getting case insensitive sort.

I'm not sure how this would happen on any standard distro, but it seems like you might have the "C" locale selected? Or perhaps have overridden just the LC_COLLATE variable? (I've actually done this intentionally on one of my systems)

@kepstin The only locale looking things I have set in my environment appear to be:

LANG=en_AU.UTF-8
GDM_LANG='en_AU.UTF-8'
LC_CTYPE=en_AU.UTF-8

GNOME Settings is as attached. Anything look off there?

@wezm @kepstin This is weird indeed. Your locale looks good, so the only explanation I have is that for some reason the locale definitions are not properly installed.

But if they're not installed, why are you able to even select it in the settings?

Could you try to open a terminal and use sort to sort a text file with a mix of upper and lower case? The sort command should use locale-dependent sorting just like the file manager, but if that works, then this is actually a bug in GNOME. If it doesn't work, then we can remove GNOME from the equation and try to figure out what's wrong with the locale files.

@loke it's possible this is a distro issue. Chimera is pretty weird after all. `sort` shows the same behaviour as nautilus. I'm not sure if it's relevant or not but I noticed that there was no en_AU in musl-locales (https://git.adelielinux.org/adelie/musl-locales). The behaviour was the same when I selected en_GB though. As well as `LC_COLLATE=en_US.UTF-8 sort /tmp/files.txt`
musl libc - Open Issues

@wezm ah yes, thar explains the issue.

It's a bit surprising though. Isn't musl supposed to be a drop-in replacement of glibc? You'd think locale support would be important.

Then again, I've seen people intentionally running with LANG=C because tgey abhor the idea of any kind of localisation at all (they also hate UTF-8)

@loke it's a drop in replacement in that things run, but it seems implementing full locale support has been on the todo list for some time. Hopefully the grant will get it over the line.

@loke @wezm FWIW we (postmarketOS) are working on implementing this together with upstream musl: https://www.openwall.com/lists/musl/2025/06/02/2

Also, Wesley, maybe you could update the original post with an edit stating that this is due to a shortcoming in musl and not GNOME? RIght now it's plain misleading and makes GNOME seems a lot more behind than it really is. I get that it still happens with upstream GNOME but using musl instead of glibc can hardly be considered mainstream Linux.

musl - Planned locale work and community thoughts

@newbyte @loke yep I found that announcement and posted about it earlier. I tried to make an edit earlier as well, but I was out of characters on the post, so replied instead. You're probably right though, so I'll remove some of the the original text and replace it with an edit.
@wezm @loke musl actually came to mind when I wrote my original comment, since I knew their locale implementation was a non-functional stub, but I didn't think there were actually any distros shipping a working GNOME on musl… things I learn, I guess.
@wezm I'm the other way around. I had to install gls (GNU ls) on macOS and alias ls as 'gls -v' to see files sorted in natural order (I.e. bookmarks.html appearing after 'Zed'). This human much prefers uppercase
letters come before lowercase letters.
😆

And if you guessed I am a long-time UNIX/Linux user, you got it right.
@wezm distro packaging issue? it is ok with opensuse.
@stephanie yeah it might be a Chimera issue.
musl libc - Open Issues

@wezm ah debloated distro moment /nm