Hey folks!
It'd be really great if anyone who has an Intel Mac that's safe for
experimenting on can try doing a dual-boot install of Fedora 38 on it.
Our (the RH Fedora QA team) initial test of this had an issue where no
option to boot macOS could be found after the Fedora install; a repeat
test didn't show the same problem, but it would be great to have tests
from other folks to verify it was just a one-time blip.
Obviously don't try this on a Mac you really need to keep working, or
which you don't know how to recover if it does get messed up.
Thanks a lot!
--
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org
https://www.happyassassin.net
We've branched F38 from Rawhide, so it's time to start everyone's
favorite Friday email from Ben! The F38 Beta freeze begins on 21
February. The current target release date is the early target date
(2023-03-14).
Action summary
====================
Accepted blockers
-----------------
1–3. distribution — {Workstation,Everything,Server} boot x86_64 image
exceeds maximum size — ASSIGNED
ACTION: Relevant Teams to reduce image size or increase the limit
Proposed blockers
-----------------
1. anaconda — installer fails to boot in text mode or rescue mode with
systemd 253 — MODIFIED
ACTION: Maintainers to build an update that includes upstream PR
2. grub2 — ext4 filessystem support missing — NEW
ACTION: Maintainer to diagnose issue
NEEDINFO: ausil
3. kwin — kwin_wayland often crashed when used as the sddm Wayland
compositor and logging out of Plasma resulting in a black screen — NEW
ACTION: Maintainer to diagnose issue
4. mesa — KDE crashes on start with mesa-23.0.0~rc3-3.fc38 — ASSIGNED
ACTION: Maintainer to diagnose issue
Bug-by-bug detail
=============
Accepted blockers
-----------------
1–3. distribution — {Workstation,Everything,Server} boot x86_64 image
exceeds maximum size — ASSIGNED
https://bugzilla.redhat.com/show_bug.cgi?id=2149246https://bugzilla.redhat.com/show_bug.cgi?id=2151495https://bugzilla.redhat.com/show_bug.cgi?id=2151497
Image sizes exceed the specified limits. The choices are to either
shrink the image by removing packages or to riase the limits.
Proposed blockers
-----------------
1. anaconda — https://bugzilla.redhat.com/show_bug.cgi?id=2165433 — MODIFIED
installer fails to boot in text mode or rescue mode with systemd 253
anaconda is writing systemd units to an unexpected area. Upstream PR
4534 contains a candidate fix:
https://github.com/rhinstaller/anaconda/pull/4534
2. grub2 — https://bugzilla.redhat.com/show_bug.cgi?id=2166412 — NEW
ext4 filessystem support missing
Between grub2-2.06-76 and grub2-2.06-78, grub2 apparently lost the
ability to detect ext4 filesystems.
3. kwin — https://bugzilla.redhat.com/show_bug.cgi?id=2168034 — NEW
kwin_wayland often crashed when used as the sddm Wayland compositor
and logging out of Plasma resulting in a black screen
Logging out of Plasma sometimes triggers a kwin crash. This may be
limited to running in a virtual machine.
4. mesa — https://bugzilla.redhat.com/show_bug.cgi?id=2164667 — ASSIGNED
KDE crashes on start with mesa-23.0.0~rc3-3.fc38
A recent mesa update caused both GNOME and KDE to crash on start.
Update FEDORA-2023-40b973fa06 fixed GNOME, but KDE is still seeing
this issue. The root cause is still uncertain.
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
==================================
#fedora-meeting: Fedora QA meeting
==================================
Meeting started by adamw at 15:00:38 UTC. The full logs are available at
https://meetbot.fedoraproject.org/fedora-meeting/2023-04-03/fedora-qa.2023-…
.
Meeting summary
---------------
* Roll Call (adamw, 15:00:48)
* Previous meeting follow-up (adamw, 15:06:32)
* "adamw to read up on how the matrix/irc bridging works for topic
setting, and get sumantro appropriate rights to set topics on both
sides in the test day channel" - i did this, sadly topic bridging
doesn't work in either direction, you have to set it manually on
both sides. I mailed sumantro some info on what he needs to set it
on IRC (adamw, 15:07:41)
* "adamw to check in with sumantro on status of iot and coreos test
weeks" - i did that, and both are in fact live now (coreos is just
ending, iot is starting) (adamw, 15:08:46)
* Window manager release criterion proposal (adamw, 15:11:18)
* kparal sent out an updated proposal:
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/…
(adamw, 15:11:57)
* the window management criterion proposal gathers strong indifference
and/or support (adamw, 15:18:56)
* Fedora 38 status (adamw, 15:19:25)
* current status is fairly good, blocker list is short and being
worked on (adamw, 15:20:02)
* final freeze is tomorrow (adamw, 15:20:07)
* not all validation tests have been run yet, if folks can help run
the missing tests on current nightly candidate composes that would
be great (adamw, 15:20:34)
* Test Day / community event status (adamw, 15:29:29)
* IoT test day is just starting:
http://fedoraproject.org/wiki/Test_Day:2023-04-03_Fedora_38_IoT_Edition
(adamw, 15:31:35)
* CoreOS test day is wrapping up:
http://fedoraproject.org/wiki/Test_Day:Fedora_38_CoreOS (adamw,
15:31:56)
* Upgrade Test Day happened last week:
http://fedoraproject.org/wiki/Test_Day:2023-03-28_F38_Upgrade_Test_Day
- thanks to everyone who tested (adamw, 15:32:38)
* Open floor (adamw, 15:35:07)
Meeting ended at 15:46:55 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* adamw (57)
* zodbot (11)
* geraldosimiao (8)
* rishi (4)
* kparal (4)
* coremodule (3)
* bcotton (3)
* lruzicka (3)
* rishi[m] (1)
* marcdeop[m] (1)
Generated by `MeetBot`_ 0.4
.. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions
--
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org
https://www.happyassassin.net
Related to a recently proposed blocker [1][2], I propose a new release
criterion which would cover such cases. Here it is:
~~~~~~~~~~~~
The desktop environment must work correctly when displaying common
application content - that includes regular application windows, video
output, games and possibly other common content. Regular operations like
windows close/resize/maximize/minimize/fullscreen (when
supported/applicable), windows switching, using windows on virtual
workspaces, and similar common operations must behave as expected.
Footnote - "What does this cover?":
A small number of misbehaving applications is not a violation of this
criterion. The goal of this criterion is to ensure general functionality
for different types of applications and their operations. An example of a
violation would be e.g. if a significant number of QT applications couldn't
be resized (but they should be), or if all Java applications failed to
display any content.
~~~~~~~~~~~~~
I think this criterion could target F38 Beta Release Criteria [3] or Basic
Release Criteria [4].
Please tell me your thoughts, thanks!
Kamil
[1] https://pagure.io/fedora-qa/blocker-review/issue/1102
[2] https://bugzilla.redhat.com/show_bug.cgi?id=2178167
[3] https://fedoraproject.org/wiki/Fedora_38_Beta_Release_Criteria
[4] https://fedoraproject.org/wiki/Basic_Release_Criteria
When I was testing the latest F38 nightly yesterday, I hit an issue when trying to use a kickstart to join an Active Directory domain at install time [1] and was able to regularly reproduce the issue. If this is reproducible, it's a pretty clear blocker and I filed it in rhbz:
- https://bugzilla.redhat.com/show_bug.cgi?id=2184223
Earlier today, I suddenly stopped being able to reproduce the issue and the other person who generally runs the AD tests has been unable to reproduce the issue at all.
If anyone has the available cycles, more reproduction attempts would be appreciated. I really don't like "this magically fixed itself" because those issues can resurface and if they do, it's usually at the worst possible time. To be clear, this test is against a windows active directory controller - the freeipa variant of the same test is run regularly by OpenQA and has shown no failures.
If you have questions about setting up a domain controller for testing, feel free to reach out here, direct email or IRC/Matrix.
Thanks,
Tim
[1] https://fedoraproject.org/wiki/QA:Testcase_realmd_join_kickstart
On Tue, Apr 4, 2023 at 6:00 AM <bcotton(a)redhat.com> wrote:
>
> You are kindly invited to the meeting:
> Prioritized bugs and issues on 2023-04-05 from 10:00:00 to 11:00:00 America/Indiana/Indianapolis
> At fedora-meeting-1(a)irc.libera.chat
>
> More information available at: https://docs.fedoraproject.org/en-US/program_management/prioritized_bugs/
> Source: https://calendar.fedoraproject.org//meeting/10144/
There are 0 nominated bugs and the 1 accepted bug is making progress,
so I am cancelling the Prioritized Bugs meeting. We'll meet again 19
April.
As a reminder, this process exists but it only works if you nominate
bugs. See https://docs.fedoraproject.org/en-US/program_management/prioritized_bugs/#_…
for the kinds of bugs to nominate.
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
# Fedora Quality Assurance Meeting
# Date: 2023-04-03
# Time: 15:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting on irc.libera.chat
Greetings testers!
It's meeting time again!
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. Window manager release criterion proposal
3. Fedora 38 status
4. Test Day / community event status
5. Open floor
--
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org
https://www.happyassassin.net