Adam Williamson :fedora: / is on Nostr

Fedora QA team lead. If Fedora isn't working, it's probably my fault! he/him/his

Blog: https://www.happyassassin.net/pages/contact/
Matrix: @adamwill:fedora.im
Github: https://github.com/AdamWill
Pagure: https://pagure.io/user/adamwill

Last Notes

2024-08-28 19:27:24

- reply

pfft, youngun. I remember sitting around for several hours waiting for Quake to finish downloading. It was 9MB.

2024-08-28 17:06:38

being as old as I am, when I stop and think about it it is completely wild in *so many ways* that I just casually downloaded two ISOs totalling 4.4GB in about thirty seconds flat so I could boot each one once, test one thing, then shut it down and probably never boot it again (but leave it lying around for years because eh, it's "not that big").

2024-08-18 21:26:59

- reply

I don't think you understand how this works. There is no Linux Design Committee making decisions about how Linux works. There's the kernel community working on kernel drivers. There's the bluez project working on the bluetooth stack - https://www.bluez.org/ . The login managers and desktops are developed by different teams. The distros try to plug it all together into something that works. Nobody can stand up and say "From Tomorrow, Bluetooth Doesn't Work At Login On Linux".

2024-08-18 21:19:42

- reply

it could possibly depend on whether your user is an admin user and/or whether your distro has some kinda way to get pairing information from your user account (where you probably do the pairing) to whatever account your login manager runs as on your distro.

2024-08-18 21:18:40

- reply

er, this isn't true, though. My bluetooth mouse works just fine at my login screen, I use it all the time (on Fedora, but I'm 100% sure it works fine on many other distros too).
It's weird to talk about "Linux" here anyway, because any distro could (though likely wouldn't) do something different with driver or bluetooth stack loading, and there is no "the login screen" or "the desktop" in Linux (there are lots of login managers, and lots of desktops).

2024-08-09 05:18:19

today: #Flock2024 all day. lots of great sessions and some good side meetings. enjoyed the keynotes by Pat Riehecky and @npub14yf…dg0x , it was really great that Mark Pearson from #lenovo came out and gave us a couple of great talks, Dan Walsh (rhatdan on The Other Place) did a good talk on #bootc , and the mentorship summit with Amita Sharma and a great panel was as thought provoking as always (except when I'm in it). looking forward to some good hackfests tomorrow!

2024-08-07 14:30:40

I like the combination of #fedora folks in this pic from #Flock2024
https://cdn.fosstodon.org/media_attachments/files/112/921/217/468/219/291/original/313e207588077cfc.jpg

2024-05-28 20:23:14

- reply

I suspect maybe Asahi fails this check:
https://gitlab.gnome.org/GNOME/gnome-software/-/blob/346da0d84d96657d570964af0b1124ce451216e8/plugins/fedora-pkgdb-collections/gs-plugin-fedora-pkgdb-collections.c#L74
i.e. gnome-software decides this isn't "Fedora", so doesn't activate the Fedora upgrade plugin. It's just a guess, though, I might be wrong. @npub1qk9…azpx might know for sure.

2024-05-08 18:36:05

- reply

oh, good question. Does Asahi not show a grub menu at all? On my aarch64 test system (which is a Jetson Nano) I still get the grub boot menu after making it through uboot...

2024-05-08 15:09:05

- reply

sorry to hear your filesystem died. you can get a root console by booting with `systemd.debug-shell=1`and going to tty9. see https://freedesktop.org/wiki/Software/systemd/Debugging/

2024-04-24 18:57:07

- reply

"You will literally be swapping to newer and newer container images when you update rather than managing independent packages and dependencies." isn't quite right. IoT was already an atomic release. But it's switched from the original ostree technology to the new bootable OCI container approach. the ultimate user experience is much the same or improved, but the implementation is actually pretty different.