See https://bugzilla.redhat.com/show_bug.cgi?id=2271547 . Apparently other applications will run automatically as a Startup Application (I tried Aisleriot), but not gnome-terminal. Don't know if this violates any Final criteria, posting here to get more attention since I wasn't even sure what component to file under.
Performing kernel regression tests:
https://fedoraproject.org/wiki/QA:Testcase_kernel_regression
I am getting errors submitting as follows:
Your log file is being submitted...
FAS password:
Traceback (most recent call last):
File "/root/kernel-tests/./fedora_submit.py", line 43, in <module>
submitclient.login(
File
"/usr/lib/python3.12/site-packages/fedora/client/openidbaseclient.py",
line 303, in login
response = openid_login(
^^^^^^^^^^^^^
File
"/usr/lib/python3.12/site-packages/fedora/client/openidproxyclient.py",
line 138, in openid_login
raise AuthError(output['message'])
fedora.client.AuthError: Invalid request
This is new [for me] from today. Is this a known issue or is it just me?
Ian
--
Ian Laurie
FAS: nixuser | IRC: nixuser
TZ: Australia/Sydney
Hi guys!
I upgraded my F39 (Workstation) to the most recent F40 Beta without any
problems.
Now, I tried to perform an update of this F40 by dnf, but this process
fails with ot lot of failures.
For details, see the attached file
Kind Regards
Joachim Backes
--
Fedora release 40 (Forty)
6.8.1-300.fc40.x86_64
Joachim Backes <joachim.backes(a)rhrk.uni-kl.de>
https://www-user.rhrk.uni-kl.de/~backes/
# F40 Blocker Review meeting
# Date: 2024-03-25
# Time: 16:00 UTC
# Location:
https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.…
Hi folks! It's time for another blocker review meeting. We have 3
proposed blockers for Final.
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+40+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 today, 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 F40 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 day and see you tomorrow!
[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
Hey Folks!
Fedora 40 is going to ship with Podman 5[0] and as part of this changeset,
there will be a lot of breaking changes which can affect your
container workflow.
To ensure a smooth transition, the Podman team and the Quality team of
Fedora have
decided to host a test week[1].
The idea is for users to test Podman 5 on a Fedora 40 Pre-release machine
and submit results in the Test Day App[2]. If you have spare cycles or use
Podman as a daily driver, it will be
great to have some folks try out and report bugs right away.
[0] https://fedoraproject.org/wiki/Changes/Podman5
[1] https://fedoraproject.org/wiki/Test_Day:2024-03-21_Podman_5
[2] https://testdays.fedoraproject.org/events/183
--
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED
Dear Fedora Community Member,
We are excited to invite you to participate in an upcoming Fedora Test
Day focused on testing Podman Desktop. Podman Desktop is an innovative
tool that enables you to manage containers on your desktop with ease.
Date: 2024-03-20
Your feedback and testing are invaluable in ensuring the stability and
functionality of Podman Desktop. By participating, you'll have the
opportunity to:
Test Podman Desktop in various scenarios on your system.
Identify and report bugs, issues, or improvements.
Collaborate with fellow Fedora enthusiasts and developers.
No prior testing experience is necessary. Whether you're a seasoned
tester or new to the process, your contributions are highly valued.
If you're interested in joining us for this Test Day, please reply to
this email or sign up on the Fedora Wiki page[0]. Feel free to reach
out if you have any questions or need assistance getting started.
Thank you for your dedication to improving Fedora, and we look forward
to your participation!
Best regards,
[0] http://fedoraproject.org/wiki/Test_Day:2024-03-20_Podman_Desktop
--
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED
On Tue, 2024-03-19 at 05:58 +0000, rawhide(a)fedoraproject.org wrote:
> According to [the schedule][1], Fedora 40 Candidate Beta-1.8 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/40
>
> 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_40_Beta_1.8_Summary
Note on this: a 1.9 will be coming which should be identical to 1.8
except with Cinnamon and Budgie fixed (they were broken by the GNOME 46
FE in 1.8, and their images are missing). Testing on 1.8 is still
useful and can mostly be transferred to 1.9, but you might want to wait
6-7 hours for 1.9 to show up before starting testing.
--
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org
https://www.happyassassin.net
Dear Fedorans,
Are you ready to make a difference in the world of Fedora Linux? We're
thrilled to announce the launch of our brand new test day series:
Rawhide Test Days! These events are your opportunity to play a crucial
role in ensuring the quality and reliability of upcoming Fedora
releases. Rawhide test days will play their unique role in keeping
Fedora Linux releases on time.
Fedora test days are renowned for their inclusivity – they welcome
participation from both seasoned Fedora contributors and newcomers
alike. If you've been itching to dip your toes into the world of
Fedora Linux contribution, this is your perfect starting point.
For some time now, we've been dedicated to elevating the quality
standards of Fedora by implementing rigorous testing processes well in
advance. Our Fedora Changes process facilitates the submission of
changesets long before the official release cycle begins. As part of
this effort, we're excited to introduce Rawhide Test Days, an
initiative designed to test these changesets thoroughly and identify
any potential (blocker) bugs early on.
To kick off this exciting journey, we're focusing our efforts on
testing DNF 5 – a crucial changeset proposed for Fedora Linux 41[0].
With the introduction of the brand new DNF5 package in Rawhide, we're
organizing a test days to gather initial feedback before it becomes
the default. We'll be rigorously testing DNF5 against its basic
acceptance criteria to ensure a seamless transition.
Mark your calendars for our Rawhide Test Days, taking place from
Friday, March 15th, through Tuesday, March 19th. Your participation
during this week will be invaluable as we work together to refine
Fedora Linux for its upcoming release.
Ready to dive in? Visit our test week page [1] to learn more about how
you can contribute and make your mark on the future of Fedora.
Happy testing, and we can't wait to see you there!
Best regards,
//sumantro
[0] https://fedoraproject.org/wiki/Changes/ReplaceDnfWithDnf5
[1] http://fedoraproject.org/wiki/Test_Day:2024-03-15_Fedora_40_DNF_5
--
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED
=====================================
# #meeting:fedoraproject.org: Quality
=====================================
Meeting started by @adamwill:fedora.im at 2024-03-18 15:00:41
Meeting summary
---------------
* TOPIC: Roll Call (@adamwill:fedora.im, 15:00:46)
* TOPIC: Previous meeting follow-up (@adamwill:fedora.im, 15:06:33)
* INFO: no action items from last meeting (@adamwill:fedora.im,
15:06:50)
* TOPIC: Fedora 40 status (including Beta testing plans)
(@adamwill:fedora.im, 15:07:37)
* INFO: Beta-1.7 is, so far, looking like a viable candidate, much
better than anything we had last week (@adamwill:fedora.im, 15:08:14)
* INFO: dustymabe had worrying results with the new shim in CoreOS
testing - https://github.com/coreos/fedora-coreos-tracker/issues/1694
(@adamwill:fedora.im, 15:08:45)
* INFO: there are some significant known differences in the
contents of at least one image now built by kiwi but formerly built by
imagefactory - the container base image built with kiwi is missing gzip
and sudo - and we haven't yet checked the others out fully (thanks
Jeremy Linton for checking container base) (@adamwill:fedora.im,
15:09:56)
* INFO: it seems sdubby may be getting installed instead of grubby
in far too many cases -
https://bugzilla.redhat.com/show_bug.cgi?id=2269992
(@adamwill:fedora.im, 15:10:22)
* INFO: there's an update for GNOME 46 final builds of the core
components (gnome-shell etc.) that we *may* want to pull in as an FE
(@adamwill:fedora.im, 15:11:15)
* INFO: travier wants to revert bootupd again -
https://pagure.io/workstation-ostree-config/pull-request/498
(@adamwill:fedora.im, 15:11:42)
* INFO: there is also a report of basic graphics mode not working -
https://bugzilla.redhat.com/show_bug.cgi?id=2270128
(@adamwill:fedora.im, 15:18:56)
* INFO: the pi 400 blocker is still outstanding -
https://bugzilla.redhat.com/show_bug.cgi?id=2267968 . We did the
candidate compose on the theory folks may want to waive it, but we
should still try and get it fixed (@adamwill:fedora.im, 15:24:31)
* TOPIC: Test Day / community event status (@adamwill:fedora.im,
15:39:49)
* INFO: Fedora IoT test week is this week:
https://fedoraproject.org/wiki/Test_Day:2024-03-18_Fedora_40_IoT_Edition#Pr…
and https://testdays.fedoraproject.org/events/178 (@adamwill:fedora.im,
15:41:21)
* INFO: Podman Desktop test day with be 2024-03-20:
https://fedoraproject.org/wiki/Test_Day:2024-03-20_Podman_Desktop
(@adamwill:fedora.im, 15:42:43)
* INFO: Podman 5 test day will be 2024-03-21:
https://fedoraproject.org/wiki/Test_Day:2024-03-21_Podman_5
(@adamwill:fedora.im, 15:42:56)
* INFO: Toolbx test day will be 2024-03-27:
https://fedoraproject.org/wiki/Test_Day:2024-03-27_Toolbx
(@adamwill:fedora.im, 15:43:13)
* TOPIC: Open floor (@adamwill:fedora.im, 15:47:20)
Meeting ended at 2024-03-18 15:53:46
Action items
------------
People Present (lines said)
---------------------------
* @adamwill:fedora.im (49)
* @nielsenb:fedora.im (13)
* @kparal:matrix.org (9)
* @geraldosimiao:matrix.org (9)
* @nhanlon:beeper.com (5)
* @zodbot:fedora.im (4)
* @meetbot:fedora.im (2)
* @tflink:fedora.im (2)
--
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org
https://www.happyassassin.net