On Tue, Sep 21, 2021 at 7:00 AM <bcotton(a)redhat.com> wrote:
>
> You are kindly invited to the meeting:
> Prioritized bugs and issues on 2021-09-22 from 11:00:00 to 12:00:00 America/Indiana/Indianapolis
> At fedora-meeting-1(a)libera.chat
>
> More information available at: https://docs.fedoraproject.org/en-US/program_management/prioritized_bugs/
>
We will evaluate the following nominated bugs:
* Screen stays black after suspend / logout when used on amd apu
laptop. — https://bugzilla.redhat.com/show_bug.cgi?id=1988528
There are no currently-accepted bugs.
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
This is related to bug 2003253 [1]. As reported in comment 1, our current
"Keyboard layout configuration" criterion [2] specifies where the
configured keyboard layout must be honored. It doesn't specify the initial
setup utility, which seems like a clear omission, because in that utility
you create your system user, connect to wifi, etc, so a correct keyboard
layout is definitely important, and is in line with all the other places
specified.
I propose to edit the existing criterion and add the following (probably as
the second bullet point):
* In the "initial setup" utility (if applicable)
So the final wording would be:
~~~~
If a particular keyboard layout has been configured for the system, that
keyboard layout must be used:
* When unlocking encrypted storage volumes during boot (but see footnotes)
* In the "initial setup" utility (if applicable)
* When logging in at a console
* When logging in via the default login manager for a release-blocking
desktop
* After logging in to a release-blocking desktop, if the user account does
not have its own keyboard layout configuration for that desktop (if there
is such a user/desktop-specific configuration, it must be used when that
user logs in to that desktop)
~~~~
Please comment, thank you.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=2003253
[2]
https://fedoraproject.org/wiki/Fedora_35_Final_Release_Criteria#Keyboard_la…
No missing expected images.
Soft failed openQA tests: 1/8 (x86_64), 1/8 (aarch64)
(Tests completed, but using a workaround for a known bug)
Old soft failures (same test soft failed in Fedora-Cloud-34-20210920.0):
ID: 993330 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://openqa.fedoraproject.org/tests/993330
ID: 993338 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi
URL: https://openqa.fedoraproject.org/tests/993338
Passed openQA tests: 7/8 (x86_64), 7/8 (aarch64)
--
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
No missing expected images.
Soft failed openQA tests: 1/8 (x86_64), 1/8 (aarch64)
(Tests completed, but using a workaround for a known bug)
Old soft failures (same test soft failed in Fedora-Cloud-33-20210920.0):
ID: 993314 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://openqa.fedoraproject.org/tests/993314
ID: 993322 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi
URL: https://openqa.fedoraproject.org/tests/993322
Passed openQA tests: 7/8 (x86_64), 7/8 (aarch64)
--
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
==================================
#fedora-meeting: Fedora QA meeting
==================================
Meeting started by adamw at 15:01:05 UTC. The full logs are available at
fedora-meeting/2021-09-20/fedora-qa.2021-09-20-15.01.log.html .
Meeting summary
---------------
* Roll Call (adamw, 15:01:13)
* tap tap tap is this thing on? (adamw, 15:04:03)
* Previous meeting follow-up (adamw, 15:09:53)
* "adamw to figure out exact current state of pipewire session manager
stuff (fresh install vs. upgrade, wireplumber vs. 'example session
manager'" - that all got squared away a week or two back, it's all
tested to be correct now (adamw, 15:12:27)
* Fedora 35 status (adamw, 15:14:41)
* overall, fedora 35 is in 'quite good' state right now. we missed the
early date and the first real target date for beta, we've got
another shot for go/no-go on thursday. the blocker list is getting
small but not empty yet. in general things are mostly working
(adamw, 15:19:00)
* Startup time criteria (adamw, 15:23:07)
* ACTION: adamw to draft vaguer and more general startup time
criterion (but not too vague) (adamw, 15:30:31)
* Test Day / community event status (adamw, 15:31:25)
* kernel 5.14 test week ran successfully last week -
https://pagure.io/fedora-qa/issue/680 (adamw, 15:36:46)
* audio test day ran successfully too -
https://pagure.io/fedora-qa/issue/678 (adamw, 15:37:11)
* GNOME test week also ran last week (busy week!) -
https://pagure.io/fedora-qa/issue/670 (adamw, 15:39:07)
* Open floor (adamw, 15:44:13)
Meeting ended at 15:58:49 UTC.
Action Items
------------
* adamw to draft vaguer and more general startup time criterion (but not
too vague)
Action Items, by person
-----------------------
* adamw
* adamw to draft vaguer and more general startup time criterion (but
not too vague)
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* adamw (70)
* zodbot (19)
* bcotton (15)
* nirik (6)
* frantisekz (5)
* cmurf[m] (5)
* StephenGallagher (5)
* tflink (3)
* coremodule (3)
* kk4ewt[m] (2)
* jforbes (2)
* pwhalen (1)
Generated by `MeetBot`_ 0.3
.. _`MeetBot`: http://wiki.debian.org/MeetBot
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net