We've branched, so let's start the weekly blocker status email yayyyyy
1. libreport — abrt-server errors when processing zstd compressed core
dumps produced by systemd-246~rc1-1.fc33 — POST
ACTION: abrt maintainers to make a new release containing the fix
2. resteasy — FreeIPA deployment fails in current Rawhide due to
various issues with Java 11 — NEW
ACTION: resteasy maintainers to diagnose issue and fix or pass the
buck as appropriate
3. sddm — login stuck when changing users repeatedly (log out, log in
a different one) — NEW
ACTION: sddm maintainers to diagnose issue and fix or pass the buck as
4. selinux-policy — SELinux is preventing systemd-machine from
'create' accesses on the sock_file io.systemd.Machine. — POST
ACTION: selinux-policy maintainers to make a new release containing the fixes
5. tomcat — FreeIPA server deployment fails in
Fedora-Rawhide-20200714.n.0 — MODIFIED
ACTION: tomcat maintainers to investigate failed upgrade test
1. gnome-shell — Network manager started stuck when I tries connecting
to VPN (openconnect) after upgrade gnome-shell to 3.37.1-1.fc33
version — NEW
ACTION: gnome-shell maintainers to diagnose issue
2. systemd — systemd-resolved.service not work with DNS server placed
behind VPN (openconnect) — NEW
ACTION: systemd maintainers to diagnose issue
3. udisks2 — zram-setup(a)zram0.service: Failed to load configuration:
No such file or directory — NEW
ACTION: Someone! to figure out why udisks2-zram gets pulled in
1. libreport — https://bugzilla.redhat.com/show_bug.cgi?id=1860616 — POST
abrt-server errors when processing zstd compressed core dumps produced
abrt doesn't support core dumps compressed with zstd, which is now
used by systemd. Merged upstream PR uses libarchive to add support for
zstd (and other compression formats):
2. resteasy — https://bugzilla.redhat.com/show_bug.cgi?id=1866570 — NEW
FreeIPA deployment fails in current Rawhide due to various issues with Java 11
Deploying FreeIPA fails with a traceback in pki-tomcat. This appears
to be a dependency chain issue that (currently) ends at resteasy via
dogtag-pki. This may not be the last layer in the Java 11 onion.
3. sddm — https://bugzilla.redhat.com/show_bug.cgi?id=1861700 — NEW
login stuck when changing users repeatedly (log out, log in a different one)
This is now a blocker based on a recent approval-in-principle of a
release criterion related to logout and user switching. User processes
linger after logout which blocks logging in when another user has
logged in between the two sessions. Or when the second user logs back
in. Or when a single user logs in repeatedly. Using
KillUserProcesses=Yes helps the first problem, but raises on of its
own. It appears to be a race condition of some kind as the behavior is
not fully consistent.
4. selinux-policy — https://bugzilla.redhat.com/show_bug.cgi?id=1862686 — POST
SELinux is preventing systemd-machine from 'create' accesses on the
librvirt VMs and systemd-machined service fail with AVC denials.
Merged upstream PRs should fix the denials mentioned in this bug:
5. tomcat — https://bugzilla.redhat.com/show_bug.cgi?id=1857043 — MODIFIED
FreeIPA server deployment fails in Fedora-Rawhide-20200714.n.0 due to
pki-tomcat failing to run with "java.lang.ClassNotFoundException:
An upstream commit resulted in tomcat-coyote.jar missing packages. A
previous fix (FEDORA-2020-f897a68801) moved the goalposts.
tomcat-9.0.37-3 should fix this. Verification is blocked on BZ1866570,
but Adam's most recent upgrade test still fails with a
1. gnome-shell — https://bugzilla.redhat.com/show_bug.cgi?id=1830343 — NEW
Network manager started stuck when I tries connecting to VPN
(openconnect) after upgrade gnome-shell to 3.37.1-1.fc33 version
Connecting to an OpenConnect VPN using 2FA hangs after the second
factor is entered. The journal contains an array.toString() message
which may or may not be a red herring (it looks like a deprecation
2. systemd — https://bugzilla.redhat.com/show_bug.cgi?id=1863041 — NEW
systemd-resolved.service not work with DNS server placed behind VPN
When connected to an OpenConnect VPN, host name resolution fails.
Manually disabling the systemd-resolved service works around this
3. udisks2 — https://bugzilla.redhat.com/show_bug.cgi?id=1861463 — NEW
zram-setup(a)zram0.service: Failed to load configuration: No such file
Installation on armhfp and aarch64 single-board computers fails with
zram-setup errors. It appears to be a conflict betwen udisks2-zram and
zram-generator-defaults. Update FEDORA-2020-e143a283fb renamse the
service unit file to make its origin more obvious. Removing
udisks2-zram fixes the issue, but it's pulled in as a dependency of
something, so that needs to be identified.
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Python 3.9.0rc2, the last preview before the final release of Python 3.9.0 has
been released yesterday.
The Fedora 33 update is at:
Should I try to get a freeze exception and get it to Fedora 33 Beta?
We would test Fedora 33 Beta with Python that is close to identical to the one
in Fedora 33 Final.
If there is a regression, we could break Beta prior to its release.
holding shift key down does not reveal GRUB menu (edit)
I'm not sure when this regression appeared. It was working with F32
VM's and I think also with some earlier F33 VMs.
Anyway, right now it's not working for me with either virt-manager or
baremetal (sample size of one each).
I've been testing right along, but haven't been reporting since the
problems I have encountered have been small compared to some of the
issues currently on the table. I am currently running F33
Workstation-Live 0916.n.0. As usual my testing is on bare metal. The
installs have been running fine.
I've seen the printer problems go from bad to worse when I couldn't even
install a printer with CUPS. Now I'm back to being able to install the
printer with CUPS, but only using the generic driver. Settings Printer
and Print Settings haven't been able to install a printer since when F33
I've been trying to break btrfs, but only for cases applicable to my as
deployed testing installing and uninstalling things trying to fragment
the disk and doing "user" unfortunate things to files. So far I haven't
seen any problems with btrfs.
There is one package in the repo that has a problem. It doesn't seem to
be retired. In fact the the version we are using in F32 is listed as the
current version for F33. The package seems to be scrambled with items
that don't seem to belong and some things missing. I don't know how this
should be reported. The package is "pitivi".
This bug still present, but as I said small issue. I'm wondering if I
have reported this against the wrong package. Since the Firewall-Applet
works in non-Gnome desktops should this be reported against one of the
Gnome components or perhaps Mutter since I suspect this is a Wayland
issue? I guess this could be an issue where the Firewall folks haven't
updated this to be Wayland compliant. Clarifications and Suggestions are
Have a Great Day!