Hi folks, I'm generating a weekly report of activity in the Fedora project centered on teams and SIGs, it's called "This Week in Fedora" <https://abompard.fedorapeople.org/twif/>. This generation uses an LLM. The goal is to make it easier to catch up with everything that's going on in the project, and to give visibility to each group's work and requests for help or testing. I think that from a newcomer's point of view, having an insight on what a group is working on at a point in time is helpful to decide whether it's interesting and worth contributing to. I'm collecting activity from: - this mailing-list - discourse posts with the `#arm-sig` tag - meetings in Matrix meeting channels, but I haven't seen any for this team recently In the latest version, I've added the possiblity to gather messages exchanged in Matrix channels. The `#arm` channel is public and its history is available to anyone, but a quite a few people in mutiple Matrix channels were unhappy about the LLM collecting this info, for various reasons. I would like to know whether this group is OK with my program collecting and submitting info to an LLM from the following sources: 1. mailing-lists, discourse posts and meetings (if any) 2. a ticket tracker in the ARM group on Fedora Forge, if you end up creating one in the future 3. the matrix channel I would like to make the case for source 3 (the Matrix channel) because I think it's less obvious: knowing the "tone" of a conversation and the currently discussed subjects before joining is very important to help contribute to it. It's like when you're added to an empty group chat and you don't know how to start. That's why we show history to new channel members, and this would be the same idea at a higher level. Plus there's actual work going on in there for a lot of groups. That said, I recognize that the form of the tool influences its use, chat messages are usually less thought-through than emails or forum posts, and members could be indimidated that something they write there and regret end up in a visible summary (the program respects message edits, but anyway). Since my goal is to foster participation, the one thing I don't want to do is to hinder it in another way. I know I've asked this in the chat last week but someone in another room noted that people can easily miss Matrix messages, which it true. Please decide which collected sources, if any, you are OK with (and if you work in other places that you would like to have collected, of course (I can do RSS feeds!)). If the group is OK with Matrix channel collection but some individuals aren't, I can also exclude certain Matrix usernames from collection throughout the Matrix channels that are not meetings. I'm happy to answer questions if you have any. Thanks! -- _______________________________________________ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
Thursday, September 17, 2026
Tuesday, September 15, 2026
Fedora Linux 45 Beta Released
The Fedora Project is pleased to announce the immediate availability of Fedora Linux 45 Beta, the next step towards our planned Fedora Linux 45 release in October. Download the prerelease from our Get Fedora site: * Get Fedora Linux 45 Beta Workstation: https://fedoraproject.org/workstation/download/beta * Get Fedora Linux 45 Beta Server: https://fedoraproject.org/server/download/beta * Get Fedora Linux 45 Beta IoT: https://fedoraproject.org/iot/download/beta * Get Fedora Linux 45 Beta CoreOS: https://fedoraproject.org/coreos/download?stream=stable * Get Fedora Linux 45 Beta Cloud: https://fedoraproject.org/cloud/download/beta * Get Fedora Linux 45 Beta KDE Plasma Desktop: https://fedoraproject.org/kde/download/beta Or, check out one of our popular variants, including Xfce, LXDE, COSMIC, i3, and other desktop environments: * Get Fedora Linux 45 Beta Spins: https://fedoraproject.org/spins/beta <https://fedoraproject.org/spins/beta> * Get Fedora Linux 45 Beta Labs: https://fedoraproject.org/labs/beta <https://fedoraproject.org/labs/beta> * Get Fedora Linux 45 Beta Atomic Desktops: https://fedoraproject.org/atomic-desktops/beta <https://fedoraproject.org/atomic-desktops/beta> For more details about the release, read the full announcement at: * https://fedoramagazine.org/announcing-fedora-linux-45-beta/ or look for the prerelease pages in the download sections at: * https://fedoraproject.org/ Since this is a Beta release, we expect that you may encounter bugs or missing features. To report issues encountered during testing, contact the Fedora QA team via the test@lists.fedoraproject.org mailing list or in the #qa:fedoraproject.org Matrix room. -- _______________________________________________ announce mailing list -- announce@lists.fedoraproject.org To unsubscribe send an email to announce-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/announce@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
[Test-Announce] Fedora 45 Branched 20260915.n.0 nightly compose nominated for testing
Announcing the creation of a new nightly release validation test event for Fedora 45 Branched 20260915.n.0. Please help run some tests for this nightly compose if you have time. For more information on nightly release validation testing, see: https://fedoraproject.org/wiki/QA:Release_validation_test_plan Notable package version changes: pungi - 20260912.n.0: pungi-4.14.0-1.fc45.src, 20260915.n.0: pungi-4.14.0-2.fc45.src Test coverage information for the current release can be seen at: https://openqa.fedoraproject.org/testcase_stats/45 You can see all results, find testing instructions and image download locations, and enter results on the Summary page: https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20260915.n.0_Summary The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20260915.n.0_Installation https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20260915.n.0_Base https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20260915.n.0_Server https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20260915.n.0_Cloud https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20260915.n.0_Desktop https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20260915.n.0_Security_Lab Thank you for testing! -- Mail generated by relvalconsumer: https://forge.fedoraproject.org/quality/relvalconsumer -- _______________________________________________ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-announce@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
Monday, September 14, 2026
[389-users] Re: Security updates required for recent 389 Directory Server releases
Hi Viktor, Version 2.2.11 is not available in the COPR repo. I'm still confused about the current state of packages. 2.2.9 appears to still be the latest version of 389DS for Rocky 8/9, when using the instructions on this page: https://www.port389.org/docs/389ds/download.html Based upon your email, shouldn't that repo offer at least 2.2.11? Thanks in advance for your advice, -Bryan On Thu, Sep 10, 2026 at 01:38:34PM +0200, Viktor Ashirov via 389-users wrote: > Hello, > > The 389 Directory Server team published security updates for multiple > release branches: > > - 3.3.1 (https://www.port389.org/docs/389ds/releases/release-3-3-1.html) > - 3.2.3 (https://www.port389.org/docs/389ds/releases/release-3-2-3.html) > - 3.1.5 (https://www.port389.org/docs/389ds/releases/release-3-1-5.html) > - 3.0.7 (https://www.port389.org/docs/389ds/releases/release-3-0-7.html) > - 2.9.1 (https://www.port389.org/docs/389ds/releases/release-2-9-1.html) > - 2.8.2 (https://www.port389.org/docs/389ds/releases/release-2-8-2.html) > - 2.6.3 (https://www.port389.org/docs/389ds/releases/release-2-6-3.html) > - 2.4.7 (https://www.port389.org/docs/389ds/releases/release-2-4-7.html) > - 2.2.11 (https://www.port389.org/docs/389ds/releases/release-2-2-11.html) > - 1.4.3.41 ( > https://www.port389.org/docs/389ds/releases/release-1-4-3-41.html) > > These releases address multiple security vulnerabilities, including > remotely exploitable issues such as: > - CVE-2026-18922 <https://access.redhat.com/security/cve/CVE-2026-18922> - > 9.8 Critical > - CVE-2026-19843 <https://access.redhat.com/security/cve/CVE-2026-19843> - > 8.4 Important > - CVE-2026-11770 <https://access.redhat.com/security/cve/CVE-2026-11770> - > 7.5 Moderate > - CVE-2026-18355 <https://access.redhat.com/security/cve/CVE-2026-18355> - > 7.5 Important > - CVE-2026-18453 <https://access.redhat.com/security/cve/CVE-2026-18453> - > 7.5 Important > - CVE-2026-76560 <https://access.redhat.com/security/cve/CVE-2026-76560> - > 7.5 Important > - CVE-2026-9064 <https://access.redhat.com/security/cve/CVE-2026-9064> - > 7.5 Important > > Please treat this as a critical security update. Review your installed > version and upgrade to the latest applicable release as soon as possible. > > Regards, > The 389 Directory Server team > -- > _______________________________________________ > 389-users mailing list -- 389-users@lists.fedoraproject.org > To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org > Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new -- Bryan K. Walton 319-337-3877 Senior Linux Systems Administrator Leepfrog Technologies, Inc -- _______________________________________________ 389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
[fedora-arm] Re: Latest brcmfmac breaks RPI5 wifi
> It does & did connect to an Android 16 AP/hotspot. > > It also connects to my AP in what it calls compatibility mode, which I think must just be WPA1. No, it's not, it's a transition mode somewhere between WPA2 and WAP3. > After upgrading to your (Peter's): > > Linux nas6 7.2.5-300.pr3.fc45.aarch64 #1 SMP PREEMPT_DYNAMIC Fri Sep 11 20:30:22 UTC 2026 aarch64 GNU/Linux > > I can now connect to LEGGWLAN: There's nothing in there that would affect brcmfmac that's not in the upstream kernels so that mostly just tells me that the issue is environmental. > On an RPI5 with latest F45 stuff, I get this many channels listed: That's not channel, that's SSIDs. > However, on an RPI4 with the latest F45 stuff, I get roughly twice as many. Are they in the same location? In the same case etc? Overall WPA3 isn't currently supported upstream with the old firmware on brcmfamc, the new firmware brings in some changes that will eventually allow WPA3 to work on upstream (ie Fedora and other distos) platforms, but we are not there yet. There's a number of sub standards that are required, or in some case optional, for WPA3 support and like all things that require interoperability different companies have different opinions on what those requirements are. Some of these are firmware related, some a kernel, and some are userspace (NM, wpa_supplicant, possibly other bits) and there's a number of bits still in flux. The SAE (Simultaneous Authentication of Equals) component of of WPA3 which does the auth has a number of options (NnP - Hunt and Peck, H2E - Hash 2 Element). Some APs only enable one or the other of HnP or H2E, similarly some clients also only support one. Digging into this generally it's fragile as hell in brcmfmac (I have tried a number of times over the years to make WPA3 work on brcmfmac) but also generally. I think there's still some work to happen here, the new firmware at least unlocks the vendor side of things. Peter > Thanks for your help. > > :D > > > On 12/09/2026 10:57, Peter Robinson wrote: > > Does it connect to a mobile AP from your phone? > > On Sat, 12 Sept 2026 at 10:48, David Legg <dwlegg@gmail.com> wrote: > > My other RPI5 running latest F43 can see both wifi ranges: > > nmcli device wifi list > IN-USE BSSID SSID MODE CHAN RATE SIGNAL BARS SECURITY > * 3C:58:36:2B:A2:E4 LEGGWLAN Infra 1 195 Mbit/s 87 ▂▄▆█ WPA2 WPA3 > 92:58:36:2B:A2:E7 LEGGGUEST Infra 1 195 Mbit/s 87 ▂▄▆█ -- > 92:58:36:2B:A2:E8 -- Infra 1 195 Mbit/s 85 ▂▄▆█ WPA3 > 92:58:36:2B:A2:E5 EE WiFi Infra 1 195 Mbit/s 85 ▂▄▆█ -- > BE:0F:F3:4B:60:97 DIRECT-97-HP OfficeJet Pro 9730e Infra 6 65 Mbit/s 84 ▂▄▆█ WPA2 > 3C:58:36:2B:A2:E3 LEGGWLAN Infra 36 540 Mbit/s 75 ▂▄▆_ WPA2 WPA3 > 8E:58:36:2B:A2:E7 -- Infra 36 540 Mbit/s 75 ▂▄▆_ WPA3 > 8E:58:36:2B:A2:E4 EE WiFi Infra 36 540 Mbit/s 75 ▂▄▆_ -- > 8E:58:36:2B:A2:E6 LEGGGUEST Infra 36 540 Mbit/s 75 ▂▄▆_ -- > > The top 5 are shown in green, the bottom ones in red. The red ones are the 5Ghz ones aren't they? > > > On 12/09/2026 10:31, Peter Robinson wrote: > > But does it? None of your LEGG show up in the 5ghz range? -- _______________________________________________ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
[fedora-arm] Re: Latest brcmfmac breaks RPI5 wifi
It does & did connect to an Android 16 AP/hotspot.
It also connects to my AP in what it calls compatibility mode, which I think must just be WPA1.
Other interesting developments:
After upgrading to your (Peter's):
Linux nas6 7.2.5-300.pr3.fc45.aarch64 #1 SMP PREEMPT_DYNAMIC Fri Sep 11 20:30:22 UTC 2026 aarch64 GNU/Linux
I can now connect to LEGGWLAN:
# nmcli device wifi connect LEGGWLAN
Device 'wlan0' successfully activated with 'c348159a-8ff0-3993-98a9-a7f26a906cad'.
and a phone AP (moto g75 5G_3501) and the EE AP in compatibility mode (LEGGWLANCOMPATIBLE).
On an RPI5 with latest F45 stuff, I get this many channels listed:
# nmcli device wifi list
IN-USE BSSID SSID MODE BAND CHAN RATE SIGNAL BARS SECURITY
06:34:42:1B:59:18 moto g75 5G_3501 Infra 2.4 GHz 11 1170 Mbit/s 100 ▂▄▆█ WPA2 WPA3
BE:0F:F3:4B:60:97 DIRECT-97-HP OfficeJet Pro 9730e Infra 2.4 GHz 6 65 Mbit/s 97 ▂▄▆█ WPA2
92:58:36:2B:A2:E5 EE WiFi Infra 2.4 GHz 1 195 Mbit/s 79 ▂▄▆_ --
92:58:36:2B:A2:E7 LEGGGUEST Infra 2.4 GHz 1 195 Mbit/s 79 ▂▄▆_ --
92:58:36:2B:A2:E9 LEGGWLANCOMPATIBLE Infra 2.4 GHz 1 195 Mbit/s 77 ▂▄▆_ WPA1 WPA2
8E:58:36:2B:A2:E7 -- Infra 5 GHz 36 540 Mbit/s 69 ▂▄▆_ WPA3
EC:FD:F8:22:51:EE AP_2361625852 Infra 2.4 GHz 1 135 Mbit/s 67 ▂▄▆_ WPA2
3C:58:36:2B:A2:E3 LEGGWLAN Infra 5 GHz 36 540 Mbit/s 67 ▂▄▆_ WPA2 WPA3
8E:58:36:2B:A2:E4 EE WiFi Infra 5 GHz 36 540 Mbit/s 67 ▂▄▆_ --
8E:58:36:2B:A2:E6 LEGGGUEST Infra 5 GHz 36 540 Mbit/s 67 ▂▄▆_ --
* 3C:58:36:2B:A2:E4 LEGGWLAN Infra 2.4 GHz 1 195 Mbit/s 66 ▂▄▆_ WPA2 WPA3
58:D6:1F:C8:D3:31 CHEEKYCP Infra 5 GHz 48 1170 Mbit/s 39 ▂▄__ WPA2 WPA3
However, on an RPI4 with the latest F45 stuff, I get roughly twice as many.
Thanks for your help.
:D
Does it connect to a mobile AP from your phone? On Sat, 12 Sept 2026 at 10:48, David Legg <dwlegg@gmail.com> wrote:My other RPI5 running latest F43 can see both wifi ranges: nmcli device wifi list IN-USE BSSID SSID MODE CHAN RATE SIGNAL BARS SECURITY * 3C:58:36:2B:A2:E4 LEGGWLAN Infra 1 195 Mbit/s 87 ▂▄▆█ WPA2 WPA3 92:58:36:2B:A2:E7 LEGGGUEST Infra 1 195 Mbit/s 87 ▂▄▆█ -- 92:58:36:2B:A2:E8 -- Infra 1 195 Mbit/s 85 ▂▄▆█ WPA3 92:58:36:2B:A2:E5 EE WiFi Infra 1 195 Mbit/s 85 ▂▄▆█ -- BE:0F:F3:4B:60:97 DIRECT-97-HP OfficeJet Pro 9730e Infra 6 65 Mbit/s 84 ▂▄▆█ WPA2 3C:58:36:2B:A2:E3 LEGGWLAN Infra 36 540 Mbit/s 75 ▂▄▆_ WPA2 WPA3 8E:58:36:2B:A2:E7 -- Infra 36 540 Mbit/s 75 ▂▄▆_ WPA3 8E:58:36:2B:A2:E4 EE WiFi Infra 36 540 Mbit/s 75 ▂▄▆_ -- 8E:58:36:2B:A2:E6 LEGGGUEST Infra 36 540 Mbit/s 75 ▂▄▆_ -- The top 5 are shown in green, the bottom ones in red. The red ones are the 5Ghz ones aren't they? On 12/09/2026 10:31, Peter Robinson wrote: But does it? None of your LEGG show up in the 5ghz range?
-- _______________________________________________ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
[Test-Announce] Test Days: KDE Plasma 6.7
Please join us for upcoming Test Days and help us improve Fedora's quality and stability.
Your participation helps us find and fix bugs before the next release, ensuring a smoother experience for all users.
This time we'll focus on testing KDE Plasma 6.7.
You'll install Fedora from the provided test image and report your test results along with your hardware configuration.
Test period: 2026-09-14 to 2026-09-20
Test instructions: https://fedoraproject.org/wiki/Test_Day:2026-09-14_KDE_Plasma_6.7
Thank you for your contributions!
Jaroslav Groman
Fedora Quality
-- _______________________________________________ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-announce@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new