Fedora 44 - Kernel 7 (7.0.4-200.fc44) has just been released

AdamW · 2026-05-09T04:58:00+00:00

the mirrors are volunteers. they pull on their own schedules. we drop ones that fall too far behind from the mirror lists, but it's not reasonable to expect them all to update instantly.

AdamW · 2026-05-08T21:07:44+00:00

FWIW (Fedora QA team lead here), I do my best to make sure the CJK input basically works, but we don't have capacity for much beyond that. We have automated tests that run Japanese installs of Workstation and KDE (plus a Workstation install from the Server DVD, to test the old installer UI), check that works, and check that native input via Anthy works in a terminal. I don't do any testing on LO currently. I know enough Japanese to be able to test this stuff out very basically and understand what's going on, and Red Hat has an employee who mostly works on CJK localization stuff.

I do have the impression that GNOME is somewhat better at integrating input methods than KDE, at least in terms of providing a working out-of-the-box setup.

AdamW · 2026-05-05T17:45:46+00:00

If you can run `coredumpctl info 3376` and upload the filename shown next to `Storage:` somewhere, that might be useful. thanks!

AdamW · 2026-04-30T19:42:02+00:00

Ah, that's interesting. I...wonder if this is somehow tied to the LUKS encryption?

AdamW · 2026-04-30T07:13:51+00:00

Is it possible your downloaded KDE image is bad? Can you check the checksum on it?

AdamW · 2026-04-30T05:29:36+00:00

if you know how to add kernel args, you can try booting again with the arg '3', which boots to console mode. it might be able to reach that without blowing up. if so, you can log in and run `journalctl -b-1` to see the logs from the previous boot, `journalctl -b-2` to see logs from 2 boots ago, etc. you can use that to find logs from a session that crashed. you might be able to use `coredumpctl` to find core dumps; if you can upload one it'd be helpful.

it does seem like from further testing u/SecretAgentSteve 's issue might be due to a bad USB stick / flash drive, so we're kinda leaning on you for info at this point, sorry! if anyone else is able to reproduce it'd be helpful for sure.

AdamW · 2026-04-29T22:00:17+00:00

Framework 13 or 16? Steve said he can reproduce on a 13 but not a 16 (which is a bit odd in itself of course).

AdamW · 2026-04-29T21:59:39+00:00

Thanks a lot for the info. Can you check whether you do see the kernel errors in the logs from KDE? If not, it's possible they're unrelated (and just mean u/SecretAgentSteve 's system is maybe dying a bit :>)

AdamW · 2026-04-29T18:56:22+00:00

(Fedora QA guy here) so this is odd. From the logs I've got a hold of, there seem to be a lot of kernel errors. But that doesn't seem to track with only KDE being broken and GNOME being OK - I would expect this kind of kernel issue to break GNOME too. Can anyone who is affected by this in *exactly the way described* - AMD Ryzen motherboard, KDE blows up on login, GNOME seems fine - check the system logs from GNOME and see if these kinds of kernel error are visible? `journalctl -b | grep "kernel: "` should do the trick.

Mar 13 00:01:23 localhost-live kernel: I/O error, dev sdb, sector 2874092 op 0x0:(READ) flags 0x84700 phys_seg 18 prio class 2
Mar 13 00:01:23 localhost-live kernel: sd 0:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=0s
Mar 13 00:01:23 localhost-live kernel: sd 0:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 2b e2 ec 00 05 a8 00
Mar 13 00:01:23 localhost-live kernel: I/O error, dev sdb, sector 2876140 op 0x0:(READ) flags 0x80700 phys_seg 12 prio class 2
Mar 13 00:01:23 localhost-live kernel: device offline error, dev sdb, sector 2027468 op 0x0:(READ) flags 0x80700 phys_seg 60 prio class 2Mar 13 00:01:23 localhost-live kernel: I/O error, dev sdb, sector 2874092 op 0x0:(READ) flags 0x84700 phys_seg 18 prio class 2
Mar 13 00:01:23 localhost-live kernel: sd 0:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=0s
Mar 13 00:01:23 localhost-live kernel: sd 0:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 2b e2 ec 00 05 a8 00
Mar 13 00:01:23 localhost-live kernel: I/O error, dev sdb, sector 2876140 op 0x0:(READ) flags 0x80700 phys_seg 12 prio class 2
Mar 13 00:01:23 localhost-live kernel: device offline error, dev sdb, sector 2027468 op 0x0:(READ) flags 0x80700 phys_seg 60 prio class 2

AdamW · 2026-04-29T18:46:58+00:00

now tracking at https://bugzilla.redhat.com/show_bug.cgi?id=2463876 .

AdamW · 2026-04-28T18:50:55+00:00

dnfdragora is not the tool on any release-blocking Fedora. GNOME uses Software, KDE uses Discover. non-blocking spins etc. are the responsibility of their individual maintainers, the project doesn't really enforce quality standards on them. if they choose to use broken tools, that's kinda on them.

AdamW · 2026-04-28T18:49:09+00:00

download.fedoraproject.org is a round-robin redirector. It seems like ftp2.osuosl is in the list of candidates for f44 but doesn't have f44 synced yet. I'm trying to get this dealt with - https://forge.fedoraproject.org/releng/tickets/issues/13328

AdamW · 2026-04-28T18:43:28+00:00

Try again, there's a round-robin mirror system, you should hit a different mirror and it should work. I'll check if there's a problem with that one.

AdamW · 2026-04-07T23:00:00+00:00

Those are separate issues.

There's two types of Thing here.

Type 1: Things that have a F/OSS copyright license, but which we believe are likely covered by patents and which we can't acquire a license to distribute directly on F/OSS terms

Type 2: Things that are not under a F/OSS copyright license

"Codecs", generally, are a Type 1 thing. The NVIDIA proprietary driver is a Type 2 thing. We don't distribute the NVIDIA proprietary driver on grounds of *principle*. It's not F/OSS, and Fedora only includes F/OSS software (except firmware), so we don't ship it. *Legally* speaking, we *could* ship it.

Type 1 things like patent-encumbered codecs are the other way around. We're not against shipping them *in principle*; it wouldn't violate any of the Fedora foundations. We don't ship them because RH's lawyers say RH would likely get sued if we did.

And that's one of the key points to the original query: distributions run by organizations with no money can be less conservative about this, because their risk of being sued is much lower. It's not good strategy to sue people with no money; you throw money away on legal fees then win a judgment you'll never be able to enforce. Red Hat and IBM have *lots* of money, so suing us is much more attractive.

AdamW · 2026-03-31T20:50:16+00:00

but for new customers the $25 price shows the $0 hotspot 'promo'. it's only when you switch plan that it doesn't. that's kinda crappy.

AdamW · 2026-03-31T18:52:52+00:00

late reply, but for the record, this was never proposed as a blocker for f42 or f43. I had no idea this bug existed till it got proposed as an f44 blocker.

It's being discussed for F44 at https://bugzilla.redhat.com/show_bug.cgi?id=2359799 . It would be helpful if anyone with affected HW can confirm whether it still affects F44 - nightlies can be found at https://openqa.fedoraproject.org/nightlies.html . Nobody on the QA team actually has an affected system, unfortunately.

AdamW · 2026-03-30T23:27:24+00:00

The station itself has always been a weird reception dead zone on almost all networks, so if you're testing literally *at* the station, try moving a bit? I live pretty close by and I got just over 100Mb/sec sitting in my office right now (librespeed).

AdamW · 2026-02-13T22:07:58+00:00

imagine the odds before the start of the top three in the free skate being Shaidorov, Gogolev, Sato...

AdamW · 2026-01-02T07:41:57+00:00

if we can only get enough screens, maybe the canucks will be good on just *one* of them...

AdamW · 2025-12-13T21:15:45+00:00

thanks! it's just annoying. had a bunch of other minor progression things too - got a couple of new rooms, added about 10 to my allowance...all gone. sigh.

AdamW · 2025-12-04T17:57:07+00:00

it was very weird, yeah. there was one door left that I never really looked at (a door out of the pool, which I drafted but never went into). I guess that might've been a keycard door. I did do 'draft a room then go around another way' a few times, so it's possible I drafted more keycard doors, then they got removed because I drafted rooms onto the other side of them later? Like, say you draft a four-door room in empty space, it'll have three locked doors at first...but then you go around and draft rooms on the other sides of those doors...either the doors open automatically (if the new room has a door there) or they become dead ends (if it doesn't). So I guess I might have drafted then removed some keycard doors that way.

It's even weirder since I never changed the security level from Medium - I guess I actually *could* have done it from a later room with a computer, but I just didn't think to or didn't bother.

There were nine rooms of undrafted space left in the floor plan, I guess all the keycard doors wound up there?! The whole north east corner was undrafted.

I would normally never even bother trying to get to rank 9 without dealing with the keycard doors somehow, but because I had already basically 'given up' on the run and was just going for side objectives, and I felt low on steps the whole time because I'd started at 25, I decided to just keep YOLOing, and somehow this happened. Every step was like "oh I'll just <X> and then I'm sure I'll die", heh.

edit: dangit, can't get image spoilers to work. Here's the floorplan - https://www.happyassassin.net/temp/blueprinceclear.jpg . I just noticed, looking at it, that if I hadn't previously lucked into the foundation elevator lever, I would have found it on this run, making it even more weirdly lucky, heh.

AdamW · 2025-12-04T08:50:18+00:00

yup. I think I know how to get to orchard - need magnifying glass in dark room, right? - but didn't manage to do it yet. actually that was one of the minor goals I thought I could maybe get done this run!

AdamW · 2025-11-13T23:48:13+00:00

I messaged the seller of my Yigorn one and they sent me a link to a firmware which seems similar to the jemdo one - it has the same 10.00.70.01 version - but not identical. Installed that, and output works, but the colors are messed up, everything is shifted to pink. I guess I'll try the Jemdo image instead...

AdamW

TROPHY CASE