test March 2025

test@lists.fedoraproject.org

15 participants
15 discussions

F41 => F42 upgrade report
by old sixpack13 16 Mar '25

16 Mar '25

upgrade went smooth Thanks a few minor things so far: - selinux error gnome shell - homebrewed kernel 6.13.7 does not compile, but 6.14.0-rc6 does compile lot of [-Wunterminated-string-initialization]- errors tried gcc-15.0.1-0.10 too

2 1

2025-03-17 @ **16:00** UTC - Fedora 42 Blocker Review Meeting
by Adam Williamson 15 Mar '25

15 Mar '25

# F42 Blocker Review meeting # Date: 2025-03-17 # Time: **16:00** UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.… Hi folks! It's time for a Fedora 42 blocker review meeting! We have 5 proposed blockers for Final. Note that as clocks went forward in North America recently, the meeting is now at 1600 UTC. If you changed your clocks recently, the meeting will be at the same local time as before. If you didn't, the meeting will be an hour earlier in your local time. Here is a handy link which should show you the meeting time in your local time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+41+Blocker… The meeting will be on Matrix. Click the link above to join in a web client - you can authenticate with your FAS account - or use a dedicated client of your choosing. If you have time this weekend, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F42 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good weekend and see you on Monday! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org https://www.happyassassin.net

1 0

2025-03-17 @ **15:00** UTC - Fedora Quality Meeting
by Adam Williamson 15 Mar '25

15 Mar '25

# Fedora Quality Assurance Meeting # Date: 2025-03-17 # Time: **15:00** UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: https://matrix.to/#/#meeting:fedoraproject.org?web-instance[element.io]=cha… Greetings testers! It's meeting time again. Note that clocks went forward in North America since the last meeting, so the meeting will be an hour earlier in UTC. If you set your clocks forward recently, the meeting will be at the same local time as before. If you did not, it will be an hour earlier. Here is a handy link which should show you the meeting time in your local time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+quality+me… If anyone has any other items for the agenda, please reply to this email and suggest them! Thanks. == Proposed Agenda Topics == 1. Previous meeting follow-up 2. Fedora 42 status, Beta release pre-flight check 3. Test Day / community event status 4. Open floor -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org https://www.happyassassin.net

1 0

https://fedoraproject.org/wiki/QA:Testcase_partitioning_custom_btrfs_preserve_home needs updating
by Andre Robatino 14 Mar '25

14 Mar '25

The wiki page above still says not to use WebUI, so needs to be updated for F42. Yet strangely, automated tests for this in the Test Matrix are passing. I'm not sure how or what they're testing. I haven't looked at the installer recently, is it obvious now how to preserve /home?

3 3

Fedora 42 Beta-1.4 Xfce Live didn't ask to create user
by Ian Laurie 12 Mar '25

12 Mar '25

Using the Beta 1.4 Xfce Live, the initial setup utility didn't run, and no regular user was set up. I did enable the root account during the install, but as I understand it that should not have prevented the initial setup utility from running. -- Ian Laurie FAS: nixuser | IRC: nixuser TZ: Australia/Sydney

1 0

Self-Introduction: Austin P.
by Austin Pauley 12 Mar '25

12 Mar '25

Hi All, My name is Austin (FAS: austin2118ace), and I am looking to become involved in the QA process for Fedora. I'm a data scientist / research technician in academia, and I interact with Fedora (and other linux distros) on the daily. While I'm not an expert, I can hold my own and learn quickly. I initially learned on Ubuntu, but have switched to Fedora for all my daily needs as I find its more robust and compatable with most things I use. I'm looking forward to getting involved! Best, Austin

1 0

Re: [Test-Announce]Fedora 42 Candidate Beta-1.3 Available Now!
by Kamil Paral 12 Mar '25

12 Mar '25

On Tue, Mar 11, 2025 at 4:48 PM rawhide via test-announce < test-announce(a)lists.fedoraproject.org> wrote: > According to [the schedule][1], Fedora 42 Candidate Beta-1.3 is now > available for testing. Please help us complete all the validation > testing! For more information on release validation testing, see: > https://fedoraproject.org/wiki/QA:Release_validation_test_plan > > Test coverage information for the current release can be seen at: > https://openqa.fedoraproject.org/testcase_stats/42 > > 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_42_Beta_1.3_Summary Please note that an existing blocker [1] wasn't fixed, most probably because the compose process used an older lorax. So there will be a new RC. However, testing RC1.3 is still valuable, because it contains newer mesa, which can affect especially desktop apps. So please help us with desktop tests in RC1.3 and we can then pull them into RC1.4 (and installation tests can be taken from RC1.2, mostly). Thanks! [1] https://bugzilla.redhat.com/show_bug.cgi?id=2350605

1 0

Unsubscription
by lz843723683 09 Mar '25

09 Mar '25

1 0

Edge case issues
by Scott Robbins 09 Mar '25

09 Mar '25

I installed F42 from the nightly builds last night. I almost always choose a minimal install and build from there. I ran into two issues, both of which I guess are edge cases, since I suspect most people use one of the included desktops. But I tend to install openbox. The first issue is that I found there is no longer a tint2 rpm. Tint2 is a panel that goes well with openbox. I guess I've been upgrading various installs which is why I didn't notice that there hasn't been a tint2 rpm in a while. (The last I found was from F39, on rpmfind). It installed on the F42 with no problems. The second issue is the alacritty terminal. I installed from rpm which seemed fine, but when I tried to open it, I got a message of thread 'main' panicked at /usr/share/cargo/registry/xkbcommon-dl-0.4.2/src/x11.rs:59:28: Library libxkbcommon-x11.so could not be loaded. note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace When I tried installing from its github version, the message was similar just a different location for the panic. thread 'main' panicked at /home/scottro/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/xkbcommon-dl-0.4.2/src/x11.rs:59:28: Library libxkbcommon-x11.so could not be loaded. note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace I'm not sure if it merits a bugzilla or not, especially because, as mentioned above, most people will probably use one of the preconfigured desktops and all the desktops have their own terminals, e.g. whatever gnome uses now, xfce4-terminaal, etc. -- Scott Robbins PGP keyID EB3467D6 ( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 ) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6

3 7

2025-03-10 @ **16:00** UTC - Fedora 42 Blocker Review Meeting
by Adam Williamson 09 Mar '25

09 Mar '25

# F42 Blocker Review meeting # Date: 2025-03-10 # Time: **16:00** UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.… Hi folks! It's time for a Fedora 42 blocker review meeting! We have 4 proposed blockers and 3 proposed freeze exceptions for Beta, and 2 proposed blockers for Final. Note that as clocks went forward in North America this weekend, the meeting is now at 1600 UTC. If you changed your clocks this weekend, the meeting will be at the same local time as before. If you didn't, the meeting will be an hour earlier in your local time. Here is a handy link which should show you the meeting time in your local time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+41+Blocker… The meeting will be on Matrix. Click the link above to join in a web client - you can authenticate with your FAS account - or use a dedicated client of your choosing. If you have time this weekend, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F42 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good weekend and see you on Monday! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org https://www.happyassassin.net

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

test March 2025