DevHeads.net

Fedora 31 Final blocker status email #2

Action summary
====================

Accepted blockers
2. gdm — Second user gets locked out of his session every ~10 seconds — NEW
ACTION: maintainer to diagnose and fix issue

3. gnome-control-center — Gnome Control Center crashes upon a typo in
Printers settings — NEW
ACTION: upstream to diagnose and fix issue

4. gnome-control-center — Apply button stays gray on Network configuration — NEW
ACTION: upstream to diagnose and fix issue

5. LiveCD — Workstation x86_64 live image is over size target — NEW
ACTION: Workstation WG to trim installed packages or revisit size limit

6. sddm — Cannot start Fedora-KDE-Live (F31) in basic graphics mode on
BIOS machine — NEW
ACTION: frantisekz to bisect systemd to narrow down the issue

7. selinux-policy — Problem with time syncronization — POST
ACTION: maintainers to create update with potential fixes

8. xfdesktop — Xfce is using upstream desktop background — VERIFIED
ACTION: anyone to add karma to FEDORA-2019-ff99c07a62

9. dnf — Revert skip_if_unavailable default back to true — ASSIGNED
ACTION: dnf maintainers to determine how to deliver dnf.conf that
overrides built-in defaults

Proposed blockers
2. gnome-calendar — [3.34] gnome-calendar doesnt always run:
GDBus.Error:org.freedesktop.DBus.Error.NoReply: Remote peer
disconnected — NEW
ACTION: upstream to diagnose and fix issue

3. gnome-shell — Attempt to start Gnome Classic ends up in an error. — NEW
ACTION: upstream to diagnose and fix issue

4. gnome-shell — disappearing icons on the frequently used
applications page — NEW
ACTION: maintainers to package update with fix

5. gnome-software — GNOME Software doesn't prepare offline updates — NEW
ACTION: QA to verify that GNOME Software works once dnf change is reverted

Bug-by-bug detail
=============

Accepted blockers
Zoom remains enabled, even after logging out and logging back in.
Issue filed with gnome-control-center upstream:
<a href="https://gitlab.gnome.org/GNOME/gnome-control-center/issues/659" title="https://gitlab.gnome.org/GNOME/gnome-control-center/issues/659">https://gitlab.gnome.org/GNOME/gnome-control-center/issues/659</a> but
gnome-control-center maintainer suspects mutter is the issue.

2. gnome-session — <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1751673" title="https://bugzilla.redhat.com/show_bug.cgi?id=1751673">https://bugzilla.redhat.com/show_bug.cgi?id=1751673</a> — NEW
Second user gets locked out of his session every ~10 seconds

When user1 is already logged into GNOME, locks his session, and user2
logs in, user2's screen is locked immediately after logging in. When
user2 keeps logging in, his screen is locked approximately every 10
seconds. The locked screen shows user1's name (so not only user2 is
locked, the screen also switches to user1's lock screen every time).
This appears to be a side effect of
<a href="https://gitlab.gnome.org/GNOME/gdm/commit/3e8220921bb608afd06ed677104fd2244b901a28" title="https://gitlab.gnome.org/GNOME/gdm/commit/3e8220921bb608afd06ed677104fd2244b901a28">https://gitlab.gnome.org/GNOME/gdm/commit/3e8220921bb608afd06ed677104fd2...</a>

3. gnome-control-center —
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1750394" title="https://bugzilla.redhat.com/show_bug.cgi?id=1750394">https://bugzilla.redhat.com/show_bug.cgi?id=1750394</a> — NEW
Gnome Control Center crashes upon a typo in Printers settings

Typo in search field (e.g. 'socket>' instead of 'socket:') causes
application to crash. Filed upstream:
<a href="https://gitlab.gnome.org/GNOME/gnome-control-center/issues/679" title="https://gitlab.gnome.org/GNOME/gnome-control-center/issues/679">https://gitlab.gnome.org/GNOME/gnome-control-center/issues/679</a>

4. gnome-control-center —
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1750805" title="https://bugzilla.redhat.com/show_bug.cgi?id=1750805">https://bugzilla.redhat.com/show_bug.cgi?id=1750805</a> — NEW
Apply button stays gray on Network configuration

Wired network connections cannot be configured because the "apply"
button remains inactive. WiFi configuration works. File upstream:
<a href="https://gitlab.gnome.org/GNOME/gnome-control-center/issues/677" title="https://gitlab.gnome.org/GNOME/gnome-control-center/issues/677">https://gitlab.gnome.org/GNOME/gnome-control-center/issues/677</a>

5. LiveCD — <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1751438" title="https://bugzilla.redhat.com/show_bug.cgi?id=1751438">https://bugzilla.redhat.com/show_bug.cgi?id=1751438</a> — NEW
Workstation x86_64 live image is over size target

Adding podman increased the size of the live image above the specified
maximum. Either some packages need to be removed from the image or the
Workstation WG needs to increase the maximum size. Discussion is
ongoing in <a href="https://pagure.io/fedora-workstation/issue/104" title="https://pagure.io/fedora-workstation/issue/104">https://pagure.io/fedora-workstation/issue/104</a>

6. sddm — <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1728240" title="https://bugzilla.redhat.com/show_bug.cgi?id=1728240">https://bugzilla.redhat.com/show_bug.cgi?id=1728240</a> — NEW
Cannot start Fedora-KDE-Live (F31) in basic graphics mode on BIOS machine

This issue only seems to affect BIOS machines when using basic
graphics mode. Regular graphics or UEFI does not exhibit this
behavior. It may be a systemd issue as downgrading solves the problem.
frantisekz will bisect to narrow it down.

7. selinux-policy — <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1750036" title="https://bugzilla.redhat.com/show_bug.cgi?id=1750036">https://bugzilla.redhat.com/show_bug.cgi?id=1750036</a> — POST
Problem with time syncronization

When SELinux is enforcing, the NTP service is not active, but no
failed services are listed. Policies updated to fix this, no update is
available in Bodhi yet.

8. xfdesktop — <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1751852" title="https://bugzilla.redhat.com/show_bug.cgi?id=1751852">https://bugzilla.redhat.com/show_bug.cgi?id=1751852</a> — VERIFIED
Xfce is using upstream desktop background

Update FEDORA-2019-ff99c07a62 fixes the issue. It is in
updates-testing waiting for karma or time.

9. dnf — <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1752249" title="https://bugzilla.redhat.com/show_bug.cgi?id=1752249">https://bugzilla.redhat.com/show_bug.cgi?id=1752249</a> — ASSIGNED
Revert skip_if_unavailable default back to true

FESCo requested the default change be reverted before F31 final.
Upstream PR #1484
(<a href="https://github.com/rpm-software-management/dnf/pull/1484" title="https://github.com/rpm-software-management/dnf/pull/1484">https://github.com/rpm-software-management/dnf/pull/1484</a>) enables the
defaults to be changed on a per-distro basis. dnf maintainers are
discussing how to deliver dnf.conf for particular distributions.

Proposed blockers
1. gnome-boxes — <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1753985" title="https://bugzilla.redhat.com/show_bug.cgi?id=1753985">https://bugzilla.redhat.com/show_bug.cgi?id=1753985</a> — NEW
Gnome-Boxes cannot connect to Virtualization Backend

In OpenQA, Gnome Boxes could not connect to the virtualization
backend. A subsequent run worked, so this may be a race condition or
other issue.

2. gnome-calendar — <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1753558" title="https://bugzilla.redhat.com/show_bug.cgi?id=1753558">https://bugzilla.redhat.com/show_bug.cgi?id=1753558</a> — NEW
[3.34] gnome-calendar doesnt always run:
GDBus.Error:org.freedesktop.DBus.Error.NoReply: Remote peer
disconnected

Launching gnome-calendar fails often (but not always) with DBus error.
Reported upstream:
<a href="https://gitlab.gnome.org/GNOME/gnome-calendar/issues/455" title="https://gitlab.gnome.org/GNOME/gnome-calendar/issues/455">https://gitlab.gnome.org/GNOME/gnome-calendar/issues/455</a>

3. gnome-shell — <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1753191" title="https://bugzilla.redhat.com/show_bug.cgi?id=1753191">https://bugzilla.redhat.com/show_bug.cgi?id=1753191</a> — NEW
Attempt to start Gnome Classic ends up in an error.

An environment variable appears to be persistent across sessions.
Related upstream issue:
<a href="https://gitlab.gnome.org/GNOME/gnome-shell/issues/1598" title="https://gitlab.gnome.org/GNOME/gnome-shell/issues/1598">https://gitlab.gnome.org/GNOME/gnome-shell/issues/1598</a> .

4. gnome-shell — <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1753337" title="https://bugzilla.redhat.com/show_bug.cgi?id=1753337">https://bugzilla.redhat.com/show_bug.cgi?id=1753337</a> — NEW
disappearing icons on the frequently used applications page

Fixed upstream: <a href="https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/704" title="https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/704">https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/704</a>

5. gnome-session — <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1749868" title="https://bugzilla.redhat.com/show_bug.cgi?id=1749868">https://bugzilla.redhat.com/show_bug.cgi?id=1749868</a> — NEW
GNOME Software doesn't prepare offline updates

Systems with third-party repos that are not functional fail. Reverting
the dnf skip_if_unavailable default appears to fix this, but GNOME
Software should handle the case more gracefully. That is probably
independent of blocker status.