2022-04-25 @ 16:00 UTC - Fedora 36 Blocker Review Meeting
by Adam Williamson
# F36 Blocker Review meeting
# Date: 2022-04-25
# Time: 16:00 UTC
# Location: #fedora-blocker-review on irc.libera.chat
Hi folks! We don't currently have any blocker or FE bugs proposed, but
just in case any show up, let's schedule a review meeting on Monday. If
there still aren't any bugs to review shortly before the meeting, I'll
cancel it.
If you have time and any show up 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 F36 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
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
2 years
Re: F36 Final blocker status summary
by Ben Cotton
We are currently targeting the target date #1 (2022-04-26), which
means we'd want to have blockers fixed by 18 April in order to provide
time for validation testing prior to the Go/No-go meeting on 21 April.
Action summary
====================
Accepted blockers
-----------------
1. kf5-kirigami2 — The About button sends Discover into loop and the
application stops responding. — VERIFIED
ACTION: none
2. anaconda — "Installing software" and other strings displayed during
installation are untranslated — VERIFIED
ACTION: Matainers to package upstream patch
3. gnome-initial-setup — gnome-initial-setup hangs when I try to setup
a google/microsoft online account — ASSIGNED
ACTION: selinux-policy maintainers to package upstream PR
4. openssl — [tr_TR] curl: (35) error:03000072:digital envelope
routines::decode error with LANG=tr_TR.utf8 — NEW
ACTION: Maintainers to package upstream PR
5. container-selinux — selinux-policy is preventing flatpak from
updating / installing / removing flatpaks — NEW
ACTION: Maintainers to rebuild against updated selinux-policy packages
6. gnome-control-center — online accounts: can't disable sync on items — NEW
ACTION: Upstream to diagnose and fix issue
7. gnome-shell — interrupted dimming partly locks window switching — POST
ACTION: Maintainers to package upstream PR
8. fedora-repos — disable updates-testing, create a final release — VERIFIED
ACTION: none
9. gnome-software — Enabling "Fedora Flathub Selection" repo doesn't
show included apps in gnome-software until re-login — NEW
ACTION: Maintainers to package upstream MR
10. selinux-policy — After upgrade to F36 several packages fail to
update due to selinux-related errors — ASSIGNED
ACTION: container-selinux, osbuild, snapd, flatpak maintainers to
rebuild against latest selinux-policy
11. spin-kickstarts —
pyanaconda.modules.common.errors.installation.StorageInstallationError:
device is active — NEW
ACTION: KDE SIG to disable automount of storage devices in live image
Proposed blockers
-----------------
1. xorg-x11-server — Basic graphics mode broken for X11 with Nvidia
GPU and UEFI — NEW
ACTION: QA to verify upstream MR
Bug-by-bug detail
=============
Accepted blockers
-----------------
1. kf5-kirigami2 — https://bugzilla.redhat.com/show_bug.cgi?id=2057563
— VERIFIED
The About button sends Discover into loop and the application stops responding.
Clicking the About button causes a loop which renders Discover
unresponsive (except when the window is maximized). Fix verified in
FEDORA-2022-120719a555.
2. anaconda — https://bugzilla.redhat.com/show_bug.cgi?id=2071098 — VERIFIED
"Installing software" and other strings displayed during installation
are untranslated
Available translations are not displayed because LC_ALL was set in the
environment of DBus modules, overriding the value in LANG.
FEDORA-2022-92570f3943 contains a verified fix.
3. gnome-initial-setup —
https://bugzilla.redhat.com/show_bug.cgi?id=2071259 — ASSIGNED
gnome-initial-setup hangs when I try to setup a google/microsoft online account
Setting up a Google or Microsoft account causes g-i-s to apparently
hang, although tty switching works. This appears to be an SELinux
policy issue. https://github.com/fedora-selinux/selinux-policy/pull/1151
contains a candidate fix.
4. openssl — https://bugzilla.redhat.com/show_bug.cgi?id=2071343 — POST
[tr_TR] curl: (35) error:03000072:digital envelope routines::decode
error with LANG=tr_TR.utf8
curl coredumps when using the Turkish locale because of a string
comparison in OpenSSL that can't handle some unique character case
features in the Turkish alphabet. Upstream has a PR with a candidate
fix: https://github.com/openssl/openssl/pull/18069
5. container-selinux —
https://bugzilla.redhat.com/show_bug.cgi?id=2070764 — ON_QA
selinux-policy is preventing flatpak from updating / installing /
removing flatpaks
SELinux prevents flatpak from accessing a variety of
files/directories, including `/etc/passwd` and
`/var/lib/flatpak/exports/share`. This, in turn, prevents flatpak from
modifying flatpaks on the system. FEDORA-2022-ee2ba7ba12 contained a
fix for F36. container-selinux will need to be rebuilt against
selinux-policy-35.17-1.fc35 and selinux-policy-35.27-1.fc34 for
supported releases.
6. gnome-control-center —
https://bugzilla.redhat.com/show_bug.cgi?id=2068470 — NEW
online accounts: can't disable sync on items
Attempting to disable sync on items in Online Accounts appears to
succeed, but sync still shows as enabled on re-launch. Reported
upstream as https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1721
7. gnome-shell — https://bugzilla.redhat.com/show_bug.cgi?id=2073206 — POST
interrupted dimming partly locks window switching
Typing or using the mouse while the screen begins blanking results in
the screen being unresponsive to mouse input. Keyboard input still
works. Upstream PR for mutter contains a candidate fix:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2333
8. fedora-repos — https://bugzilla.redhat.com/show_bug.cgi?id=2073950 — VERIFIED
disable updates-testing, create a final release
FEDORA-2022-bda822f1ae contains a verified fix.
9. gnome-software — https://bugzilla.redhat.com/show_bug.cgi?id=2074121 — NEW
Enabling "Fedora Flathub Selection" repo doesn't show included apps in
gnome-software until re-login
You have to re-login or reboot to show applications from the filtered
Flathub repo. All other third-party repos work as expected. This
appears to be a cache error. Upstream MR
https://gitlab.gnome.org/GNOME/gnome-software/-/merge_requests/1325
has a candidate fix.
10. selinux-policy —
https://bugzilla.redhat.com/show_bug.cgi?id=2056303 — ASSIGNED
After upgrade to F36 several packages fail to update due to
selinux-related errors
Some container-related packages have references to SELinux socket
classes that no longer exist. container-selinux, osbuild, snapd,
flatpak need to be rebuilt against the newest selinux-policy.
11. spin-kickstarts — https://bugzilla.redhat.com/show_bug.cgi?id=2073708 — NEW
pyanaconda.modules.common.errors.installation.StorageInstallationError:
device is active
KDE Plasma automounts storage devices in the live image, causing
Anaconda to fail when trying to modifiy a disk with an existing
logical volume. Disabling automount in the KDE automount settings
prevents this.
Proposed blockers
-----------------
1. xorg-x11-server — https://bugzilla.redhat.com/show_bug.cgi?id=2074789 — NEW
Basic graphics mode broken for X11 with Nvidia GPU and UEFI
The vesa driver checks for the presence of a directory that no longer
exists since the switch to simpledrm in this release. Upstream MR
contains a candidate fix
https://gitlab.freedesktop.org/xorg/driver/xf86-video-vesa/-/merge_reques...
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
2 years
2022-04-19 **TUESDAY** @ 16:00 UTC - Fedora 36 Blocker Review
Meeting
by Adam Williamson
# F36 Blocker Review meeting
# Date: 2022-04-19 (**TUESDAY**)
# Time: 16:00 UTC
# Location: #fedora-blocker-review on irc.libera.chat
Hi folks! We have 3 proposed Final blockers and 4 proposed Final freeze
exception issues to review, so let's have a review meeting on *Tuesday*.
I'm scheduling it for Tuesday as Monday is a vacation day for Red Hat
in Canada and Czechia (among other countries).
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 F36 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 **TUESDAY**!
[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
2 years
KIO with Google Drive
by Patrick O'Callaghan
I'm attempting to use the KIO add-on for Google Drive in Dolphin. After
going through the Google authentication dialogue, it appears to be
stuck on the final confirmation screen. After clicking on "Allow"
nothing happens, even after many minutes of waiting.
Thoughts?
poc
2 years
I think it's a bug, but where do I report it?
by Mark ＠ GMail
Asking because I doubt that it's a Fedora bug, but yous all are so
knowledgable I'm sure someone can point me in the right direction.
I think there's a bug in php (fpm) for the Apache webserver. Unsetting
the user_dir directive (& therefore I assume any similar directive) by
resetting it to its initial state ("user_dir =", ie no value), does
*not* unset the previous non-empty value.
Surely such a basic thing can't have been overlooked, and therefore I
must've done something (else) wrong?
If not, where do I report that?
Many thanks.
2 years
Logitech mouse
by Emmett Culley
I have a logitech mouse that has been working well for a long time. Except that every once in a while it suddenly won't scroll one line at a time and instead requires multiple turns of the wheel to move a page.
I've been putting up with this as I am able to fix it by running solaar and toggling scroll wheel resolution off then on again. Only a couple of mouse clicks.
Now it seems to have gotten worse, or I am finally tired of having to stop my workflow to fix it. It seems to be related to the mouse going to sleep during inactivity, though it is random enough so I cannot be sure.
I am on the latest fedora 34 code, and I have been seeing issue since before 32.
Any ideas where to look for a solution?
Emmett
2 years
