Fedora Linux 37 Final freeze begins Tuesday 4 October.
Action summary ====================
Accepted blockers -----------------
1. anaconda — Custom partitioning with 2 drives selected, bootloader fails to install due to one drive not having a BIOS Boot partition — ON_QA ACTION: QA to verify FEDORA-2022-c20d42f3bc
2. gnome-contacts — When a single contact is edited, it results in multiple contacts of the same name. — ON_QA ACTION: QA to verify FEDORA-2022-acbfee2ce8
3. gnome-initial-setup — Unable to set up enterprise account with gnome-initial-setup, clicking continue does not join the domain — ASSIGNED ACTION: dgilmore to test https://koji.fedoraproject.org/koji/taskinfo?taskID=92037333
4. gnome-shell — GNOME Initial Setup uses the English keyboard, instead of the default keyboard — ASSIGNED ACTION: Upstream to diagnose and resolve issue
5. gnome-shell — Attempting to disconnect VPN connection from system menu does nothing — VERIFIED ACTION: (none)
6. gnome-software — Can't install a local rpm package anymore, Install button missing (for certain RPMs) — VERIFIED ACTION: (none)
7. greenboot — greenboot-grub2-set-counter.service fails on 38 IoT with "cannot open `/boot/grub2/grubenv.new`: No such file or directory." — NEW ACTION: Maintainers to diagnose issue
8. grub2 — Windows with bitlocker enabled can't be booted, needs to use bootnext instead of chainloader — NEW ACTION: Maintainers to diagnose issue or provide status update
9. mesa — totem: nouveau_pushbuf_data(): totem killed by SIGABRT — NEW ACTION: Maintainers to update mesa with fixes for F37
10. uboot-tools — Regression booting Fedora on rockchip devices installed on PCIe NVME drives — ON_QA ACTION: QA to verify FEDORA-2022-c1d9e8daa9
Proposed blockers -----------------
1. chrome-gnome-shell — Project name and source repository changed to gnome-browser-connector — NEW ACTION: Reviewer to approve new gnome-browser-connector package.
2. gnome-shell — screencast doesn't record the top layer — NEW ACTION: QA to verify if behavior still exists
3. gnome-shell-extension-background-logo — Update gnome-shell-extension-background-logo to 43.0 — NEW ACTION: Maintainer to update package
4. systemd — Czech qwerty layout configured in anaconda, but qwertz layout used in disk unlock and in VT console — NEW ACTION: kbd maintainers to reconsider the -legacy subpackage split
Bug-by-bug detail =============
Accepted blockers -----------------
1. anaconda — https://bugzilla.redhat.com/show_bug.cgi?id=2088113 — ON_QA Custom partitioning with 2 drives selected, bootloader fails to install due to one drive not having a BIOS Boot partition
When using custom partitioning on two drives with /boot on a RAID 1 device, the installer only creates one BIOS boot. grub2-install is run against both drives, but the second fails because it has no BIOS boot partition. FEDORA-2022-c20d42f3bc contains a candidate fix.
2. gnome-contacts — https://bugzilla.redhat.com/show_bug.cgi?id=2111003 — ON_QA When a single contact is edited, it results in multiple contacts of the same name.
Editing a contact results in the contact being properly updated, but an empty contact is created with the same name. FEDORA-2022-acbfee2ce8 contains a candidate fix.
3. gnome-initial-setup — https://bugzilla.redhat.com/show_bug.cgi?id=2123494 — ASSIGNED Unable to set up enterprise account with gnome-initial-setup, clicking continue does not join the domain
Initially the buttons were missing. Update FEDORA-2022-50e585b456 fixed that issue, however clicking the button does not joing the domain. Instead, the user is returned to the domain credentials screen, resulting in an endless loop. https://koji.fedoraproject.org/koji/taskinfo?taskID=92037333 contains a backport of upstream's change which may fix it.
4. gnome-shell — https://bugzilla.redhat.com/show_bug.cgi?id=2121110 — ASSIGNED GNOME Initial Setup uses the English keyboard, instead of the default keyboard
Regardless of the default keyboard setting, g-i-s uses the English keyboard. Relatedly, new users have the English keyboard selected, even though another language is shown as the default. FEDORA-2022-52cdfc7920 failed to fix this issue.
5. gnome-shell — https://bugzilla.redhat.com/show_bug.cgi?id=2125252 — VERIFIED Attempting to disconnect VPN connection from system menu does nothing
Disabling a VPN doesn't disable the VPN. Fixed in FEDORA-2022-50e585b456.
6. gnome-software — https://bugzilla.redhat.com/show_bug.cgi?id=2124869 — VERIFIED Can't install a local rpm package anymore, Install button missing (for certain RPMs)
What it says on the tin. Fixed in FEDORA-2022-b6246d02fa.
7. greenboot — https://bugzilla.redhat.com/show_bug.cgi?id=2121944 — NEW greenboot-grub2-set-counter.service fails on 38 IoT with "cannot open `/boot/grub2/grubenv.new`: No such file or directory."
greenboot service fails on a file-not-found error. This also results in rebase tests failing because of conflicts with the rebase triggered by the greenboot failure.
8. grub2 — https://bugzilla.redhat.com/show_bug.cgi?id=2049849 — NEW Windows with bitlocker enabled can't be booted, needs to use bootnext instead of chainloader
Dual-booting recent Windows 10 system with TPM 2.0 fails because bitlocker can't be unsealed by the TPM. This was waived to F37 under the "difficult to fix" exception. No additional updates have been provided.
9. mesa — https://bugzilla.redhat.com/show_bug.cgi?id=2123274 — NEW totem: nouveau_pushbuf_data(): totem killed by SIGABRT
totem plays ~1 second of video and then crashes. This appears to happen with all video formats. This appears to be an issue in multithreading support in the nouveau driver, which is fixed upstream. The fix is large and may not be suitable for backporting, but would be available in a mesa-22.3 update.
10. uboot-tools — https://bugzilla.redhat.com/show_bug.cgi?id=2124127 — ON_QA Regression booting Fedora on rockchip devices installed on PCIe NVME drives
uboot-tools introducted a regression when used with 5.19.x kernels. FEDORA-2022-c1d9e8daa9 contains a candidate fix.
Proposed blockers -----------------
1. chrome-gnome-shell — https://bugzilla.redhat.com/show_bug.cgi?id=2106868 — NEW Project name and source repository changed to gnome-browser-connector
Upstream has split this into two packages. Package review pending for renamed package: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2127314
2. gnome-shell — https://bugzilla.redhat.com/show_bug.cgi?id=2125439 — NEW screencast doesn't record the top layer
Typing and popup windows don't show when recording a screencast. This may be fixed in pipewire-gstreamer-0.3.57-1.
3. gnome-shell-extension-background-logo — https://bugzilla.redhat.com/show_bug.cgi?id=2127192 — NEW Update gnome-shell-extension-background-logo to 43.0
The Fedora logo is not displayed and the package is not compatible with gnome-shell 43.
4. systemd — https://bugzilla.redhat.com/show_bug.cgi?id=2121106 — NEW Czech qwerty layout configured in anaconda, but qwertz layout used in disk unlock and in VT console
The wrong keymap is used when unlocking disks or virtual terminals. It looks like this may have never worked. It looks like an issue with how layouts are mapped between console and xkb. Adam is thinking about how to approach this: https://bugzilla.redhat.com/show_bug.cgi?id=2121106#c24
Action summary ====================
Accepted blockers -----------------
1. anaconda — Custom partitioning with 2 drives selected, bootloader fails to install due to one drive not having a BIOS Boot partition — ON_QA ACTION: QA to verify FEDORA-2022-c20d42f3bc
2. gnome-initial-setup — Unable to set up enterprise account with gnome-initial-setup, clicking continue does not join the domain — VERIFIED ACTION: (none)
3. gnome-shell — GNOME Initial Setup uses the English keyboard, instead of the default keyboard — VERIFIED ACTION: (none)
4. greenboot — greenboot-grub2-set-counter.service fails on 38 IoT with "cannot open `/boot/grub2/grubenv.new`: No such file or directory." — NEW ACTION: Maintainers to diagnose issue
5. grub2 — Windows with bitlocker enabled can't be booted, needs to use bootnext instead of chainloader — NEW ACTION: QA to finalize updated criterion proposal
6. mesa — totem: nouveau_pushbuf_data(): totem killed by SIGABRT — NEW ACTION: Maintainers to update mesa with fixes for F37
Proposed blockers -----------------
1. abrt — Abrt does not report a segfault which is reported in journalctl. — ASSIGNED ACTION: Maintainers to diagnose issue
2. nautilus — Nautilus thumbnailing doesn't work on hidpi screens — NEW ACTION: Upstream to diagnose issue
Bug-by-bug detail =============
Accepted blockers -----------------
1. anaconda — https://bugzilla.redhat.com/show_bug.cgi?id=2088113 — ON_QA Custom partitioning with 2 drives selected, bootloader fails to install due to one drive not having a BIOS Boot partition
When using custom partitioning on two drives with /boot on a RAID 1 device, the installer only creates one BIOS boot. grub2-install is run against both drives, but the second fails because it has no BIOS boot partition. FEDORA-2022-c20d42f3bc contains a candidate fix.
2. gnome-initial-setup — https://bugzilla.redhat.com/show_bug.cgi?id=2123494 — VERIFIED Unable to set up enterprise account with gnome-initial-setup, clicking continue does not join the domain
Initially the buttons were missing. Update FEDORA-2022-50e585b456 fixed that issue, however clicking the button does not joing the domain. Instead, the user is returned to the domain credentials screen, resulting in an endless loop. gnome-initial-setup-43.0-3.fc37 contains a verified fix.
3. gnome-shell — https://bugzilla.redhat.com/show_bug.cgi?id=2121110 — ASSIGNED GNOME Initial Setup uses the English keyboard, instead of the default keyboard
Regardless of the default keyboard setting, g-i-s uses the English keyboard. Relatedly, new users have the English keyboard selected, even though another language is shown as the default. FEDORA-2022-b14944cb83 contains a verified fix.
4. greenboot — https://bugzilla.redhat.com/show_bug.cgi?id=2121944 — NEW greenboot-grub2-set-counter.service fails on 38 IoT with "cannot open `/boot/grub2/grubenv.new`: No such file or directory."
greenboot service fails on a file-not-found error. This also results in rebase tests failing because of conflicts with the rebase triggered by the greenboot failure.
5. grub2 — https://bugzilla.redhat.com/show_bug.cgi?id=2049849 — NEW Windows with bitlocker enabled can't be booted, needs to use bootnext instead of chainloader
Dual-booting recent Windows 10 system with TPM 2.0 fails because bitlocker can't be unsealed by the TPM. This was waived to F37 under the "difficult to fix" exception. A proposed change to the release criteria may exclude this from blocker status.
6. mesa — https://bugzilla.redhat.com/show_bug.cgi?id=2123274 — NEW totem: nouveau_pushbuf_data(): totem killed by SIGABRT
totem plays ~1 second of video and then crashes. This appears to happen with all video formats. This appears to be an issue in multithreading support in the nouveau driver, which is fixed upstream. The fix is large and may not be suitable for backporting, but would be available in a mesa-22.3 update.
Proposed blockers -----------------
1. abrt — https://bugzilla.redhat.com/show_bug.cgi?id=2128662 — ASSIGNED Abrt does not report a segfault which is reported in journalctl.
In some circumstances (currently unclear), abrt does not report segfaults. Restarting abrt-journal-core (including via reboot) causes abrt to work correctly again.
2. nautilus — https://bugzilla.redhat.com/show_bug.cgi?id=2127618 — NEW Nautilus thumbnailing doesn't work on hidpi screens
No thumbnails are generated in the file manager on hidpi screens. Other functionality works. Reported upstream as https://gitlab.gnome.org/GNOME/nautilus/-/issues/2487
On Thu, 2022-09-22 at 13:01 -0400, Ben Cotton wrote:
- mesa — https://bugzilla.redhat.com/show_bug.cgi?id=2123274 — NEW
totem: nouveau_pushbuf_data(): totem killed by SIGABRT
totem plays ~1 second of video and then crashes. This appears to happen with all video formats. This appears to be an issue in multithreading support in the nouveau driver, which is fixed upstream. The fix is large and may not be suitable for backporting, but would be available in a mesa-22.3 update.
Well, it's not so much backporting that's the problem. It's just that it's a large change and nobody seems to be super confident about just throwing it into F37, whether via a backport or a new mesa release. I'm really not sure what we should do here. It may honestly be safer to ship the way we are, with a known bug, and then do mesa as a post- release update; it's much safer in a way to do something as a post- release update, because then we at least have a "known not-completely- broken" version in the release repo, and our release live image is in a known-not-completely-broken state. We can then let the update sit for testing until we're relatively confident it's better than the current state.
If we decide to put the new version in for release then belatedly find out the new code has significant problems that are worse than video playback in totem, we're up a much rougher creek.
So, this one seems like a bit of a tough call. It would be a good idea, I think, to get an update with the new code rolled at least, then people can try it out and we can start getting an idea whether it has problems...
I am relieved of the burden of worrying that we don't have enough blockers. F37 Final freeze begins Tuesday. The current target release date is the early target date of 18 October.
Action summary ====================
Accepted blockers -----------------
1. grub2 — Windows with bitlocker enabled can't be booted, needs to use bootnext instead of chainloader — NEW ACTION: QA to accept proposed release criteria amendment
2. abrt — Abrt does not report a segfault which is reported in journalctl. — ASSIGNED ACTION: QA to come up with a reproducer
3. glibc — glibc 2.36+ breaks EAC with removal of DT_HASH (and other game libraries), making games fail to load — POST ACTION: Maintainers to work out a solution with requester
4. gnome-maps — Gnome-Maps crashes when searching for locations. — VERIFIED ACTION: (none)
Proposed blockers -----------------
1. firefox — Firefox cause flickering context menus on websites since 105.1 on wayland — NEW ACTION: Maintainers to investigate backporting the upstream fix
2. gnome-calendar — Month names are not in sync — NEW ACTION: Upstream to diagnose and fix issue
3. gnome-calendar — Editing recurring events is broken, changes a single instance instead of all instances — NEW ACTION: Upstream to diagnose and fix issue
4. gnome-calendar — Calendar does not delete events properly — NEW ACTION: Upstream to diagnose and fix issue
5. gnome-contacts — Editing an existing contact's email address causes Contacts to display an empty "Unnamed Person" card, other edits made at the same time are lost – POST ACTION: Maintainers to package upstream MR for testing
6. gnome-contacts — Link Contacts feature completely broken — NEW ACTION: Upstream to diagnose and fix issue
7. gnome-photos — Favorited photos from albums are shown as favorited only after app restart or second attempt — NEW ACTION: Upstream to diagnose and fix issue
8. gnome-photos — Memory exhaustion when editing a cropped photo — NEW ACTION: Upstream to diagnose and fix issue
9. gnome-settings-daemon — Default GTK_IM_MODULE should be ibus in GNOME Xorg — POST ACTION: Maintainers to package upstream MR for testing
10. nautilus — Nautilus thumbnailing doesn't work on hidpi screens — NEW ACTION: Upstream to fix issue
Bug-by-bug detail =============
Accepted blockers -----------------
1. grub2 — https://bugzilla.redhat.com/show_bug.cgi?id=2049849 — NEW Windows with bitlocker enabled can't be booted, needs to use bootnext instead of chainloader
Dual-booting recent Windows 10 system with TPM 2.0 fails because bitlocker can't be unsealed by the TPM. This was waived to F37 under the "difficult to fix" exception. A proposed amendment to the release criteria would exclude this from blocker status: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/m...
2. abrt — https://bugzilla.redhat.com/show_bug.cgi?id=2128662 — ASSIGNED Abrt does not report a segfault which is reported in journalctl.
A possible race condition caused abrt to fail to report segfaults. Restarting the service caused abrt to work as expected. Recent attempts to reproduce the behavior have failed.
3. glibc — https://bugzilla.redhat.com/show_bug.cgi?id=2129358 — POST glibc 2.36+ breaks EAC with removal of DT_HASH (and other game libraries), making games fail to load
Not including DT_HASH data in glibc's ELF binaries causes Steam games using Epic Games Easy Anti-Cheat software to fail to load the EAC module. This was made a blocker by FESCo due to the reptuational impact it would have in the gaming community. A PR exists to restore this data, but the maintainers have concerns about testing.
4. gnome-maps — https://bugzilla.redhat.com/show_bug.cgi?id=2129914 — VERIFIED Gnome-Maps crashes when searching for locations.
Seraching for a location causes Maps to crash. Update FEDORA-2022-094ef88915 contains a verified fix.
Proposed blockers -----------------
1. firefox — https://bugzilla.redhat.com/show_bug.cgi?id=2130087 — NEW Firefox cause flickering context menus on websites since 105.1 on wayland
Context menus flicker, particularly when the mouse moves. This only happens on Wayland sessions and does not appear to be related to scaling. An upstream patch in the upcoming 107 release (expected 15 Nov) contains a fix.
2. gnome-calendar — https://bugzilla.redhat.com/show_bug.cgi?id=2130964 — NEW Month names are not in sync
Under a variety of conditions, the month names do in the two panels do not adjust in sync. In fact, it's possible to create an event in one month while the main view and left pane each say different months. Filed upstream as https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/868
3. gnome-calendar — https://bugzilla.redhat.com/show_bug.cgi?id=2130977 — NEW Editing recurring events is broken, changes a single instance instead of all instances
When editing a recurring event, only one isntance moves. That instance is duplicated, while previous instances are deleted and subsequent instances are unchanged. Filed upstream as https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/871
4. gnome-calendar — https://bugzilla.redhat.com/show_bug.cgi?id=2130981 — NEW Calendar does not delete events properly
Deleting a calendar event before the confirmation appears results in events listed in certain views. After an application restart, the events are back but cannot be deleted or edited. Filed upstream as https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/858
5. gnome-contacts — https://bugzilla.redhat.com/show_bug.cgi?id=2130657 — POST Editing an existing contact's email address causes Contacts to display an empty "Unnamed Person" card, other edits made at the same time are lost
Clicking back on an edited contact shows the card correctly if only one field is edited. If the test edited two properties of the contact (e.g. the email address and the phone number), the new email address is shown, but the old phone number is shown - i.e. the phone number change seems to be lost. Upstream MR https://gitlab.gnome.org/GNOME/gnome-contacts/-/merge_requests/213 contains a candidate fix.
6. gnome-contacts — https://bugzilla.redhat.com/show_bug.cgi?id=2130661 — NEW Link Contacts feature completely broken
Trying to link contacts yields unexpected behavior. Linking contacts results in two identifcal contacts with the information from both originals. After restarting Contacts, the original contacts are restored to their original states.
7. gnome-photos — https://bugzilla.redhat.com/show_bug.cgi?id=2130927 — NEW Favorited photos from albums are shown as favorited only after app restart or second attempt
Using the star button to mark a photo as a favorite is not reflected until either the operation is performed again or Photos is restarted. Filed upstream as https://gitlab.gnome.org/GNOME/gnome-photos/-/issues/204
8. gnome-photos — https://bugzilla.redhat.com/show_bug.cgi?id=2130937 — NEW Memory exhaustion when editing a cropped photo
When changing the shadows or highlights on a cropped photos, Photos consumes 100% CPU and uses all available memory until killed by the OOMkiller. This may be related to a recent change in the Generic Graphics Library (GEGL). Filed upstream as https://gitlab.gnome.org/GNOME/gnome-photos/-/issues/205
9. gnome-settings-daemon — https://bugzilla.redhat.com/show_bug.cgi?id=2128423 — POST Default GTK_IM_MODULE should be ibus in GNOME Xorg
Trying to add a first input method in gnome-control-center does not take effect until GNOME is restarted. This only affects X11 sessions. Upstream MR contains a candidate fix: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/merge_requests/309
10. nautilus — https://bugzilla.redhat.com/show_bug.cgi?id=2127618 — NEW Nautilus thumbnailing doesn't work on hidpi screens
When an image that does not already have a thumbnail, Nautilus has a heavy CPU load while it is showing the directory. Filed upstream as https://gitlab.gnome.org/GNOME/nautilus/-/issues/2487
The Go/No-Go for the early target date is Thursday. In order to be ready, we need blockers to be resolved by Tuesday at the latest.
Action summary ====================
Accepted blockers -----------------
1. abrt — Abrt does not report a segfault which is reported in journalctl. — ASSIGNED ACTION: QA to come up with a reproducer
2. anaconda — Installer Crashes When Attempting to Reclaim Space — ON_QA ACTION: QA to verify FEDORA-2022-2c9c1ebab5
3. glibc — glibc 2.36+ breaks EAC with removal of DT_HASH (and other game libraries), making games fail to load — POST ACTION: Maintainers to merge PR and build update
4. gnome-calendar — Month names are not in sync — VERIFIED ACTION: (none)
5. gnome-calendar — Editing recurring events is broken, changes a single instance instead of all instances — VERIFIED ACTION: (none)
6. gnome-calendar — Calendar does not delete events properly — VERIFIED ACTION: (none)
7. gnome-contacts — Editing an existing contact's email address causes Contacts to display an empty "Unnamed Person" card, other edits made at the same time are lost — ASSIGNED ACTION: upstream to diagnose and fix issue
8. gnome-contacts — Link Contacts feature completely broken — NEW ACTION: upstream to diagnose and fix issue
9. gnome-shell — On Screen Keyboard cannot type a space anywhere — NEW ACTION: upstream to diagnose and fix issue
Proposed blockers -----------------
1. gnome-calendar — Changes to recurring events don't redraw correctly — NEW ACTION: upstream to diagnose and fix issue
2. gnome-calendar — Editing a recurring event moves it forward in time — NEW ACTION: upstream to diagnose and fix issue
3. gnome-photos — Memory exhaustion when editing a cropped photo — NEW ACTION: upstream to diagnose and fix issue
4. gnome-software — rpm-ostree plugin refuses to update — ON_QA ACTION: QA to verify FEDORA-2022-b53191498a
5. imsettings — Default GTK_IM_MODULE should be ibus in GNOME Xorg — ON_QA ACTION: QA to verify FEDORA-2022-d5a9bcdac5
6. mesa — Mesa 22.2.0~rc3 is built without support for common video codecs, missing mesa-va-drivers might cause issues — ASSIGNED ACTION: Maintainers to diagnose and fix issue
7. poppler — CVE-2022-38784: integer overflow in JBIG2 decoder using malformed files — ON_QA ACTION: QA to verify FEDORA-2022-fcb3b063a6
Bug-by-bug detail =============
Accepted blockers -----------------
1. abrt — https://bugzilla.redhat.com/show_bug.cgi?id=2128662 — ASSIGNED Abrt does not report a segfault which is reported in journalctl.
A possible race condition caused abrt to fail to report segfaults. Restarting the service caused abrt to work as expected. Recent attempts to reproduce the behavior have failed.
2. anaconda — https://bugzilla.redhat.com/show_bug.cgi?id=2131183 — ON_QA Installer Crashes When Attempting to Reclaim Space
When using custom storage configuration, deleting existing mount points and devices on the Manual Partitioning Screen causes Anaconda to crash. FEDORA-2022-2c9c1ebab5 contains a candidate fix.
3. glibc — https://bugzilla.redhat.com/show_bug.cgi?id=2129358 — POST glibc 2.36+ breaks EAC with removal of DT_HASH (and other game libraries), making games fail to load
Not including DT_HASH data in glibc's ELF binaries causes Steam games using Epic Games Easy Anti-Cheat software to fail to load the EAC module. This was made a blocker by FESCo due to the reptuational impact it would have in the gaming community. A PR exists to restore this data, but the maintainers have concerns about testing.
4. gnome-calendar — https://bugzilla.redhat.com/show_bug.cgi?id=2130964 — VERIFIED Month names are not in sync
Under a variety of conditions, the month names do in the two panels do not adjust in sync. In fact, it's possible to create an event in one month while the main view and left pane each say different months. FEDORA-2022-89b6622d53 contains a verified fix.
5. gnome-calendar — https://bugzilla.redhat.com/show_bug.cgi?id=2130977 — VERIFIED Editing recurring events is broken, changes a single instance instead of all instances
When editing a recurring event, only one isntance moves. That instance is duplicated, while previous instances are deleted and subsequent instances are unchanged. FEDORA-2022-89b6622d53 contains a verified fix (although the UI does not correctly redraw events, which is RHBZ 2132769).
6. gnome-calendar — https://bugzilla.redhat.com/show_bug.cgi?id=2130981 — VERIFIED Calendar does not delete events properly
Deleting a calendar event before the confirmation appears results in events listed in certain views. After an application restart, the events are back but cannot be deleted or edited. FEDORA-2022-89b6622d53 contains a verified fix.
7. gnome-contacts — https://bugzilla.redhat.com/show_bug.cgi?id=2130657 — ASSIGNED Editing an existing contact's email address causes Contacts to display an empty "Unnamed Person" card, other edits made at the same time are lost
Clicking back on an edited contact shows the card correctly if only one field is edited. If the test edited two properties of the contact (e.g. the email address and the phone number), the new email address is shown, but the old phone number is shown - i.e. the phone number change seems to be lost. Filed upstream as https://gitlab.gnome.org/GNOME/gnome-contacts/-/issues/271
8. gnome-contacts — https://bugzilla.redhat.com/show_bug.cgi?id=2130661 — NEW Link Contacts feature completely broken
Trying to link contacts yields unexpected behavior. Linking contacts results in two identifcal contacts with the information from both originals. After restarting Contacts, the original contacts are restored to their original states. Filed upstream as https://gitlab.gnome.org/GNOME/gnome-contacts/-/issues/247
9. gnome-shell — https://bugzilla.redhat.com/show_bug.cgi?id=2131837 — NEW On Screen Keyboard cannot type a space anywhere
The on-screen keyboard does not type space characters. It appears that with the default typing-booster IM, space keys never reach the client. Filed upstream as https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5930
Proposed blockers -----------------
1. gnome-calendar — https://bugzilla.redhat.com/show_bug.cgi?id=2132769 — NEW Changes to recurring events don't redraw correctly
Building off of RHBZ 2130977, edits to recurring events don't cause the UI to re-render the events correctly. Filed upstream as https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/881
2. gnome-calendar — https://bugzilla.redhat.com/show_bug.cgi?id=2132772 — NEW Editing a recurring event moves it forward in time
Applying a change to all events in a recurring series moves all events forward in time. Filed upstream as https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/882
3. gnome-photos — https://bugzilla.redhat.com/show_bug.cgi?id=2130937 — NEW Memory exhaustion when editing a cropped photo
When changing the shadows or highlights on a cropped photos, Photos consumes 100% CPU and uses all available memory until killed by the OOMkiller. Recent discovery that this behavior exists in F36 has caused a trend toward not blocking on this bug. Filed upstream as https://gitlab.gnome.org/GNOME/gnome-photos/-/issues/205
4. gnome-software — https://bugzilla.redhat.com/show_bug.cgi?id=2132292 — ON_QA rpm-ostree plugin refuses to update
A typo caused Software to offer a download button for rpm-ostree updates, which does nothing, instead of the "Restart & Update" button, which performs the update. FEDORA-2022-b53191498a contains a candidate fix.
5. imsettings — https://bugzilla.redhat.com/show_bug.cgi?id=2131673 — ON_QA Default GTK_IM_MODULE should be ibus in GNOME Xorg
In some locales, GTK_IM_MODULE is set to gtk-im-context-simple instead of ibus. FEDORA-2022-d5a9bcdac5 contains a candidate fix.
6. mesa — https://bugzilla.redhat.com/show_bug.cgi?id=2123998 — ASSIGNED Mesa 22.2.0~rc3 is built without support for common video codecs, missing mesa-va-drivers might cause issues
Some users have encountered a failure of GDM to launch, which is solved by installing mesa-va-drivers. This may not be an issue with the default install. We have not yet identified the specific conditions which cause it to fail.
7. poppler — https://bugzilla.redhat.com/show_bug.cgi?id=2124530 — ON_QA CVE-2022-38784 poppler: integer overflow in JBIG2 decoder using malformed files
FEDORA-2022-fcb3b063a6 contains a build to fix the vulnerability.
Action summary ====================
Accepted blockers -----------------
1. abrt — Abrt does not report a segfault which is reported in journalctl. — ON_QA ACTION: QA to verify FEDORA-2022-7cf3cad7c7
2. glibc — glibc 2.36+ breaks EAC with removal of DT_HASH (and other game libraries), making games fail to load — POST ACTION: Maintainers to build update with simplified patch
3. gnome-calendar — Changes to recurring events don't redraw correctly — VERIFIED ACTION: (none)
4. gnome-calendar — Editing a recurring event moves it forward in time — VERIFIED ACTION: (none)
5. gnome-contacts — Link Contacts feature completely broken — MODIFIED ACTION: QA to verify FEDORA-2022-67067ed63e
6. kernel — kernel crash on a number of rockchip rk3399 devices on boot — ON_QA ACTION: QA to verify FEDORA-2022-1a5b125ac6
Proposed blockers -----------------
(none)
Bug-by-bug detail =============
Accepted blockers -----------------
1. abrt — https://bugzilla.redhat.com/show_bug.cgi?id=2128662 — ON_QA Abrt does not report a segfault which is reported in journalctl.
A possible race condition caused abrt to fail to report segfaults. Restarting the service caused abrt to work as expected. Update FEDORA-2022-7cf3cad7c7 contains a candidate fix.
2. glibc — https://bugzilla.redhat.com/show_bug.cgi?id=2129358 — POST glibc 2.36+ breaks EAC with removal of DT_HASH (and other game libraries), making games fail to load
Not including DT_HASH data in glibc's ELF binaries causes Steam games using Epic Games Easy Anti-Cheat software to fail to load the EAC module. This was made a blocker by FESCo due to the reputational impact it would have in the gaming community. Carlos is testing a simplified version of a submitted patch.
3. gnome-calendar — https://bugzilla.redhat.com/show_bug.cgi?id=2132769 — VERIFIED Changes to recurring events don't redraw correctly
Building off of RHBZ 2130977, edits to recurring events don't cause the UI to re-render the events correctly. FEDORA-2022-d687a7f331 contains a verified fix.
4. gnome-calendar — https://bugzilla.redhat.com/show_bug.cgi?id=2132772 — VERIFIED Editing a recurring event moves it forward in time
Applying a change to all events in a recurring series moves all events forward in time. FEDORA-2022-d687a7f331 contains a verified fix
5. gnome-contacts — https://bugzilla.redhat.com/show_bug.cgi?id=2130661 — MODIFIED Link Contacts feature completely broken
Trying to link contacts yields unexpected behavior. Linking contacts results in two identifcal contacts with the information from both originals. After restarting Contacts, the original contacts are restored to their original states. Filed upstream as https://gitlab.gnome.org/GNOME/gnome-contacts/-/issues/247 . FEDORA-2022-67067ed63e hides the functionality in the UI until it can be fixed.
6. kernel — https://bugzilla.redhat.com/show_bug.cgi?id=2134177 — ON_QA kernel crash on a number of rockchip rk3399 devices on boot
The USB2 module causes a kernel error on some rockchip devices. FEDORA-2022-1a5b125ac6 contains a candidate fix.
Proposed blockers -----------------
(none)
We were no-go today for target date #1. In order to hit target date #2, we'd ideally have fixes for outstanding blockers by Monday. Tuesday at the latest. (Note that based on upstream's comments, the accepted gnome-calendar bug is a candidate to be waived under the "difficult to fix" exception)
In the interests of saving myself a few minutes, I did not include two proposed blockers that have overwhelmingly negative votes. You can see them for yourself at: https://qa.fedoraproject.org/blockerbugs/milestone/37/final/buglist
Action summary ====================
Accepted blockers -----------------
1. gnome-calendar — Editing the recurring event freezes Calendar. — NEW ACTION: Upstream to diagnose and fix issue
2. kernel — No video on Raspberry Pi 4 with kernel 5.19.15 and 5.19.16 (testing) — ASSIGNED ACTION: Maintainer to diagnose and fix issue
Proposed blockers -----------------
1. gnome-control-center — Settings crashes when trying to edit WPA2 Enterprise wifi without a stored password — NEW ACTION: Upstream to diagnose and fix issue
Bug-by-bug detail =============
Accepted blockers -----------------
1. gnome-calendar — https://bugzilla.redhat.com/show_bug.cgi?id=2135772 — NEW Editing the recurring event freezes Calendar.
Fixing other recurring-event handling in Calendar reveals that the handling in general is, as upstream calls it, "stupidly broken." In short: with both (and only) weekly recurrence and "until date" termination, editing a recurring event causes Calendar to crash.
2. kernel — https://bugzilla.redhat.com/show_bug.cgi?id=2136234 — ASSIGNED No video on Raspberry Pi 4 with kernel 5.19.15 and 5.19.16 (testing)
Beginning with kernel 5.9.15, some users report no video on Raspberry Pi 4 devices. This may be related to vc4 driver patches that were backported to fix video on the Pi 3.
Proposed blockers -----------------
1. gnome-control-center — https://bugzilla.redhat.com/show_bug.cgi?id=2136471 — NEW Settings crashes when trying to edit WPA2 Enterprise wifi without a stored password
Editing (but not creating) a WPA2 Enterprise wifi connection without a stored password (e.g for authentication that uses tokens) causes Control Center to freeze. The connection cannot be removed through the GUI. Filed upstream as https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1905
Because of the openssl blocker, we are targeting 15 November. See the Fedora Magazine article for more information behind the reasoning: https://fedoramagazine.org/fedora-linux-37-update/
Action summary ====================
Accepted blockers -----------------
1. gnome-calendar — Editing the recurring event freezes Calendar. — NEW ACTION: Upstream to diagnose and fix issue
2. kwin — Plasma on Wayland hangs at startup when booting with nomodeset ("basic graphics" mode) on UEFI) — NEW ACTION: Kernel maintainers to build update with patch
3. openssl — upcoming critical openssl vulnerability — NEW ACTION: openssl maintainers to build version 3.0.7 when released
Proposed blockers -----------------
(none)
Bug-by-bug detail =============
Accepted blockers -----------------
1. gnome-calendar — https://bugzilla.redhat.com/show_bug.cgi?id=2135772 — NEW Editing the recurring event freezes Calendar.
Fixing other recurring-event handling in Calendar reveals that the handling in general is, as upstream calls it, "stupidly broken." In short: with both (and only) weekly recurrence and "until date" termination, editing a recurring event causes Calendar to crash.
2. kwin — https://bugzilla.redhat.com/show_bug.cgi?id=2136234 — NEW Plasma on Wayland hangs at startup when booting with nomodeset ("basic graphics" mode) on UEFI
The DRM driver advertises some formats that aren't actually supported by the hardware. Kwin naively believes the kernel, resulting in a failure to launch Plasma under certain conditions. A patch has been discussed upstream and will be added to an F37 kernel udpate.
3. openssl — https://bugzilla.redhat.com/show_bug.cgi?id=2137661 — NEW upcoming critical openssl vulnerability
A "critical" severity bug is fixed in an openssl release due Tuesday 1 November. That's about all we know at this point.
Action summary ====================
Accepted blockers -----------------
1. gnome-calendar — Editing the recurring event freezes Calendar. — VERIFIED ACTION: (none)
2. kernel — No video on Raspberry Pi 4 with kernel 5.19.15 and 5.19.16 (testing) — ASSIGNED ACTION: Kernel maintainers to build update with patch
3. kernel — Plasma on Wayland hangs at startup when booting with nomodeset ("basic graphics" mode) on UEFI due to simpledrm incorrectly advertising 10-bit pixel formats on 8-bit native framebuffers — VERIFIED ACTION: (none)
Proposed blockers -----------------
1. gnome-calendar — The calendar events are displayed as many times as the calendar gets opened. — NEW ACTION: QA to identify the conditions that cause this bug
Bug-by-bug detail =============
Accepted blockers -----------------
1. gnome-calendar — https://bugzilla.redhat.com/show_bug.cgi?id=2135772 — VERIFIED Editing the recurring event freezes Calendar.
Fixing other recurring-event handling in Calendar reveals that the handling in general is, as upstream calls it, "stupidly broken." In short: with both (and only) weekly recurrence and "until date" termination, editing a recurring event causes Calendar to crash. FEDORA-2022-ce3b8fbd4d contains a verified fix.
2. kernel — https://bugzilla.redhat.com/show_bug.cgi?id=2136234 — ASSIGNED No video on Raspberry Pi 4 with kernel 5.19.15 and 5.19.16 (testing)
Booting to a graphical environment on the Pi4 fails. This was fixed in kernel-5.19.16-300, but was reintroduced in the 6.0 kernel series due to a merge issue. A new build with a mergeable patch is needed.
3. kernel — https://bugzilla.redhat.com/show_bug.cgi?id=2137600 — VERIFIED Plasma on Wayland hangs at startup when booting with nomodeset ("basic graphics" mode) on UEFI due to simpledrm incorrectly advertising 10-bit pixel formats on 8-bit native framebuffers
The simpledrm driver offers formats that aren't actually supported and kwin ends up using one of the unsupported formats. FEDORA-2022-c4057cabb4 contains a verified fix.
Proposed blockers -----------------
1. gnome-calendar — https://bugzilla.redhat.com/show_bug.cgi?id=2139552 — NEW The calendar events are displayed as many times as the calendar gets opened.
Under some (not entirely clear to me) conditions, Calendar duplicates events in the display every time the calendar is open. This does not sync to remote calendar servers (e.g. Google Calendar) and resets on restart of the calendar service.
-
Adam Williamson -
Ben Cotton