Re: [Fedocal] Reminder meeting : Prioritized bugs and issues
On Tue, Apr 18, 2023 at 6:00 AM wrote: > > You are kindly invited to the meeting: >Prioritized bugs and issues on 2023-04-19 from 10:00:00 to 11:00:00 > America/Indiana/Indianapolis >At fedora-meetin...@irc.libera.chat > > More information available at: > https://docs.fedoraproject.org/en-US/program_management/prioritized_bugs/ > Source: https://calendar.fedoraproject.org//meeting/10144/ We will discuss the following nominated bugs: * English keyboard layout is erroneously used during initramfs phase (e.g. decrypting encrypted storage devices) instead of native layout, on Silverblue / ostree installs - https://bugzilla.redhat.com/show_bug.cgi?id=1890085 * Cannot copy/paste to/from KDE VMs - https://bugzilla.redhat.com/show_bug.cgi?id=2016563 * Windows with bitlocker enabled can't be booted, needs to use bootnext instead of chainloader - https://bugzilla.redhat.com/show_bug.cgi?id=2049849 * Live image made with BOOTX64.EFI from latest shim-x64-15.6-2 fails to boot on some boards - https://bugzilla.redhat.com/show_bug.cgi?id=2113005 In addition, we'll check in on the following accepted bugs: * It is possible to go through the initial setup without creating a root and without adding a user to the wheel group - https://bugzilla.redhat.com/show_bug.cgi?id=2015490 -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: new criterion proposal: toolbox functionality
On Tue, Apr 11, 2023 at 11:56 PM Sumantro Mukherjee wrote: > > Toolbox aka Toolbx should be usable. As a style matter, let's just cut this sentence. "usable" is vague and the next sentence offers more clarity. > Toolbox should be able to list, > create and provide the desired containerized environment to the user > without root privileges. Do we need to tighten the scope here? What sorts of failures are acceptable? If someone tries to create a toolbox that pulls in software from third-party repositories, I think we'd want to call that not our problem. > Toolbox images should be generally > functional. How does this differ from the previous sentence? Is "generally functional" more than list, create, and provide the containerized environment? > Footnote - "What does this cover?": > Toolbox's general functionality as covered by this test cases > https://fedoraproject.org/wiki/QA:Testcase_toolbox The test case seems to be much narrower than the text of the criterion implies. Is the test case insufficient or is the criterion too broad? > I think this criterion could target F39 Beta Release Criteria or Basic > Release Criteria [2]. I'd say this is a Beta (or possibly Final, although I'm not sure if I believe that) criterion for now. When/if ostree variants become our primary desktop deliverable, moving it to Basic would make sense to me. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Fedora Linux 38 blocker status summary
The current target is the early target date (18 April). Action summary Accepted blockers - 1. shim — Live image made with BOOTX64.EFI from latest shim-x64-15.6-2 fails to boot on some boards — NEW ACTION: kernel upstream to merge NX support Proposed blockers - 1. fedora-release — Fedora 38 Final needs a non-prerelease fedora-release package and fedora-repos with updates-testing disabled — MODIFIED ACTION: QA to verify update FEDORA-2023-ae8bf65eea Bug-by-bug detail = Accepted blockers - 1. shim — https://bugzilla.redhat.com/show_bug.cgi?id=2113005 — NEW Live image made with BOOTX64.EFI from latest shim-x64-15.6-2 fails to boot on some boards UEFI LoadOptions that start with NUL cause boot failure. This is fixed upstream in https://github.com/rhboot/shim/pull/505 but the SecureBoot signing process requires NX support in the kernel, which is still pending upstream. Proposed blockers - 1. fedora-release — https://bugzilla.redhat.com/show_bug.cgi?id=2185122 — MODIFIED Fedora 38 Final needs a non-prerelease fedora-release package and fedora-repos with updates-testing disabled Currently fedora-release and fedora-repos are in a pre-release state. Update https://bodhi.fedoraproject.org/updates/FEDORA-2023-ae8bf65eea contains a candidate fix. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [Fedocal] Reminder meeting : Prioritized bugs and issues
On Tue, Apr 4, 2023 at 6:00 AM wrote: > > You are kindly invited to the meeting: >Prioritized bugs and issues on 2023-04-05 from 10:00:00 to 11:00:00 > America/Indiana/Indianapolis >At fedora-meetin...@irc.libera.chat > > More information available at: > https://docs.fedoraproject.org/en-US/program_management/prioritized_bugs/ > Source: https://calendar.fedoraproject.org//meeting/10144/ There are 0 nominated bugs and the 1 accepted bug is making progress, so I am cancelling the Prioritized Bugs meeting. We'll meet again 19 April. As a reminder, this process exists but it only works if you nominate bugs. See https://docs.fedoraproject.org/en-US/program_management/prioritized_bugs/#_nomination for the kinds of bugs to nominate. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Fedora Linux 38 blocker status summary
The current target is the early target date (18 April). Action summary Accepted blockers - 1. kernel — anaconda failed to detect the fcoe target(only affects ixgbe) — NEW ACTION: Maintainers to diagnose issue NEEDINFO: lnie 2. plasma-workspace — Logging out of Plasma 5.27.3 on Wayland as the second user on the system resulted in a black screen — NEW ACTION: Maintainers to diagnose issue 3. shim — Live image made with BOOTX64.EFI from latest shim-x64-15.6-2 fails to boot on some boards — NEW ACTION: kernel upstream to merge NX support Proposed blockers - 1. abrt — crash data are erased occasionally — VERIFIED ACTION: (none) 2. Podman — shadow-utils installations fails with “cap_set_file failed” in toolbox/podman on F38 host ACTION: Maintainers to diagnose issue Bug-by-bug detail = Accepted blockers - 1. kernel — https://bugzilla.redhat.com/show_bug.cgi?id=2171350 — NEW anaconda failed to detect the fcoe target(only affects ixgbe) The installer does not detect attached FCOE storage using ixgbe. The device ends up in "NO-CARRIER state DORNMANT". 2. plasma-workspace — https://bugzilla.redhat.com/show_bug.cgi?id=2179591 — NEW Logging out of Plasma 5.27.3 on Wayland as the second user on the system resulted in a black screen In some cases, a race condition prevents a user on a system from logging out successfully. This appears to be an SELinux issue filed as RHBZ 2181010 for which FEDORA-2023-624eb88729 contains a verified fix. It seems that a failure of dbus-:1.2-org.kde.LogoutPrompt@0.service causes the sddm session to not be restarted. 3. shim — https://bugzilla.redhat.com/show_bug.cgi?id=2113005 — NEW Live image made with BOOTX64.EFI from latest shim-x64-15.6-2 fails to boot on some boards UEFI LoadOptions that start with NUL cause boot failure. This is fixed upstream in https://github.com/rhboot/shim/pull/505 but the SecureBoot signing process requires NX support in the kernel, which is still pending upstream. Proposed blockers - 1. abrt — https://bugzilla.redhat.com/show_bug.cgi?id=2177153 — VERIFIED MaxCrashReportsSize claims to be 5000 MB but is 1000 MB abrt is using a smaller size limit than the hard-coded default of 5000 MB. FEDORA-2023-eb09dd6406 containes a verified fix. 2. podman — https://bugzilla.redhat.com/show_bug.cgi?id=2183034 — NEW packages with file capabilities fail to install in podman on F38 host DNF update in a freshly-created f38 toolbox fails. The issue seems to only happen on F38 hosts; shadow-utlis is updatable in an F36 and F37 container and host using podman 4.4.1. Suspected issue is a change in Podman between 4.4.2 -> 4.4.3 or a different config file in F38. This does not appear to be specific to the shadow-utils package. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Fedora Linux 38 blocker status summary
igh priority reload requests. 3. gnome-shell — https://bugzilla.redhat.com/show_bug.cgi?id=2180277 — NEW gnome-shell crashes and sysops happens when users logout Logging out sometimes causes a crash. It may be caused by trying to exit with open windows. An upstream MR contains work-in-progress fixes: https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2722/ 4. gnome-software — https://bugzilla.redhat.com/show_bug.cgi?id=2181367 — MODIFIED Incorrect priority order of app sources Contrary to FESCo's requirement for the Unfiltered Flathub Change, flatpaks from Flathub sometimes take priority over Fedora RPMs. FEDORA-2023-49b5dec107 contains a candidate fix. 5. kwin — https://bugzilla.redhat.com/show_bug.cgi?id=2179591 — NEW Logging out of Plasma 5.27.3 on Wayland as the second user on the system resulted in a black screen In some cases, a race condition prevents the second user on a system from logging out successfully. This appears to be an SELinux issue filed as RHBZ 2181010. An upstream PR contains a candidate fix: https://github.com/fedora-selinux/selinux-policy/pull/1628 -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: new criterion proposal: Window manager functionality
On Wed, Mar 22, 2023 at 3:58 AM Kamil Paral wrote: > > Here's a second draft. I took feedback here and also from the QA meeting [1]. > The split between the milestones makes this harder to read and compare. If > you have better ideas on how to do it, please tell me :-) I like it. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Fedora Linux 38 blocker status summary
d. The proposed `vga=normal` workaround does not appear to work. 7. mutter — https://bugzilla.redhat.com/show_bug.cgi?id=2175809 — VERIFIED Session crash when reverting Display settings Applying a change to Display settings and then reverting (or pressing Escape when presented with the revert dialog) results in a crash. Letting the dialog window time out does not crash. FEDORA-2023-6cec60a347 contains a verified fix. 8. mutter — https://bugzilla.redhat.com/show_bug.cgi?id=2177982 — VERIFIED Crash when using Win+P shortcut Using Win+P to switch between displays configuration crashes gnome-shell. FEDORA-2023-6cec60a347 contains a verified fix. 9. nautilus — https://bugzilla.redhat.com/show_bug.cgi?id=2176766 — VERIFIED Dragging files is Nautilus doesn't work as expected, quick movements result in a selection box instead In order to successfully drag-and-drop a file, you must first hold the mouse still with the left button pressed for ~half a second. FEDORA-2023-287e6e502b contains a verified fix. 10. openssh — https://bugzilla.redhat.com/show_bug.cgi?id=2172956 — POST Update hostkey migration to support OSTree systems and dynamically detect hostkey location rpm-ostree systems don't run RPM scriptlets on upgrade, which could result in an upgrade locking users out of remote machines. Package pull requests https://src.fedoraproject.org/rpms/fedora-release/pull-request/253 and https://src.fedoraproject.org/rpms/openssh/pull-request/45 contain a candidate fix. 11. sddm — https://bugzilla.redhat.com/show_bug.cgi?id=2174563 — NEW Virtual keyboard (on-screen) not working at sddm-wayland-plasma The virtual keyboard at the login screen does not appear when you click the appropriate button. This appears to be a Wayland-specific issue; reverting to X11 allows the keyboard to work as expected. 12. shim — https://bugzilla.redhat.com/show_bug.cgi?id=2113005 — NEW Live image made with BOOTX64.EFI from latest shim-x64-15.6-2 fails to boot on some boards UEFI LoadOptions that start with NUL cause boot failure. This is fixed upstream in https://github.com/rhboot/shim/pull/505 but the SecureBoot signing process requires NX support in the kernel, which is still pending upstream. Proposed blockers - 1. f38-backgrounds — https://bugzilla.redhat.com/show_bug.cgi?id=2178172 — VERIFIED The default wallpaper isn't listed among available wallpapers The default background is correctly applied, but if the users switches to a different wallpaper, the default is not visible in the selection. FEDORA-2023-359dafca1d contains a verified fix. 2. gnome-abrt — https://bugzilla.redhat.com/show_bug.cgi?id=2177153 — NEW crash data are erased occasionally It appears that abrt is removing report data when disk usage exceeds a threshold, but it's not clear why the reporter is expericing this worse than others. There may be some user experience improvements to make. In any case, the vote looks likely to be for rejecting this as a blocker. 3. gnome-calendar — https://bugzilla.redhat.com/show_bug.cgi?id=2177993 — NEW Crash/Hang when clicking a modified Google event right after editing it (due to the preview popover) Clicking on a remote event immediately after editing it results in either a crash or an unresponsive window. Waiting a few seconds before clicking results in expected behavior. 4. ibus — https://bugzilla.redhat.com/show_bug.cgi?id=2156108 — MODIFIED ibus: XFree(): ibus-x11 killed by SIGABRT Typing is sometimes "sluggish" with frequent pauses. Eventually ibus crashes. FEDORA-2023-e0df9e598e contains a candidate fix. 5. mutter — https://bugzilla.redhat.com/show_bug.cgi?id=2178167 — POST Fullscreen mode is broken for many games Many games fail to work in fullscreen and if they launch in fullscreen, they may not be usable at all. Upstream MR https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2910 contains a candidate fix. 6. xdg-desktop-portal-kde — https://bugzilla.redhat.com/show_bug.cgi?id=2178971 — NEW xdg-desktop-portal-kde is launching and crashing when SDDM launches the Wayland greeter When the greeter launches, xdg-desktop-portal-kde also launches and crashes. This appears to only happen on Wayland. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: new criterion proposal: Window manager functionality
On Fri, Mar 17, 2023 at 5:48 AM Kamil Paral wrote: > > The desktop environment must work correctly when displaying common > application content - that includes regular application windows, video > output, games and possibly other common content. Regular operations like > windows close/resize/maximize/minimize/fullscreen (when > supported/applicable), windows switching, using windows on virtual > workspaces, and similar common operations must behave as expected. Thinking like an editor for a moment, this feels a little redundant in places. I agree with the general concept, so this is entirely a presentation issue and I will not push back if you disagree. :But how about something more like: The desktop environment must perform regular operations like windows close/resize/maximize/minimize/fullscreen (when supported/applicable), windows switching, using windows on virtual workspaces, and similar common operations as expected. Common application content such as regular application windows, video output, and games must be displayed correctly. > Footnote - "What does this cover?": > A small number of misbehaving applications is not a violation of this > criterion. The goal of this criterion is to ensure general functionality for > different types of applications and their operations. An example of a > violation would be e.g. if a significant number of QT applications couldn't > be resized (but they should be), or if all Java applications failed to > display any content. I'd also add something that makes it clear if it's the application not displaying the content correctly, that's out of scope for this criterion. I can't think of a good way to phrase that. But I wouldn't want someone to think Joe's Fancy Pew Pew Pew Game having a glitchy display would violate this. > I think this criterion could target F38 Beta Release Criteria [3] or Basic > Release Criteria [4]. Definitely Basic for the same reason as Neal gave. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Fedora Linux 38 blocker status summary
d then un-deleting does not appear to fully undelete it. 7. mutter — https://bugzilla.redhat.com/show_bug.cgi?id=2175809 — POST Session crash when reverting Display settings Applying a change to Display settings and then reverting (or pressing Escape when presented with the revert dialog) results in a crash. Letting the dialog window time out does not crash. Upstream MR contains a candidate fix: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2901 8. nautilus — https://bugzilla.redhat.com/show_bug.cgi?id=2176766 — NEW Dragging files is Nautilus doesn't work as expected, quick movements result in a selection box instead In order to successfully drag-and-drop a file, you must first hold the mouse still with the left button pressed for ~half a second. 9. sddm — https://bugzilla.redhat.com/show_bug.cgi?id=2176782 — NEW SDDM doesn't start in basic graphics mode in BIOS mode In BIOS mode only, sddm results in a blank screen when using basic graphics mode. This may be the result of a SimpleDRM device not being created. 10. totem — https://bugzilla.redhat.com/show_bug.cgi?id=2176726 — NEW totem crashes everytime when users try to delete a video Deleting a video results in an application crash, but only when there is only one video. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Fedora Linux 38 blocker status summary
The current target release date is the early target date (2023-03-14). The Go/No-Go meeting will be Thursday! Action summary Accepted blockers - 1. distribution — Workstation boot x86_64 image exceeds maximum size — POST ACTION: gdb maintainers to remove the 'Recommends' for gcc-gdb-plugin from gdb 2. crypto-policies — Insecure installed RPMs (like Google Chrome) prevent system updates in F38, can't be removed — NEW ACTION: Upstream to implement MR #129 Proposed blockers - 1. gnome-session — reboot/poweroff/logout from GNOME are 60 seconds delayed without 3D acceleration — NEW ACTION: Maintainers to diagnose issue 2. gnupg2 — revert the RFC4880bis from defaults — NEW ACTION: Maintainers to revert inclusion of RFC4880bis 3. initial-setup — User creation and root password setting do not work on minimal install, so cannot log into installed system — NEW ACTION: Maintainers to diagnose issue 4. kernel — Black screen when amdgpu started during 6.2-rc1 boot with AMD IOMMU enabled — NEW ACTION: Maintainers to package update which includes upstream patches 5. mutter — XWayland apps steal focus — NEW ACTION: Maintainers to build update with upstream merge request 6. sddm — Virtual keyboard (on-screen) not working at sddm-wayland-plasma — NEW ACTION: Maintainers to diagnose issue Bug-by-bug detail = Accepted blockers - 1. distribution — https://bugzilla.redhat.com/show_bug.cgi?id=2149246 — POST Workstation boot x86_64 image exceeds maximum size Changes to linux-firmware briefly brought the Worktation image below the limit. Removing the recommendation (in gdb) of gcc-gdb-plugin, which is "largely broken", should reduce the image size below limits. 2. crypto-policies — https://bugzilla.redhat.com/show_bug.cgi?id=2170878 — NEW Insecure installed RPMs (like Google Chrome) prevent system updates in F38, can't be removed Some third-party repos (including Google Chrome) that sign packages with SHA-1 cannot be uninstalled, which breaks upgrades. This was designated a blocker by FESCo. Work is in progress upstream to allow RPM to permit SHA-1 in the default policy while third-party repos update to a supported hash function: https://gitlab.com/redhat-crypto/fedora-crypto-policies/-/merge_requests/129 Proposed blockers - 1. gnome-session — https://bugzilla.redhat.com/show_bug.cgi?id=2174753 — NEW reboot/poweroff/logout from GNOME are 60 seconds delayed without 3D acceleration On machines (physical and virtual) without 3D acceleration, clicking the reboot/poweroff/logout buttons has no apparent effect for 60 seconds. A second click or using command line commands works immediately. 2. gnupg2 — https://bugzilla.redhat.com/show_bug.cgi?id=2175155 — NEW revert the RFC4880bis from defaults GnuPG 2.4.0 made a potentially-incompatible change. A PR is pending to revert this: https://src.fedoraproject.org/rpms/gnupg2/pull-request/15 3. initial-setup — https://bugzilla.redhat.com/show_bug.cgi?id=2175244 — NEW User creation and root password setting do not work on minimal install, so cannot log into installed system On the Minimial image only, initial-setup silently fails to create a user. This results in a system with no usable user account. 4. kernel — https://bugzilla.redhat.com/show_bug.cgi?id=2156691 — NEW Black screen when amdgpu started during 6.2-rc1 boot with AMD IOMMU enabled Kernel 6.2.0 introduced an issue that causes the system to hang when booting with amdgpu. There are upstream patches targeted for 6.2.2 that contain a candidate fix. 5. mutter — https://bugzilla.redhat.com/show_bug.cgi?id=2173985 — NEW XWayland apps steal focus Alt+Tab switching, as well as (sometimes) clicking on windows does not focus the window. This seems to largely affect Wine, Java, and Chromium applications. This may have been introduced by upstream commit a68b8e95. Upstream MR #2841 has a fix for Chrome and Electron apps. 6. sddm — https://bugzilla.redhat.com/show_bug.cgi?id=2174563 — NEW Virtual keyboard (on-screen) not working at sddm-wayland-plasma The virtual keyboard at the login screen does not appear when you click the appropriate button. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [Proposal] Dropping YYYY-MM-DD from Test Day Page Title
I don't see that including the date in the title adds much value, particularly since it creates the potential for confusion. Using the release (e.g. 'F38') or release+milestone when there are multiple in a cycle (e.g. "F38beta") provides uniqueness in a way that's much easier to manage. I'm in favor of dropping dates from the title. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Fedora Linux 38 blocker status summary
The current target release date is the early target date (2023-03-14). Action summary Accepted blockers - 1. distribution — Workstation boot x86_64 image exceeds maximum size — ASSIGNED ACTION: Workstation WG to reduce image size or increase the limit 2. kwin — kwin_wayland often crashed when used as the sddm Wayland compositor and logging out of Plasma resulting in a black screen — ON_QA ACTION: QA to verify FEDORA-2023-81ff51758d Proposed blockers - 1. gdb — Can't open file anon_inode:i915.gem which was expanded to anon_inode:i915.gem during file-backed mapping note processing — NEW ACTION: Maintainer to diagnose issue 2. pkgconf — Don't depend on system-rpm-config — ON_QA ACTION: QA to verify FEDORA-2023-766817d642 Bug-by-bug detail = Accepted blockers - 1. distribution — https://bugzilla.redhat.com/show_bug.cgi?id=2149246 — ASSIGNED Workstation boot x86_64 image exceeds maximum size Changes to linux-firmware briefly brought the Worktation image below the limit. However, the Fedora-38-20230216.n.0 went above the limit again. 2. kwin — https://bugzilla.redhat.com/show_bug.cgi?id=2168034 — ON_QA kwin_wayland often crashed when used as the sddm Wayland compositor and logging out of Plasma resulting in a black screen Logging out of Plasma sometimes triggers a kwin crash. FEDORA-2023-81ff51758d contains a candidate fix. Proposed blockers - 1. gdb — https://bugzilla.redhat.com/show_bug.cgi?id=2172342 — NEW Can't open file anon_inode:i915.gem which was expanded to anon_inode:i915.gem during file-backed mapping note processing Reporting a bug with gnome-abrt fails because no fram and no thread found in the backtrace that gdb produces. 2. pkgconf — https://bugzilla.redhat.com/show_bug.cgi?id=2172406 — ON_QA Don't depend on system-rpm-config pkgconf pulls in ~22 new packages as a runtime dependency, which don't appear to be strictly necessary. FEDORA-2023-766817d642 contains a candidate fix. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Fedora Linux 38 blocker status summary
The F38 Beta freeze begins on 21 February. The current target release date is the early target date (2023-03-14). Action summary Accepted blockers - 1. distribution — Workstation boot x86_64 image exceeds maximum size — ASSIGNED ACTION: Workstation WG to reduce image size or increase the limit Proposed blockers - 1. glusterfs — libglusterd0 prevents upgrades to Fedora 38 — NEW ACTION: Maintainer to diagnose issue 2. kwin — kwin_wayland often crashed when used as the sddm Wayland compositor and logging out of Plasma resulting in a black screen — NEW ACTION: Maintainer to diagnose issue Bug-by-bug detail = Accepted blockers - 1. distribution — https://bugzilla.redhat.com/show_bug.cgi?id=2149246 — ASSIGNED Workstation boot x86_64 image exceeds maximum size Changes to linux-firmware briefly brought the Worktation image below the limit. However, the Fedora-38-20230216.n.0 went above the limit again. Proposed blockers - 1. glusterfs — https://bugzilla.redhat.com/show_bug.cgi?id=2169401 — NEW libglusterd0 prevents upgrades to Fedora 38 libglusterd0, which is preinstalled in F37 Workstation, is not provided by anything in the F38 repos, so upgrades fail. 2. kwin — https://bugzilla.redhat.com/show_bug.cgi?id=2168034 — NEW kwin_wayland often crashed when used as the sddm Wayland compositor and logging out of Plasma resulting in a black screen Logging out of Plasma sometimes triggers a kwin crash. This may be limited to running in a virtual machine. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
F37 retrospective survey open through 9 March
In case you missed it on the Community Blog[1], the F37 retrospective survey[2] is open through 9 March. As a reminder, this survey is about the _process_ of creating F37, not the end result. This is the third such survey, so we'll be able to start putting together trends. This survey uses Fedora's LimeSurvey instance. Responses are anonymous. [1] https://communityblog.fedoraproject.org/f37-retrospective-survey-open/ [2] https://fedoraproject.limequery.com/37 -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora Linux 38 blocker status summary
We've branched F38 from Rawhide, so it's time to start everyone's
favorite Friday email from Ben! The F38 Beta freeze begins on 21
February. The current target release date is the early target date
(2023-03-14).
Action summary
Accepted blockers
-
1–3. distribution — {Workstation,Everything,Server} boot x86_64 image
exceeds maximum size — ASSIGNED
ACTION: Relevant Teams to reduce image size or increase the limit
Proposed blockers
-
1. anaconda — installer fails to boot in text mode or rescue mode with
systemd 253 — MODIFIED
ACTION: Maintainers to build an update that includes upstream PR
2. grub2 — ext4 filessystem support missing — NEW
ACTION: Maintainer to diagnose issue
NEEDINFO: ausil
3. kwin — kwin_wayland often crashed when used as the sddm Wayland
compositor and logging out of Plasma resulting in a black screen — NEW
ACTION: Maintainer to diagnose issue
4. mesa — KDE crashes on start with mesa-23.0.0~rc3-3.fc38 — ASSIGNED
ACTION: Maintainer to diagnose issue
Bug-by-bug detail
=
Accepted blockers
-
1–3. distribution — {Workstation,Everything,Server} boot x86_64 image
exceeds maximum size — ASSIGNED
https://bugzilla.redhat.com/show_bug.cgi?id=2149246
https://bugzilla.redhat.com/show_bug.cgi?id=2151495
https://bugzilla.redhat.com/show_bug.cgi?id=2151497
Image sizes exceed the specified limits. The choices are to either
shrink the image by removing packages or to riase the limits.
Proposed blockers
-
1. anaconda — https://bugzilla.redhat.com/show_bug.cgi?id=2165433 — MODIFIED
installer fails to boot in text mode or rescue mode with systemd 253
anaconda is writing systemd units to an unexpected area. Upstream PR
4534 contains a candidate fix:
https://github.com/rhinstaller/anaconda/pull/4534
2. grub2 — https://bugzilla.redhat.com/show_bug.cgi?id=2166412 — NEW
ext4 filessystem support missing
Between grub2-2.06-76 and grub2-2.06-78, grub2 apparently lost the
ability to detect ext4 filesystems.
3. kwin — https://bugzilla.redhat.com/show_bug.cgi?id=2168034 — NEW
kwin_wayland often crashed when used as the sddm Wayland compositor
and logging out of Plasma resulting in a black screen
Logging out of Plasma sometimes triggers a kwin crash. This may be
limited to running in a virtual machine.
4. mesa — https://bugzilla.redhat.com/show_bug.cgi?id=2164667 — ASSIGNED
KDE crashes on start with mesa-23.0.0~rc3-3.fc38
A recent mesa update caused both GNOME and KDE to crash on start.
Update FEDORA-2023-40b973fa06 fixed GNOME, but KDE is still seeing
this issue. The root cause is still uncertain.
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
Re: Proposed change to rendering of release schedule ics file
Sure, no problem. I was under the assumption that the packager dashboard parsed the json file and not the ics file, so this change may be more impactful than I thought. But I'll wait until you've had a chance to look. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Proposed change to rendering of release schedule ics file
Hi everyone, I want to get feedback before I make a change to how Fedora Linux schedules are generated. As reported in schedule#91[1], the current ics files include very long tasks that aren't particularly useful. I have a plan for how to address that, but first I want to check that it won't impact how people currently use the ics files. If you're using the Fedora Linux schedule ics files, please see the details in the Pagure issue[2]. If this will affect how you or your team use those files, comment in the issue before 13 February. Note that this will not change how the html or json versions are produced. [1] https://pagure.io/fedora-pgm/schedule/issue/91 [2] https://pagure.io/fedora-pgm/schedule/issue/91#comment-838492 -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [Fedocal] Reminder meeting : Prioritized bugs and issues
On Tue, Jan 10, 2023 at 5:35 AM wrote: > > You are kindly invited to the meeting: >Prioritized bugs and issues on 2023-01-11 from 10:00:00 to 11:00:00 > America/Indiana/Indianapolis >At fedora-meetin...@irc.libera.chat > > More information available at: > https://docs.fedoraproject.org/en-US/program_management/prioritized_bugs/ There are no nominated prioritized bugs, so I'm cancelling this week's meeting. I follow up with the currently accepted bugs out of band. The next meeting is scheduled for 25 January. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [Fedocal] Reminder meeting : Prioritized bugs and issues
On Tue, Nov 29, 2022 at 5:00 AM wrote: > > You are kindly invited to the meeting: >Prioritized bugs and issues on 2022-11-30 from 10:00:00 to 11:00:00 > America/Indiana/Indianapolis >At fedora-meetin...@irc.libera.chat > > More information available at: > https://docs.fedoraproject.org/en-US/program_management/prioritized_bugs/ We will evaluate the following proposed Prioritized Bugs: * Recent kernels cause problem with microphone LED on Thinkpad X1 Carbon gen. 9 - https://bugzilla.redhat.com/show_bug.cgi?id=2134824 * Do Not Disturb enabled when screens are not mirrored - https://bugzilla.redhat.com/show_bug.cgi?id=2143358 In addition, we'll follow up on the accepted bugs: * It is possible to go through the initial setup without creating a root and without adding a user to the wheel group - https://bugzilla.redhat.com/show_bug.cgi?id=2015490 -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [Fedocal] Reminder meeting : Prioritized bugs and issues
On Tue, Nov 15, 2022 at 11:29 AM wrote: > > You are kindly invited to the meeting: >Prioritized bugs and issues on 2022-11-16 from 10:00:00 to 11:00:00 > America/Indiana/Indianapolis >At fedora-meetin...@irc.libera.chat > > More information available at: > https://docs.fedoraproject.org/en-US/program_management/prioritized_bugs/ We will discuss the following nominated bug: * ABRT on KDE can't store any passwords: Secret Service is not available - https://bugzilla.redhat.com/show_bug.cgi?id=2141237 -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F37 Final blocker status update
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.
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
Re: [Fedocal] Reminder meeting : Prioritized bugs and issues
On Tue, Nov 1, 2022 at 6:00 AM wrote: > > You are kindly invited to the meeting: >Prioritized bugs and issues on 2022-11-02 from 10:00:00 to 11:00:00 > America/Indiana/Indianapolis >At fedora-meetin...@irc.libera.chat > > More information available at: > https://docs.fedoraproject.org/en-US/program_management/prioritized_bugs/ There are no nominated or accepted bugs, so the meeting is cancelled. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F37 Final blocker status update
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.
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
Re: F37 Final blocker status update
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 -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Thoughts welcome: interface between automated test gating and the "critical path"
On Mon, Oct 17, 2022 at 8:54 PM Adam Williamson wrote: > > Does anyone object to these proposed changes? Thanks! Ship it! -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F37 Final blocker status update
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) -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F37 Final blocker status update
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. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [Fedocal] Reminder meeting : Prioritized bugs and issues
On Tue, Oct 4, 2022 at 6:00 AM wrote: > > You are kindly invited to the meeting: >Prioritized bugs and issues on 2022-10-05 from 10:00:00 to 11:00:00 > America/Indiana/Indianapolis >At fedora-meetin...@irc.libera.chat > > More information available at: > https://docs.fedoraproject.org/en-US/program_management/prioritized_bugs/ > Source: https://calendar.fedoraproject.org//meeting/10144/ We will evaluate the following nominated bugs: * [abrt] gnome-shell: clutter_actor_destroy_all_children(): gnome-shell killed by SIGABRT - https://bugzilla.redhat.com/show_bug.cgi?id=2127826 * Systemd causes PC Speaker to emit a loud beep during reboot/poweroff, after suspend&resume - https://bugzilla.redhat.com/show_bug.cgi?id=2129387 -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F37 Final blocker status update
ance 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 -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F37 Final blocker status update
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 -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject
F37 Final blocker status update
ause 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 -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [Test-Announce] Fedora Linux 37 Beta Release Announcement
On Tue, Sep 13, 2022 at 7:27 PM Adam Williamson wrote: > > There's another issue we need to take care of here for Final: CoreOS is > supposed to become an Edition for F37, and Cloud is supposed to return > as one. > > Ideally this announcement should have included them alongside > Workstation and Server somehow, but the Final announcement *definitely* > needs to if we're considering them as editions. That's on me, at least in part. I've submitted a PR for the Beta template[1] and will make sure mattdm's Final announcement includes it. > That implies that we also need to work out how to present them on > getfedora.org. The Edition teams should be working with the Websites team to make that happen. I'll check with them to see how that's progressing. [1] https://pagure.io/releng/pull-request/11031 -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Release criteria proposal: require GNOME Shell extension install/remove to work
On Mon, Sep 12, 2022 at 3:35 PM Adam Williamson wrote: > > === GNOME extensions === > > On Fedora Workstation, it must be possible to install and remove > extensions by visiting https://extensions.gnome.org in the default web > browser, after installing the required browser extension. > > # > > Do folks think this is important enough to block Final release on? Assuming the desktop folks don't say "OMG there's no way we could handle this", then I'm on board with making this a final criterion. This is one of those "we'll get dragged in reviews if it doesn't work" sorts of things. The wording looks good to me. I'm trying to think of an escape hatch we can give ourselves if it goes particularly sideways at some point, but maybe the "difficult to fix" exception would be good enough. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F37 Beta blocker status email
The Go/No-Go meeting for the early F37 Beta target date is Thursday. Action summary Proposed blockers - 1. gnome-initial-setup — Unable to set up enterprise account with gnome-initial-setup due to missing buttons — NEW ACTION: Upstream to diagnose and fix issue 2. kernel — Kernel panics during boot when laptop connected to a usb-c dock — NEW ACTION: Testers to identify the scope of affected hardware, maintainers to diagnose issue. 3. kernel — kernel regression causing mdraid systems to hang during reboot — ON_QA ACTION: QA to verify FEDORA-2022-ccb0138bb6 Bug-by-bug detail = Proposed blockers - 1. gnome-initial-setup — https://bugzilla.redhat.com/show_bug.cgi?id=2123494 — NEW Unable to set up enterprise account with gnome-initial-setup due to missing buttons The g-i-s dialog for connecting to enterprise authentication does not display the "continue" or "cancel" buttons. Filed upstream as https://gitlab.gnome.org/GNOME/gnome-initial-setup/-/issues/152 2. kernel — https://bugzilla.redhat.com/show_bug.cgi?id=2119305 — NEW Kernel panics during boot when laptop connected to a usb-c dock Recent kernels are failing on some hardware when connected to a USB-C dock. The scope of hardware affected is unclear. 3. kernel — https://bugzilla.redhat.com/show_bug.cgi?id=2121791 — ON_QA kernel regression causing mdraid systems to hang during reboot Beginning with commit a09b314005f3 (in 5.19-rc4), software raid devices would result in an unbounded wait for reboot. This is observed across multiple Fedora Linux releases. FEDORA-2022-ccb0138bb6 contains a candidate fix. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Thoughts welcome: interface between automated test gating and the "critical path"
From my perspective, anything that blocks the release is on the critical path. So any time there's a violation of the release criteria and the package is not on the critical path definition, that's a bug in the definition. I recognize that this is a somewhat naïve view. For one, it may broaden the definition beyond the current capacity of our test infrastructure. It also may broaden the definition beyond what maintainers are willing to put up with. These are both legitimate problems. But the closer we can get to this ideal state, the better. For anyone who is curious, I just searched for all accepted blockers in the "Fedora" product in Bugzilla. 327 components have been a blocker at least once. Some of those may no longer be blocking and others will be added over time as our criteria change. The full list with counts is at https://bcotton.fedorapeople.org/release-blocking-components.csv if you're interested. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F37 Beta blocker status email
Action summary Accepted blockers - 1. osinfo-db — failed to install server iso with virt-install due to the missing of isolinux in the media — NEW ACTION: Maintainers to create update with upstream MR 501 2. sddm — Logout from KDE session on Rawhide goes to console, not SDDM — ASSIGNED ACTION: Maintainers to diagnose issue Proposed blockers - 1. distribution — "dnf update" runs out of memory on swapless machines with 1G or less of RAM — ASSIGNED ACTION: mattdm to coordinate long-term solution 2. openssl-pkcs11 — dnssec-keyfromlabel fails with openssl-pkcs11-0.4.12-1.fc36 — NEW ACTION: Maintainers to diagnose issue 3. rpm-ostree — Failing services in new Fedora IoT installations with RO /sysroot — NEW ACTION: IoT to apply PR #8 Bug-by-bug detail = Accepted blockers - 1. osinfo-db — https://bugzilla.redhat.com/show_bug.cgi?id=2103835 — NEW failed to install server iso with virt-install due to the missing of isolinux in the media virt-install fails because there's no isolinux path, where it looks for vmlinuz and initrd.img . Upstream merge request 501 contains a candidate fix. This should allow us to see if RHBZ 2119633 also affects F37. 2. sddm — https://bugzilla.redhat.com/show_bug.cgi?id=2110801 — NEW Logout from KDE session on Rawhide goes to console, not SDDM After logging out of KDE Plasma, you end up at a console on tty2. SDDM had been running on tty1 but just shows a flashing cursor. Update FEDORA-2022-8456442870 reverted sddm back to X11, however the lastest compose appears to still be using Wayland. Proposed blockers - 1. distribution — https://bugzilla.redhat.com/show_bug.cgi?id=1907030 — NEW "dnf update" runs out of memory on swapless machines with 1G or less of RAM dnf is killed by oom-kill on machines with 512 MB of RAM. Adding a swap disk or disabling the updates repo works around this issue. Recently, FCOS has seen this behavior with 1 GB VMs. The issue appears to be the size of the metadata for the repository. mattdm is going to coordinate a long-term solution for this. 2. openssl-pkcs11 — https://bugzilla.redhat.com/show_bug.cgi?id=2115865 — NEW dnssec-keyfromlabel fails with openssl-pkcs11-0.4.12-1.fc36 Tests in openQA cannot resolve kojipkgs.fedoraproject.org. Previous F37 build (openssl-pkcs11-0.4.12-1.fc37) behaves as expected. The corresponding versions both work on F36. Disabling dnssec on the server is a workaround. 3. rpm-ostree — https://bugzilla.redhat.com/show_bug.cgi?id=2121197 — NEW Failing services in new Fedora IoT installations with RO /sysroot The switch to read-only /sysroot results in IoT tests with many failing services. https://pagure.io/fedora-iot/ostree/pull-request/8 contains a candidate fix. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F37 Beta blocker status email
Action summary Accepted blockers - 1. kde-settings — KDE needs to pick up F37 backgrounds — ON_QA ACTION: None 2. sddm — Logout from KDE session on Rawhide goes to console, not SDDM — POST ACTION: Maintainers to build package with X11 by default Proposed blockers - 1. anaconda — Anaconda will not start F37 Raw — NEW ACTION: Reporter to provide requested log files NEEDINFO: aalmeleh.whatever.0101 2. dnf — "dnf update" runs out of memory on swapless 0.5 GiB RAM machine — NEW ACTION: Maintainers to investigate short-term dnf improvements NEEDINFO: jmracek 3. openssl-pkcs11 — FreeIPA client enrollment fails due to DNS issues with openssl-pkcs11-0.4.12-2.fc37 — NEW ACTION: Maintainers to diagnose issue 4. osinfo-db — failed to install server iso with virt-install due to the missing of isolinux in the media — NEW ACTION: Maintainers to diagnose issue Bug-by-bug detail = Accepted blockers - 1. kde-settings — https://bugzilla.redhat.com/show_bug.cgi?id=2117706 — ON_QA KDE needs to pick up F37 backgrounds New desktop backgrounds require a new KDE settings update. Fixed in FEDORA-2022-fe8729bced. 2. sddm — https://bugzilla.redhat.com/show_bug.cgi?id=2110801 — NEW Logout from KDE session on Rawhide goes to console, not SDDM After logging out of KDE Plasma, you end up at a console on tty2. SDDM had been running on tty1 but just shows a flashing cursor. This appears to be specific to Wayland, so a PR is pending to revert to and X11 default. Proposed blockers - 1. anaconda — https://bugzilla.redhat.com/show_bug.cgi?id=2101229 — NEW Anaconda will not start F37 Raw Neither clicking the desktop icon nor the taskbar icon will launch anaconda. openQA is not experiencing this. Using basic graphics mode results in the expected behavior. 2. dnf — https://bugzilla.redhat.com/show_bug.cgi?id=1907030 — NEW "dnf update" runs out of memory on swapless 0.5 GiB RAM machine dnf is killed by oom-kill on machines with 512 MB of RAM. Adding a swap disk or disabling the updates repo works around this issue. Recently, FCOS has seen this behavior with 1 GB VMs. The issue appears to be the size of the metadata for the repository. The short term fixes look like they may need to be made on the repo side, not in dnf. 3. openssl-pkcs11 — https://bugzilla.redhat.com/show_bug.cgi?id=2117859 — NEW FreeIPA client enrollment fails due to DNS issues with openssl-pkcs11-0.4.12-2.fc37 Tests in openQA cannot resolve kojipkgs.fedoraproject.org. Previous F37 build (openssl-okcs11-0.4.12-1.fc37) behaves as expected. The corresponding versions both work on F36. Disabling dnssec on the server is a workaround. 4. osinfo-db — https://bugzilla.redhat.com/show_bug.cgi?id=2103835 — NEW failed to install server iso with virt-install due to the missing of isolinux in the media virt-install fails because there's no isolinux path, where it looks for vmlinuz and initrd.img . An upstream fix has been released in F35, F36, and F37 updates, but it does not appear to fully solve the problem on F37 and Rawhide. See also RHBZ 2119633. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
F37 Beta blocker status email
With F37 now branched from Rawhide, it's time to pick up our weekly blocker status emails! Action summary Accepted blockers - 1. kde-settings — KDE needs to pick up F37 backgrounds — NEW ACTION: Maintainers to make new kde-settings build Proposed blockers - 1. anaconda — Anaconda crashed on signal 11 - keyboard layout encryption password prompt — ON_QA ACTION: QA, reporter to verify anaconda-37.12-1 NEEDINFO: doug.hs 2. anaconda — Anaconda will not start F37 Raw — NEW ACTION: Reporter to provide requested log files NEEDINFO: aalmeleh.whatever.0101 3. dnf — "dnf update" runs out of memory on swapless 0.5 GiB RAM machine — NEW ACTION: Manitainers to investigate short-term dnf improvements NEEDINFO: jmracek 4. dracut — Media check fails with checkisomd5 "service failed because the control process exited with error code" — POST ACTION: Maintainers to build with upstream PR 5. polkit — Switching users in Gnome results in polkitd errors that prevent powering off the computer. — ASSIGNED ACTION: Maintainers to diagnose issue 6. sddm — Logout from KDE session on Rawhide goes to console, not SDDM — NEW ACTION: Maintainers to diagnose issue Bug-by-bug detail = Accepted blockers - 1. kde-settings — https://bugzilla.redhat.com/show_bug.cgi?id=2117706 — NEW KDE needs to pick up F37 backgrounds New desktop backgrounds require a new KDE settings update. Proposed blockers - 1. anaconda — https://bugzilla.redhat.com/show_bug.cgi?id=2070823 — ON_QA Anaconda crashed on signal 11 - keyboard layout encryption password prompt Clicking the keyboard layout button in the LUKS decryption popup crashes anaconda. anaconda-37.12-1 contains a candidate fix. 2. anaconda — https://bugzilla.redhat.com/show_bug.cgi?id=2101229 — NEW Anaconda will not start F37 Raw Neither clicking the desktop icon nor the taskbar icon will launch anaconda. openQA is not experiencing this. Using basic graphics mode results in the expected behavior. 3. dnf — https://bugzilla.redhat.com/show_bug.cgi?id=1907030 — NEW "dnf update" runs out of memory on swapless 0.5 GiB RAM machine dnf is killed by oom-kill on machines with 512 MB of RAM. Adding a swap disk or disabling the updates repo works around this issue. Recently, FCOS has seen this behavior with 1 GB VMs. The issue appears to be the size of the metadata for the repository. The short term fixes look like they may need to be made on the repo side, not in dnf. 4. dracut — https://bugzilla.redhat.com/show_bug.cgi?id=2107858 — POST Media check fails with checkisomd5 "service failed because the control process exited with error code" Media check fails on certain hardware. Skipping the media check results in a successful boot. Upstream PR #1882 contains a candidate fix: https://github.com/dracutdevs/dracut/pull/1882 5. polkit — https://bugzilla.redhat.com/show_bug.cgi?id=2109145 — ASSIGNED Switching users in Gnome results in polkitd errors that prevent powering off the computer. Under certain conditions (including but not limited to several user switches), the power off button disappears from the GNOME menu due to a polkitd error. `systemctl poweroff -i` as an unprivileged user does not work. It may be an issue with using the duktape JS engine instead of mozjs91. polkit-121-3 reverts to mozjs91, but is not a sufficient fix. 6. sddm — https://bugzilla.redhat.com/show_bug.cgi?id=2110801 — NEW Logout from KDE session on Rawhide goes to console, not SDDM After logging out of KDE Plasma, you end up at a console on tty2. SDDM had been running on tty1 but just shows a flashing cursor. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [Fedocal] Reminder meeting : Prioritized bugs and issues
A rather important scheduling conflict has arisen, so there will be no prioritized bugs meeting this week. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [Fedocal] Reminder meeting : Prioritized bugs and issues
On Tue, Aug 9, 2022 at 6:00 AM wrote: > > You are kindly invited to the meeting: >Prioritized bugs and issues on 2022-08-10 from 10:00:00 to 11:00:00 > America/Indiana/Indianapolis >At fedora-meetin...@irc.libera.chat > > More information available at: > https://docs.fedoraproject.org/en-US/program_management/prioritized_bugs/ We will evaluate the following nominated bug (which is ON_QA, so it should be quick): * update 2.06-45 breaks windows boot manager - https://bugzilla.redhat.com/show_bug.cgi?id=2115202 And discuss the resolution of the following accepted bug: * Get rid of multiple source path definitions - https://bugzilla.redhat.com/show_bug.cgi?id=2079833 -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [Fedocal] Reminder meeting : Prioritized bugs and issues
On Tue, Jun 14, 2022 at 6:00 AM wrote: > > You are kindly invited to the meeting: >Prioritized bugs and issues on 2022-06-15 from 10:00:00 to 11:00:00 > America/Indiana/Indianapolis >At fedora-meetin...@irc.libera.chat > > More information available at: > https://docs.fedoraproject.org/en-US/program_management/prioritized_bugs/ We will review the following nominated bugs: * Connecting/disconnecting an external monitor or VM resizing switches GNOME to the login screen - https://bugzilla.redhat.com/show_bug.cgi?id=2071394 * Get rid of multiple source path definitions - https://bugzilla.redhat.com/show_bug.cgi?id=2079833 -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Interested in an updated "Exploring Our Bugs" talk at Nest?
At Nest With Fedora last year, I presented a talk called "Exploring Our Bugs"[1]. In this talk, I took a look at some summary data about Fedora Linux bugs since F19. I'm considering proposing this for Nest 2022. The new talk would mostly be an update with bugs up through F34, but if there were particular topics to dig into, I'm open to suggestions. If there's something that last year's talk left unanswered that you want me to dig into, please let me know off-list. [1] https://www.youtube.com/watch?v=k9NWVYTXj_I -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: F36 release retrospective
On Mon, May 16, 2022 at 1:03 PM Ben Cotton wrote: > > If you missed the announcement at the release party, the F36 release > retrospective survey is now open: > https://fedoraproject.limequery.com/231354 Whoops! That's the F35 link. The correct survey link is https://fedoraproject.limequery.com/36 -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
F36 release retrospective
If you missed the announcement at the release party, the F36 release retrospective survey is now open: https://fedoraproject.limequery.com/231354 It should only take a few moments of your time. No matter how you participated in the development and release of F36, I'd like your input. (Remember, this is about the process of producing F36, not the end result.) If you have any questions, please let me know. If you have suggestions for the next time around, there's a field for that in the survey! The survey is open through 27 May. As I did for F35[1], I'll share results on the Community Blog in June.. [1] https://communityblog.fedoraproject.org/f35-retrospective-results/ -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: F36 Final blocker status summary
On Fri, Apr 29, 2022 at 2:41 PM Ben Cotton wrote: > > We are now targeting target date #2 (2022-05-10). If we slip again, we > won't release until after the Release Party! That should be target date #3, of course. The date is still 2022-05-10. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: F36 Final blocker status summary
We are now targeting target date #2 (2022-05-10). If we slip again, we won't release until after the Release Party! Action summary Accepted blockers - 1. selinux-policy — After upgrade to F36 several packages fail to update due to selinux-related errors — ON_QA ACTION: Cross your fingers that users fully update prior to upgrade 2. gnome-photos — pictures in Pictures folder aren't shown in the Photos — NEW ACTION: Upstream to diagnose and fix issue 3. gnome-photos — A new album looks empty until app restart — NEW ACTION: Upstream to diagnose and fix issue 4. wpa_supplicant — Connection to wireless network fails without explanation when other end does not support secure renegotiation — NEW ACTION: wpa_supplicant maintainers to add a wpa-supplicant specific openssl.cnf file which contains the necessary configuration changes Proposed blockers - 1. gnome-contacts — Contact deletion is unreliable — NEW ACTION: Upstream to diagnose and fix issue Bug-by-bug detail = Accepted blockers - 1. selinux-policy — https://bugzilla.redhat.com/show_bug.cgi?id=2056303 — ON_QA After upgrade to F36 several packages fail to update due to selinux-related errors selinux-policy updates to address this are in F34, F35, and F36. The blocking behavior is fixed, however the concern is that anyone who tries to upgrade from a not-fully-updated F35 may encounter SELinux problems post-upgrade. Although our documentation instructs users to update, graphical updaters do not display this recommendation. The additional week due to the slip will hopefully reduce the number of people affected. 2. gnome-photos — https://bugzilla.redhat.com/show_bug.cgi?id=2079308 — NEW pictures in Pictures folder aren't shown in the Photos Photos added to ~/Pictures don't always show up until the GNOME session is restarted. Filed upstream as https://gitlab.gnome.org/GNOME/gnome-photos/-/issues/196 3. gnome-photos — https://bugzilla.redhat.com/show_bug.cgi?id=2079344 — NEW A new album looks empty until app restart If you add pictures to a new album, the album shows as empty until PHotos is restarted. Filed upstream as https://gitlab.gnome.org/GNOME/gnome-photos/-/issues/197 4. wpa_supplicant — https://bugzilla.redhat.com/show_bug.cgi?id=2072070 — NEW Connection to wireless network fails without explanation when other end does not support secure renegotiation Authentication fails with certain enterprise WiFi networks that do not support resure renegotiation. An OpenSSL config file specifically for wpa_supplicant which sets SSL_OP_LEGACY_SERVER_CONNECT would be a short-term fix as described in https://bugzilla.redhat.com/show_bug.cgi?id=2072070#c24 . Proposed blockers - 1. gnome-contacts — https://bugzilla.redhat.com/show_bug.cgi?id=2079274 — NEW Contact deletion is unreliable Deleting a contact appears to be successful, but takes time on the backend so if a user closes the application shortly after deleting the contact, it's not actually deleted and will appear the next time Contacts is launched. Filed upstream as https://gitlab.gnome.org/GNOME/gnome-contacts/-/issues/241 -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
F36 testing needed: cloud-on-real-cloud
Hello, my cloudy friends, Adam noted in yesterday's Go/No-Go meeting that we're short on test coverage with Cloud images on real clouds. We'll have a new RC coming in a few days to address some outstanding blockers, but in the meantime, if we could start filling in the test matrix[1], I expect most tests should carry over just fine. As a reminder, our next go/no-go meeting is Thursday 5 May. [1] https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Test request: Gnome Text Editor infinite loop (RHBZ 2071228)
Hi folks, I saw RHBZ 2071228 [1] proposed as a freeze exception, but it looks blockery to me. The report specifically mentions the fa_IR locale. It would be very helpful for the purposes of blocker decision to know if the problem is specific to that locale or if others are affected. I've tried to reproduce it using the steps in the bug, but I haven't been able to. That could be entirely a Me Problem™ though. [1] https://bugzilla.redhat.com/show_bug.cgi?id=2071228 -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: F36 Final blocker status summary
Action summary Accepted blockers - 1. selinux-policy — gnome-initial-setup hangs when I try to setup a google/microsoft online account — VERIFIED ACTION: none 2. container-selinux — selinux-policy is preventing flatpak from updating / installing / removing flatpaks — ON_QA ACTION: QA to verify upgrades work reliably with FEDORA-2022-c5bee6b70f 3. selinux-policy — After upgrade to F36 several packages fail to update due to selinux-related errors — ON_QA ACTION: QA to verify blocking behavior is fixed 4. plasma-desktop — pyanaconda.modules.common.errors.installation.StorageInstallationError: device is active — ON_QA ACTION: QA to verify live sessions behave as expected NEEDINFO: fzatl...@redhat.com Proposed blockers - NONE Bug-by-bug detail = Accepted blockers - 1. selinux-policy — https://bugzilla.redhat.com/show_bug.cgi?id=2071259 — VERIFIED 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. FEDORA-2022-76963fee71 contains a verified fix. 2. 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-c5bee6b70f has a potential fix, but it's unclear if it solves the problem in full. 3. selinux-policy — https://bugzilla.redhat.com/show_bug.cgi?id=2056303 — ON_QA After upgrade to F36 several packages fail to update due to selinux-related errors selinux-policy updates to address this are in F34, F35, and F36. It's unclear if there are still blocking behaviors associated with this bug. 4. plasma-desktop — https://bugzilla.redhat.com/show_bug.cgi?id=2073708 — ON_QA pyanaconda.modules.common.errors.installation.StorageInstallationError: device is active KDE Plasma attempted to auto-mount certain hard drives during the live session, preventing anaconda from using the disks in an installation. Adam made an update to fedora-kickstarts that disables this on live sessions. Proposed blockers - NONE -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: [Fedocal] Reminder meeting : Prioritized bugs and issues
On Tue, Apr 19, 2022 at 6:00 AM wrote: > > You are kindly invited to the meeting: >Prioritized bugs and issues on 2022-04-20 from 10:00:00 to 11:00:00 > America/Indiana/Indianapolis >At fedora-meetin...@irc.libera.chat > > More information available at: > https://docs.fedoraproject.org/en-US/program_management/prioritized_bugs/ We will discuss the following nominated (with fix pending) bug: * kexec-tools built with gcc 12 will fail kexec/kdump jumping to 2nd kernel with kexec_load interface - https://bugzilla.redhat.com/show_bug.cgi?id=2057391 And check on the following accepted bug: * Lenovo ThinkPad T490, unable to boot following clean install, stuck at splash screen - https://bugzilla.redhat.com/show_bug.cgi?id=1955416 -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: F36 Final blocker status summary
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_requests/5 -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: F36 Final blocker status summary
https://bugzilla.redhat.com/show_bug.cgi?id=2063156 — NEW Workstation Live is frozen in a VM with QXL video driver (Virtio works OK) VMs that initially use the QXL driver appears frozen. Using virtio (including to switching to QXL after?) avoids this. KDE Lives do not display (heh) this behavior, not does using `nomodeset`. FEDORA-2022-fec53b10e3 has a workaround, which removed this as an accepted blocker. 2. selinux-policy — 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 contains a candidate fix. 3. gnome-connections — https://bugzilla.redhat.com/show_bug.cgi?id=2072445 — VERIFIED GNOME Connections window can't be moved or (un)maximized while a remote desktop is displayed When you connect to a remote desktop (through RDP or VNC), you can no longer move or resize the gnome-connections window. FEDORA-2022-4f7e9dc2fb contains a verified fix. 4. gnome-connections — https://bugzilla.redhat.com/show_bug.cgi?id=2072462 — ASSIGNED Saved entries can't be deleted in GNOME Connections Saved entries are apparently removed, but reappear the next time the application starts. FEDORA-2022-4f7e9dc2fb contains a fix which allows removal of a single entry, but when removing multiple entries, only the last one is successfully removed. 5. gnome-connections — https://bugzilla.redhat.com/show_bug.cgi?id=2072490 — VERIFIED Reconnection in GNOME Connections fails and removes RDP credentials Connection credentials are not preserved between connections. FEDORA-2022-4f7e9dc2fb contains a verified fix. 6. gnome-connections — https://bugzilla.redhat.com/show_bug.cgi?id=2072513 — VERIFIED [abrt] gnome-connections: frdp_session_configure_event(): gnome-connections killed by SIGSEGV Connecting to a server, another server, and then the first server again causes gnome-connections to crash. FEDORA-2022-4f7e9dc2fb contains a verified fix. 7. 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 8. gnome-shell — https://bugzilla.redhat.com/show_bug.cgi?id=2073206 — NEW 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. 9. gnome-software — https://bugzilla.redhat.com/show_bug.cgi?id=2073353 — NEW RPM repos can't be disabled in GNOME Software after F35->F36 upgrade All RPM repos are force enabled and cannot be disabled after upgrade from F35 to F36. New installs of F36 do not exhibit this behavior. 10. kernel — https://bugzilla.redhat.com/show_bug.cgi?id=2053729 — VERIFIED RPi4 wired network fails - eth0 (bcmgenet): transmit queue 1 timed out, due to gcc12 inline assembly miscompilation Networking on the Raspberry Pi 4 fails. FEDORA-2022-af492757d9 contains a verified fix. 11. mutter — https://bugzilla.redhat.com/show_bug.cgi?id=2071226 — NEW anaconda failed to start a live session on a VM with QXL video driver (Virtio works OK) Similar to RHBZ 2061356, Anaconda cannot start a live GNOME session (KDE Plasma works). This is only an issue for the QXL driver. FEDORA-2022-fec53b10e3 provides a workaround for F35, but this bug is still a blocker candidate since it's possible that GNOME Boxes would fall back to QXL. 12. wpa_supplicant — https://bugzilla.redhat.com/show_bug.cgi?id=2072070 — NEW F36 Silverblue won't connect to WPA2 Enterprise network (PEAP + MSChapv2) Connecting to a WPA2 Enterprise wi-fi network fails. Adding the UnsafeLegacyRenegotiation in openssl.cnf allows the network connection to succeed. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Make Flatpak support explicit
On Fri, Apr 8, 2022 at 6:05 AM Kamil Paral wrote: > > Anyone else, thoughts on listing Flatpak explicitly in [0]? My interpretation is that Flatpak is already covered implicitly, in the same way that RPMs are. The careful reader will notice that "rpm" doesn't appear there except in "rpm-ostree", but no one would argue that the criterion doesn't cover managing RPMs. That said, there's some benefit to being explicit. I suppose my take is "sure, I guess." -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: [Fedocal] Reminder meeting : Prioritized bugs and issues
On Tue, Apr 5, 2022 at 6:07 AM wrote: > > You are kindly invited to the meeting: >Prioritized bugs and issues on 2022-04-06 from 10:00:00 to 11:00:00 > America/Indiana/Indianapolis >At fedora-meetin...@irc.libera.chat We will review the following nominated bugs * flathub filtered repo seems missing from F35 install - https://bugzilla.redhat.com/show_bug.cgi?id=2011274 * kexec-tools built with gcc 12 will fail kexec/kdump jumping to 2nd kernel with kexec_load interface - https://bugzilla.redhat.com/show_bug.cgi?id=2057391 * online accounts: can't disable sync on items - https://bugzilla.redhat.com/show_bug.cgi?id=2068470 * kernels newer than 5.15.11-200.fc35 cause libgpiod to issue "Unknown error 517" - https://bugzilla.redhat.com/show_bug.cgi?id=2060490 * GDM login screen does not display all users - https://bugzilla.redhat.com/show_bug.cgi?id=2021839 If we have time, we'll also review the status of the current accepted bugs: * SELinux preventing systemd-network-generator from creating files in /run/systemd/network/ - https://bugzilla.redhat.com/show_bug.cgi?id=2037047 * Lenovo ThinkPad T490, unable to boot following clean install, stuck at splash screen - https://bugzilla.redhat.com/show_bug.cgi?id=1955416 -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: F36 Final blocker status summary
c graphics mode broken for KDE BIOS mode, screen goes black in minutes Related to 2067151, basic graphics mode fails unrecoverably when using KDE Plasma on BIOS. Xorg is materially unchanged from F35 (which works). The vesa driver was updated on F36, but using the new vesa version on F35 still works, so it appears to not be the issue. Proposed blockers - 1. gnome-control-center — https://bugzilla.redhat.com/show_bug.cgi?id=2063410 — NEW Printer setting: can't scroll media size list The scrolling behavior on the media size list is unintuitive, which means users may not be able to select the appropriate media size when trying to print. An upstream merge request exists, but may not be merged until GNOME 43: https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1268 2. gnome-control-center — https://bugzilla.redhat.com/show_bug.cgi?id=2064462 — ON_QA X11: Failed to create foreign window for XID 0: clicking on already set up account in settings > online accounts does not open a new pop up window to show account sync settings The sync settings dialog for existing accounts does now show up when glicking the account in Online Accounts. FEDORA-2022-67fa3533bf contains a candidate fix. 3. hplip — https://bugzilla.redhat.com/show_bug.cgi?id=2066528 — NEW Cannot print except when rebooting computer after upgrade from F35 -> after recommended manual intervention, now cannot print except after turning off printer and then printing a blank page in LibreOffice Print jobs enqueue until the next time the computer boots, at which time they successfully print. This appears to be due to a breakage when the device supports IPP-over-USB and is currently installed with a "classic" print driver. See https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org/thread/BISRSRAUSMMKK34UBAGP44QL7MPZ74GI/ 4. libdnf — https://bugzilla.redhat.com/show_bug.cgi?id=2068773 — NEW systemd-oomd kills rpm-ostree when installing a package on Fedora IoT 36 on the Raspberry Pi Zero 2 W Devices with 512 MB of RAM cannot install updates via `dnf upgrade` or `rpm-ostree`. This is a regression from previous versions (last known-good version currently unknown). 5. qemu — https://bugzilla.redhat.com/show_bug.cgi?id=2070066 — POST VMs hang when trying to access virtiofs mounts in the guest VM Mounting between guest and host using virtiofs causes VMs to hang. A patch for the spec file with a candidate fix is available: https://src.fedoraproject.org/rpms/qemu/pull-request/22 6. selinux-policy — https://bugzilla.redhat.com/show_bug.cgi?id=2070764 — NEW 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. 7. xdg-desktop-portal-gnome — https://bugzilla.redhat.com/show_bug.cgi?id=2068041 — MODIFIED xdg-desktop-portal-gnome: wl_proxy_get_version(): xdg-desktop-portal-gnome killed by SIGSEGV Attempting to download a file in a Chromium-based browser causes the file picker to crash on Xwayland. FEDORA-2022-f8681a48e6 contains a candidate fix, however it may be incomplete. The process crash is gone, but an error message is displayed and the save window expands to full screen. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Spreading test responsibilities to other teams
On Tue, Mar 29, 2022 at 12:05 AM Sudhir Dharanendraiah wrote: > > I agree with the intent. This has been a topic of discussion within the > Fedora QA team for a while now and we have made some efforts to engage SIGs > early in the cycle. Oh, great! I must have missed those conversations. If there's anything I can do to help from a program management perspective, please let me know. > As far as the question of when the testing should be a focus from respective > SIGs? In my humble opinion, it should be continuous and should be a priority > in their respective upstream. SIGs start testing during RC will act as a > helping hand but it won't prevent late findings of issue. I totally agree in theory. In practice, a lot of contributors are volunteers. I'd love to get to the point where the testing is continuous, but getting them to test the RCs more would be an improvement over where we are now. On Wed, Mar 30, 2022 at 10:12 AM Kamil Paral wrote: > > I'm not sure if those mentioned parties read this list and will respond :-) > But yes, in general, it would be nice to see more people from various SIGs to > get involved. I assume everyone has all of the mailing lists beamed directly into their brain. :-D But yeah, I wanted to start the conversation within the QA team to figure out how we can rope them in before we engage with the SIGs. For example, do the RC announcements (e.g. [1]) go to the right places? I see some SIGs receive it, but Cloud doesn't seem to. And there's no clear call-to-action for the SIGs. That could be a low-effort way to potentially improve engagement from SIGs. [1] https://lists.fedoraproject.org/archives/list/test-annou...@lists.fedoraproject.org/thread/3N5LMPVXXVVCLWXMWGLLVUNDX5WRR2OL/ -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Spreading test responsibilities to other teams
Hi friends, I was a little concerned that we were running some tests during the Go/No-Go last week, especially considering it seemed like we had most of the blockers wrapped up well ahead of when we normally do. Part of the answer, in my opinion, is to lean on some of the SIGs/WGs to take a more active role in the testing process for RCs and the period leading up to RCs. In particular, I'd like to see the Server WG taking care of the Active Directory tests (which is a non-trivial thing to remove our dependence on sgallagh's setup, admittedly) and the Cloud SIG taking care of many of those tests. The fact that we didn't have any AWS AMIs uploaded until after the meeting started suggests there's a gap in our process. And of course, pwhalen and coremodule could always use more support in running ARM tests. This isn't a criticism of the QA team, because y'all do a tremendous job. And I don't want to suggest that _all_ of the testing be pushed out onto other teams. But I'd like to start a conversation on how we can spread the responsibility out more. This should hopefully make everyone's life a little easier and make our Go/No-Go meetings more efficient to boot. Thoughts? -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
F36 Final blocker status summary
r if these are the same or separate issues. All combinations work as expected in F35. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: F36 Beta blocker status summary
Action summary Accepted blockers - 1. anaconda — When running anaconda on Wayland with two keyboard layouts configured, hitting any modifier key with the second layout selected switches to the first layout — ON_QA ACTION: QA to verify FEDORA-2022-840ea87072 Proposed blockers - 1. gnome-software — Fedora 34 cannot be upgraded to Fedora 36 with Gnome Software — VERIFIED ACTION: none Bug-by-bug detail = Accepted blockers - 1. anaconda — https://bugzilla.redhat.com/show_bug.cgi?id=2016613 — ON_QA When running anaconda on Wayland with two keyboard layouts configured, hitting any modifier key with the second layout selected switches to the first layout adamwill's research shows that this bug has existed since F25, but became more visible after KDE switched to Wayland by default. This bug was deferred to F36 Beta under the "too hard to fix" exception. Update FEDORA-2022-840ea87072 contains a candidate fix. Proposed blockers - 1. gnome-software — https://bugzilla.redhat.com/show_bug.cgi?id=2064623 — VERIFIED Fedora 34 cannot be upgraded to Fedora 36 with Gnome Software Under some conditions, setting show-upgrade-prerelease does not result in Software showing an available update. Reproducing has been spotty, and there's an emerging consensus that if this is a bug, it's better suited as a Final blocker. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Proposal: Explicitly allow Council to waive Edition self-identification
On Mon, Mar 14, 2022 at 5:33 PM Matthew Miller wrote: > > FESCo has a "make this a blocker" button... I kind of feel an itch for a > generalized "sometimes stuff comes up" lever that goes the _other_ > direction, rather than a very specific carve-out. Like Adam, I fear we'd be too tempted to use it as a "YOLO, ship it!" button. It wouldn't happen right away, but slowly, we'd become more comfortable with waiving more things. I think there are more likely to be cases where we'd want to block on things (e.g. "wow, this bug will be really embarrassing when reviewers find it, but it doesn't actually violate any criteria") arbitrarily than cases where we'd wave. In the "this should be a blocker, actually" case, we can lean on FESCo to use their blocker power to apply it, so I don't think Council needs an explicit authority there. We already have exceptions to allow some blockers to be waived, and I think most of the ones we'd want to waive could be handled under those. Also, as a group we're pretty good at word lawyering when we set our minds to it, so we can find ways to say "this bug does not violate a very specific interpretation of the criteria" if it comes down to it. :-) > We wouldn't be here if I (well, the Council, but I'll go ahead and say > specifically _me_) had made sure we'd done the proper followup around Cloud > "de-editioning" several years ago, and I don't think there's likely to be a > case where this new policy is actually ever used again — if there is, that'd > signal another failure. At the risk of being too pedantic, I want to point out that this is not a new policy. The only reason we're having this discussion is because I was going to just make it happen but I asked Adam about his preferences on the mechanics of it. I argued (correctly, of course) that the Council always had this authority implicitly because it decides what is and is not an Edition. And I think that's why we saw no pushback on the list, in the QA meeting, or in the Blocker Review meeting. Everyone understands that this makes sense. But for the purposes of release criteria, it's better to be explicit than implicit. We're not adding a new feature here. We're fixing a bug so that we get the expected behavior in an exceptional case. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: F36 Beta blocker status summary
Action summary Accepted blockers - 1. anaconda — When running anaconda on Wayland with two keyboard layouts configured, hitting any modifier key with the second layout selected switches to the first layout — POST ACTION: Maintainers to package upstream PR #3912 2. fedora-release — fedora-release-identity-cloud says "Cloud Edition", Cloud has not been an edition for years — ASSIGNED ACTION: none 3. mutter — GNOME doesn't accept input from wireless keyboard if there's not another "keyboard" input available — ON_QA ACTION: QA to verify FEDORA-2022-21d81706cd 4. firefox — f36 composes still have firefox 96, f34 f35 have firefox 97 — ON_QA ACTION: QA to verify FEDORA-2022-42ea499a7d Proposed blockers - 1. mutter — Workstation Live is frozen in a VM with QXL video driver (Virtio works OK) — NEW ACTION: Maintainers to diagnose and fix issue 2. selinux-policy — SELinux preventing systemd-network-generator from creating files in /run/systemd/network/ — ASSIGNED ACTION: Maintainers to update policy to fix issue Bug-by-bug detail = Accepted blockers - 1. anaconda — https://bugzilla.redhat.com/show_bug.cgi?id=2016613 — POST When running anaconda on Wayland with two keyboard layouts configured, hitting any modifier key with the second layout selected switches to the first layout adamwill's research shows that this bug has existed since F25, but became more viisble after KDE switched to Wayland by default. This bug was deferred to F36 Beta under the "too hard to fix" exception. jkonecny is working on a fix to disconnect keyboard control between Anaconda and the live environment. Upstream PR https://github.com/rhinstaller/anaconda/pull/3912 has a candidate fix. 2. fedora-release — https://bugzilla.redhat.com/show_bug.cgi?id=2018271 — ASSIGNED fedora-release-identity-cloud says "Cloud Edition", Cloud has not been an edition for years Waived from F35 final under the "late blocker exception." Cloud WG is working on a proposal to re-promote Cloud to Edition status, but that will not happen for F36 release cycle. Council voted to waive this. An update to the release criterion is pending that explicitly grants Council the ability to do that. 3. mutter — https://bugzilla.redhat.com/show_bug.cgi?id=2017043 — ON_QA GNOME doesn't accept input from wireless keyboard if there's not another "keyboard" input available On some hardware, devices with multiple capabilities that include keyboard do not get registered as a keyboard. Thus they only work if another keyboard is connected. FEDORA-2022-21d81706cd (GNOME 42 megaupdate) includes a candidate fix. 4. firefox — https://bugzilla.redhat.com/show_bug.cgi?id=2057193 — ON_QA f36 composes still have firefox 96, f34 f35 have firefox 97 Builds of Firefox 97, which contains security fixes, are failing on F36 and Rawhide due to a GCC 12 internal error. FEDORA-2022-42ea499a7d provides a successful build of Firefox 97. Proposed blockers - 1. mutter — https://bugzilla.redhat.com/show_bug.cgi?id=2063156 — NEW Workstation Live is frozen in a VM with QXL video driver (Virtio works OK) Recent composes of Workstation with the default video driver freeze on the welcome screen. Using virtio initially (including switching to qxl post-install) does not have this behavior. 2. selinux-policy — https://bugzilla.redhat.com/show_bug.cgi?id=2037047 — ASSIGNED SELinux preventing systemd-network-generator from creating files in /run/systemd/network/. Passing network kernel arguments (e.g. to set the nameserver) at boot causes a failure in systemd-network-generator due to an SELinux denial. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Proposal: Explicitly allow Council to waive Edition self-identification
## Proposal Modify the "Edition self-identification" criterion to explicitly give the Fedora Council the ability to waive the blocker status of bugs that violate this criterion. Specifically, append the following to https://fedoraproject.org/wiki/Fedora_36_Final_Release_Criteria#Self-identification > The Fedora Council, as the body that defines Editions, may vote to waive this > criterion at its discretion through its regular decision-making process. I included "as the body that defines Edition" to make it clear that the Council's ability to waive this criterion follows from its ownership of what an Edition is and not as a broad "the Council can waive arbitrary criteria" statement. The reason I said "regular decision-making process" is to indicate that waiving a blocker under this criterion requires a normal ticket vote[1], not a policy change[2]. ## Context During F35, Adam discovered that our Cloud deliverables were calling themselves an Edition when they are not. This violates the "Edition self-identifications" Final release criterion. We waived this for F35 under the "late blocker exception". The Cloud SIG is working to re-Editionify Cloud, but that won't happen for F36. The Council agreed to waive this[3], but we don't have an explicit mechanism to allow this. Hence, the proposal above. [1] https://docs.fedoraproject.org/en-US/council/#_making_decisions [2] https://docs.fedoraproject.org/en-US/council/policy/policy-change-policy/ [3] https://pagure.io/Fedora-Council/tickets/issue/389#comment-785482 -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: F36 Beta blocker status summary
x27;t require creating an admin user" (RHBZ 2015490) assumes a kickstart file will be available, which is not the case. This results in ARM images not booting to initial-setup. This has been reverted in FEDORA-2022-c263b25459 Proposed blockers - 1. NetworkManager-openvpn — https://bugzilla.redhat.com/show_bug.cgi?id=2057719 — NEW After upgrade gnome-control-center to 42~beta-1.fc37 unable to configure VPN connection VPN connections can't be configured with recent gnome-control-center builds. This appears to be because the NetworkManager-* plugins are still using GTK3, which can't work with a GTK4 gnome-control-center. Work is in progress to update the plugins. 2. dnfdragora — https://bugzilla.redhat.com/show_bug.cgi?id=2060414 — NEW On Fedora 36 KDE, dnfdragora does not start. dnfdragora fails with a libyui error. There seems to be a bootstrap issue because libyui-bindings is part of libyui now. The question of whether two graphical package managers can be blocking is under discussion. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: rfc: new beta release criterion for minimum firefox version
I'm inclined to favor Adam's interpretation and say the existing criteria covers this. But let me put it this way: are there cases where we'd care about a browser version trailing that *aren't* covered by existing criteria? -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Release criteria proposal: networking requirements
On Mon, Feb 28, 2022 at 12:37 PM Adam Williamson wrote: > > So, uh, we sorta forgot about this. Kamil approved this draft, but > nobody else gave any feedback on it. This topic is still relevant and > we have a proposed VPN blocker today, so...any more feedback on this > draft? I think it's sound enough to start using. I'm sure we'll find all sorts of edge cases to argue over and eventually fix. That's the Fedora Way™. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: F36 Beta blocker status summary
ugzilla.redhat.com/show_bug.cgi?id=2057193 — NEW f36 composes still have firefox 96, f34 f35 have firefox 97 Builds of Firefox 97, which contains security fixes, are failing on F36 and Rawhide due to a GCC 12 internal error. FEDORA-2022-e056239611 contains a fix for those issues, but is apparently incomplete. 2. gnome-control-center — https://bugzilla.redhat.com/show_bug.cgi?id=2057719 — NEW After upgrade gnome-control-center to 42~beta-1.fc37 unable to configure VPN connection VPN connections can't be configured with recent gnome-control-center builds. This bug is reported against Rawhide and there's no confirmation at this moment that the behavior exists on F36. 3. initial-setup — https://bugzilla.redhat.com/show_bug.cgi?id=2057600 — NEW Initial Setup startup failed due to invalid kickstart file A previous fix for the "initial-setup doesn't require creating an admin user" (RHBZ 2015490) assumes a kickstart file will be available, which is not the case. This results in ARM images not booting to initial-setup. An upstream PR reverts the partial fix while a better long-term solution is found: https://github.com/clalancette/oz/pull/297 -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: F36 Beta blocker status summary
sion breaks the login screen. A crash message is displayed instead of the login screen. This is fixed in gjs 1.71.1. 3. pipewire — https://bugzilla.redhat.com/show_bug.cgi?id=2054921 — NEW dnf system-upgrade 35 to 36 fails with various pipewire wireplumber conflicts Package conflicts exist between pipewire-media-session and pipewire-session-manager. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
F36 Beta blocker status summary
Now that we've reached the branch point, it's time to start doing weekly blocker summaries again! Beta freeze begins on 22 February and the current target Beta release date is 15 March. Action summary Accepted blockers - 1. anaconda — When running anaconda on Wayland with two keyboard layouts configured, hitting any modifier key with the second layout selected switches to the first layout — ASSIGNED ACTION: Maintainers to diagnose issue 2. distribution — Fedora 36 backgrounds not present on release-blocking desktops (GNOME, KDE) — NEW ACTION: Maintainers to update background packages 3. fedora-release — fedora-release-identity-cloud says "Cloud Edition", Cloud has not been an edition for years — NEW ACTION: Maintainers to update fedora-release-identity-cloud or group-with-such-authority to waive this. 4. kwin — openQA clicks in anaconda on KDE stop working shortly after it starts — NEW ACTION: Maintainers to diagnose issue 5. libinput — GNOME doesn't accept input from wireless keyboard if there's not another "keyboard" input available — NEW ACTION: Maintainers to diagnose issue 6. linux-firmware — Fedora 36: Server boot x86_64 image exceeds maximum size — ASSIGNED ACTION: None Proposed blockers - 1. distribution — Some variants are missing /etc/resolv.conf symlink (use systemd-resolved) — POST ACTION: QA to verify issue is resolved 2. dnf — exclude_from_weak_autodetect=true effectively renders rich weak dependencies useless — NEW ACTION: dnf maintainers to decide on approach for "instally only newly recommended packages" proposal Bug-by-bug detail = Accepted blockers - 1. anaconda — https://bugzilla.redhat.com/show_bug.cgi?id=2016613 — ASSIGNED When running anaconda on Wayland with two keyboard layouts configured, hitting any modifier key with the second layout selected switches to the first layout adamwill's research shows that this bug has existed since F25, but became more viisble after KDE switched to Wayland by default. This bug was deferred to F36 Beta under the "too hard to fix" exception. There's ongoing discussion trying to come up with a potential fix, however we still seem to be a long way from that point. 2. distribution — https://bugzilla.redhat.com/show_bug.cgi?id=2052654 — NEW Fedora 36 backgrounds not present on release-blocking desktops (GNOME, KDE) The usual desktop background blocker. 3. fedora-release — https://bugzilla.redhat.com/show_bug.cgi?id=2018271 — NEW fedora-release-identity-cloud says "Cloud Edition", Cloud has not been an edition for years Waived from F35 final under the "late blocker exception." Cloud WG is working on a proposal to re-promote Cloud to Edition status, but that will not happen for F36 release cycle. 4. kwin — https://bugzilla.redhat.com/show_bug.cgi?id=2047503 — NEW openQA clicks in anaconda on KDE stop working shortly after it starts Shortly after the installer starts, mouse clicks in openQA stop working. Using 'development mode' which allows for manual interaction still works. This bug only affects KDE, and appears to have been introduced in the KDE Plasma 5.24 pre-release on 2022-01-19. This bug is accepted under the "hinders execution of required Beta test plans" criterion. 5. libinput — https://bugzilla.redhat.com/show_bug.cgi?id=2017043 — NEW GNOME doesn't accept input from wireless keyboard if there's not another "keyboard" input available On some hardware, devices with multiple capabilities that include keyboard do not get registered as a keyboard. Thus they only work if another keyboard is connected. It seems to mostly (or exclusively) affect some ARM hardware. 6. linux-firmware — https://bugzilla.redhat.com/show_bug.cgi?id=2031214 — ASSIGNED Fedora 36: Server boot x86_64 image exceeds maximum size Fedora-Server-netinst-x86_64-36-20220210.n.0.iso is 731906048 bytes, which is below the maximum size of 734003200. This bug can probably be closed until the image exceeds the limit again. Proposed blockers - 1. distribution — https://bugzilla.redhat.com/show_bug.cgi?id=2032085 — POST Some variants are missing /etc/resolv.conf symlink (use systemd-resolved) Some variants are not using systemd-resolved as intended. With some recently-merged changes to Anaconda, this appears to be working correctly now. 2. dnf — https://bugzilla.redhat.com/show_bug.cgi?id=2033130 — NEW exclude_from_weak_autodetect=true effectively renders rich weak dependencies useless Behavior introduced by the "Enable exclude_from_weak_autodetect by default in LIBDNF" System-Wide Change appear to have undesired effects in some use cases, particularly with language packs. It appears that a robust fix is technically difficult, and the Change owners are discussing reverting this Change for F36 (see BZ 2013327). -- Ben Cotton He
Re: [Fedocal] Reminder meeting : Prioritized bugs and issues
On Tue, Feb 8, 2022 at 5:00 AM wrote: > > You are kindly invited to the meeting: >Prioritized bugs and issues on 2022-02-09 from 10:00:00 to 11:00:00 > America/Indiana/Indianapolis >At fedora-meetin...@irc.libera.chat > > More information available at: > https://docs.fedoraproject.org/en-US/program_management/prioritized_bugs/ We will evaluate the following nominated bugs: * SELinux preventing systemd-network-generator from creating files in /run/systemd/network/ - https://bugzilla.redhat.com/show_bug.cgi?id=2037047 We will check in on the following accepted bugs: * Lenovo ThinkPad T490, unable to boot following clean install, stuck at splash screen - https://bugzilla.redhat.com/show_bug.cgi?id=1955416 * Flatpak using excessive space in /var/lib/flatpak/appstream - https://bugzilla.redhat.com/show_bug.cgi?id=2032528 (Note that we're now meeting one hour earlier than we used to) -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Picking a new time for the Prioritized Bugs meeting
Beginning next week, the Fedora Prioritized Bugs meetings will be held on alternate Wednesdays at 10:00 AM US/Eastern (currently 1500 UTC)[1] in #fedora-meeting-1. This is one hour earlier than the previous time. For more information on the Prioritized Bugs process, see the docs[2]. [1] https://calendar.fedoraproject.org/meeting/10144/ [2] https://docs.fedoraproject.org/en-US/program_management/prioritized_bugs/ -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Picking a new time for the Prioritized Bugs meeting
I have a personal conflict with the current meeting time for the Prioritized Bugs meeting, so I'm looking to reschedule. If you'd like to attend semi-regularly, please feel free to add your availability: https://whenisgood.net/c8iqggm/ I make no promises about when the meeting will be scheduled, but if there are times that are obviously favoriable, then I'll use that. If you're not sure what meeting I'm talking about, the Prioritized Bugs process is documented at: https://docs.fedoraproject.org/en-US/program_management/prioritized_bugs/ -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Proposal: revise "Default application functionality" final criterion to be clearer
On Thu, Jan 20, 2022 at 7:10 PM Adam Williamson wrote: > > Thoughts? Is this an improvement? Anyone have a better idea? Thanks! This is a definite improvement. I agree with Kamil's comment about including the "graphically" wording. It might be unnecessarily pedantic, but our future selves may appreciate the clarity of intent. Perhaps: > Additionally, for Fedora Workstation on the x86_64 architecture, '''all''' > applications that are installed by default and can be launched using the > standard graphical mechanism must meet this requirement. We might make a similar edit to the "all combos" wording, too: > For all release-blocking desktop / arch combinations, the following graphical > applications must start successfully and withstand a basic functionality test: This shows that we mean, for example, nautilus and not tar. Stylistically, I like the idea of making the list of application types and the examples given below into a table. That seems easier to understand, although I see arguments for leaving it as-is. I suggest this change, but will not lobby for it beyond this suggestion. :-) -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: new criterion proposal: Graphical package managers (take #2)
Great work, Kamil. I think this addresses most of the concerns. And while I still don't love the idea of including concurrent actions, the argument is good enough that I'll live with it. I have some pedantic arguments about one of the things that must hold true, but that's something to discuss socially. I'm +1 to the modified proposal. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: [Fedocal] Reminder meeting : Prioritized bugs and issues
On Tue, Jan 11, 2022 at 6:00 AM wrote: > > You are kindly invited to the meeting: >Prioritized bugs and issues on 2022-01-12 from 11:00:00 to 12:00:00 > America/Indiana/Indianapolis >At fedora-meetin...@libera.chat > > More information available at: > https://docs.fedoraproject.org/en-US/program_management/prioritized_bugs/ We will review the following nominated bugs: * Lenovo ThinkPad T490, unable to boot following clean install, stuck at splash screen https://bugzilla.redhat.com/show_bug.cgi?id=1955416 * Lenovo Ideapad 5 14alc05 Touchpad Randomly stops working https://bugzilla.redhat.com/show_bug.cgi?id=2019926 * Flatpak using excessive space in /var/lib/flatpak/appstream https://bugzilla.redhat.com/show_bug.cgi?id=2032528 * USB Controller doesn't reconize the connected device(s) https://bugzilla.redhat.com/show_bug.cgi?id=2032895 * "fedpkg lint" dies with rpmlint-2.0.0: rpmlint: error: unrecognized arguments: -f https://bugzilla.redhat.com/show_bug.cgi?id=1967821 -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: is an accidentally reverted Fedora feature/change a blocker?
I generally agree with Adam's points. We don't want to add tests for every accepted Change proposal. In particular, the "updating X to version Y". That said, I think we should be checking for certain paradigm-shift or otherwise notable changes. Changes to the default filesystem, moving to Wayland by default, etc. are obvious candidates. Some key "how" or performance changes, too (e.g. WirePlumber, systemd-resolved). Looking at the last four releases, there are 2-3 per release that I would put on that list. One thing we could do is to require a check with QA in Change proposals (the way we require a check with Rel Eng). This would be a good, early opportunity to adjust criteria or test cases, when needed. I do think we should be careful about relying *solely* on our release criteria. They're an important part of the process and give us a lot of objectivity and predictability. But we're not producing a release to meet the criteria, we're producing a release to give our users an experience. (I don't love that phrasing, but I hope the intent is clear enough.) So if we're shipping something that passes the criteria and test cases, but doesn't give the intended experience, then our criteria/tests are wrong. We'll never be able to test everything exactly, but if there's a way we can close the gap in a sustainable way, we should do that. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: [Fedocal] Reminder meeting : Prioritized bugs and issues
On Tue, Dec 14, 2021 at 6:00 AM wrote: > > You are kindly invited to the meeting: >Prioritized bugs and issues on 2021-12-15 from 11:00:00 to 12:00:00 > America/Indiana/Indianapolis >At fedora-meetin...@libera.chat > > More information available at: > https://docs.fedoraproject.org/en-US/program_management/prioritized_bugs/ There are no nominated or accepted bugs, so tomorrow's meeting is canceled. The 29 December meeting is also canceled. If you have any bugs to nominate, we'll review them on Wednesday 12 January 2022. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Bug 1949417 - Fedora 34 does not boot after upgrade (edit)
On Wed, Dec 8, 2021 at 8:28 AM wrote: Hi Joe, > I just tested this and it now works correctly. Can I > makr it as closed? Since you're the person who originally reported it, please feel free to close it. (CLOSED->CURRENTRELEASE). If you have any trouble with that, please let me know directly and I can help. If you know what specific update fixed it, please note that in the comments for historical reference. Thanks, BC -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: F35 release retrospective
This is your reminder that the F35 release retrospective is open through 4 December. On Mon, Nov 15, 2021 at 3:56 PM Ben Cotton wrote: > > Hi everyone, > > Now that we've released F35, I'd like to share the first semi-annual > release retrospective survey: > https://fedoraproject.limequery.com/231354 > > I kept it intentionally short and open-ended. It should only take a > few moments of your time. If you have any questions, please let me > know. If you have suggestions for the next time around, there's a > field for that in the survey! > > The survey is open through 4 December. I'll share results on the > Community Blog in late December or early January. > -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: F35 retrospective follow-up: proposed actions
On Fri, Nov 26, 2021 at 7:06 PM Adam Williamson wrote: > > 3. "Ahmedalmeleh - Bugzilla is challenging to me and still getting used > to it. I wish I was able to learn how to operate OpenQA's automated > tests, in the given timeframe and was given guidance sooner.", also > Ahmed's 'wishlist' item and Matt's item - I'll plan to file a ticket > for improved guidance on using Bugzilla, I'm happy to work with you on that. Or just let you assign it to Program Management. I've been thinking about putting together some "helpful Bugzilla tips" docs and potentially making videos for them. Mainly, what I'd need to get started is some things that people want to know. I've been around Bugzilla long enough to have lost track of what "everyone knows". -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Heads up: moving some content from wiki to docs
Hi everyone, Just wanted to let you know I'm going to start moving some release-related content out of the wiki and into docs. It's largely things that are static and copy/pasted forward like release-blocking images, spins/labs, etc. I will setup automatic redirects as I move pages, but if you're linking to specific anchors, that will likely break. I'll continue to create wiki pages for the next release or two, but if you have anything generating links to the wiki pages for spins/labs or blocking images, you'll want to start updating those. You can see the basic structure starting to take place at: https://docs.fedoraproject.org/en-US/releases/ Note that ChangeSet pages and schedules are not moving, at least for now. Thanks, BC -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
F35 release retrospective
Hi everyone, Now that we've released F35, I'd like to share the first semi-annual release retrospective survey: https://fedoraproject.limequery.com/231354 I kept it intentionally short and open-ended. It should only take a few moments of your time. If you have any questions, please let me know. If you have suggestions for the next time around, there's a field for that in the survey! The survey is open through 4 December. I'll share results on the Community Blog in late December or early January. If you haven't seen, Adam is running a QA-specific retrospective as well. If you only have QA feedback, you can record it on the wiki page and I'll incorporate the responses into my final analysis. https://fedoraproject.org/wiki/Fedora_35_QA_Retrospective -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Meeting on 2021-11-15: options
On Fri, Nov 12, 2021 at 7:02 PM Adam Williamson wrote: > > So, we can either wait one more week, or someone else can volunteer to > run the meeting on Monday in my stead. Does anyone want to do that, or > should we wait till 2021-11-22? Thanks! It's not that we can't meet without you, but I don't see anything on the list that couldn't wait another week. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: new criterion proposal: Graphical package managers
On Mon, Nov 8, 2021 at 8:37 AM Kamil Paral wrote: > > I find it hard to draw the line somewhere between all these cases. So > aborting a previous operation is not ok, but not even starting a second > operation is ok? Installing and removing the same package is not blocking? > What about installing two different packages, would that block? What about > installing A and removing B? I don't honestly think it's a good idea to dig > into the million of sub-cases here. > Just imagine we're not talking about the package manager but a file manager > instead. If you could either create a file, or remove a file, but you > couldn't create&remove the file, or you couldn't remove 2 different either > sequentially or together, that would clearly be a blocker (I hope). It would > be quite obvious that this is a basic functionality. So why isn't this a > basic functionality for the package manager? And why do we have (it seems) a > different quality bar for dnf vs graphical package managers? I don't think > these bugs would be waived for dnf. > I agree with František's comment that the DNF case is different enough in how it functions that it's not a fair comparison. I do think that aborting a previous operation is not okay, but refusing to start a second operation until the first is done is. Ideally with a clear message explaining why, but not necessarily. So I still disagree with you, but my position is softening. I'd rather we have a clearly-defined and understood set of criteria that I disagree with in some places than to try to make every criterion match my preferences. :-) So while I disagree, I'm happy to move forward with this. > So let's reduce the original requirement into something like this: > * configure software sources by enabling/disabling pre-defined official > repositories and then adjust the available software pool accordingly > > Does it sound better? Yes, that works for me. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: new criterion proposal: Graphical package managers
On Thu, Nov 4, 2021 at 6:12 AM Kamil Paral wrote: > > "Multiple operations" is one of the reasons for proposing this criterion. In > this release, and previous releases, we often had a bug that you can install > a package, but then you can't remove it. But if you restarted the package > manager, or your session, then it worked. And people said "well, both install > and remove work, you just can't use them together, so... it's fine according > to the criteria!". That's why I list it explicitly as blocking Final. I don't > think it's fine. > I guess my question comes down to is this something The Average User™ does, or is it just something that Kamil does because he's really good at QA? If it's the former, then I'm in favor of your proposal. > Another scenario could be when you hit Install on app A, and before it is > done, you hit install on app B. Imagine if the first operation would get > stopped abruptly. The same argument could be used as above (which is a real > argument, not a made-up one). Again, that's why I mention it explicitly. > I see that as being a different case from the above, and I would definitely support blocking on that behavior. The only thing that should abruptly stop a transaction is the user hitting a cancel button. So while I'm still unclear about the first part, I'm totally on board with this part. >> We should clarify this to something like "list software installed from >> managed repositories". The wording probably needs help, but the idea > What about: > * list locally-installed software coming from the official Fedora repositories > ? Well, I think we'd want it to work for other repositories too (like Flathub, rpmfusion, etc). But there's a case for keeping the criterion limited to just the official repos because if something fails because a third-party repo does something weird, that's out of our control. So I guess this wording works if only to prevent ourselves getting hung up on a totally-out-of-our-control bug at some point in the future. >> > * start the selected installed software >> > I use it from time to time, it's faster than retyping the app name into the > gnome overview (and it also takes a few seconds to show up there, so you must > not be too fast or you need to start over). It's also convenient when trying > out 5 different drawing applications or similar. But the fact that it's > prominently shown made me include this. I think it would be a really poor > experience if you install some app, hit Open/Launch, and nothing happens. (At > the same time, this one use case is not as important as the others, so if > most people dislike it, I'm not going to fight for it - I'd just give you a > sad panda face). > You've convinced me. +1 to this >> Do we want to make it clear that it's not intended to allow the user >> to *add* a new repository? Or is that understood? > > GNOME Software doesn't allow the user to add any additional repository. KDE > Discover allows the user to add an arbitrary Flatpak repository, or Flathub > directly with a specialized button. My idea was to not distinguish between > different buttons, simply if it is present and serves for repo configuration, > it must work. However, if you think it's better, we can exclude the Add > button explicitly, or we can name which exact buttons/operations must work. > I'm on board with the enable/disable part for sure. I'm not sure how I feel about the adding new repos part. I think I'm weakly opposed to including it. One, it adds to the number of things we need to test. Two, and more importantly, most third-party repos that I've come across provide an RPM or similar to add a new repo. And if for some reason it doesn't work via the GUI tool, I think saying "sorry, do it on the command line then" is reasonable for this particular use case. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: new criterion proposal: Graphical package managers
On Wed, Nov 3, 2021 at 7:32 AM Kamil Paral wrote: > > * install, remove and update software, even if multiple operations are > scheduled sequentially or concurrently I don't like the "multiple operations" part but to be honest I'm not sure if that's because I worry about how many delays it will cause or if I legitimately don't think that's a sufficiently common use case. > * list software installed on the system We should clarify this to something like "list software installed from managed repositories". The wording probably needs help, but the idea is that we want it to know what RPMs and flatpaks are installed. But if someone installs a package from source or a tarball, we don't expect the package manager to know about it. I know that's not what you're saying, but it's worth being clear here so that future readers are clear on the intent. > * start the selected installed software Is this a common case? I almost never use a graphical package manager myself, so I don't know. > * configure software sources (enable/disable/add/remove repositories, set > default sources) and then adjust the available software pool accordingly Do we want to make it clear that it's not intended to allow the user to *add* a new repository? Or is that understood? -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: [Fedocal] Reminder meeting : Prioritized bugs and issues
> On Tue, Nov 2, 2021 at 7:00 AM wrote: > > You are kindly invited to the meeting: >Prioritized bugs and issues on 2021-11-03 from 11:00:00 to 12:00:00 > America/Indiana/Indianapolis >At fedora-meetin...@libera.chat > > More information available at: > https://docs.fedoraproject.org/en-US/program_management/prioritized_bugs/ > We will discuss the following nominated bug (for real this time. I swear I won't forget to run the meeting this time): * gnome-shell: gnome-shell killed by SIGSEGV — https://bugzilla.redhat.com/show_bug.cgi?id=1960938 There are no currently accepted prioritized bugs. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Keyboard layout criterion update proposal
On Thu, Oct 28, 2021 at 3:06 PM Adam Williamson wrote: > > https://fedoraproject.org/wiki/Fedora_35_Final_Release_Criteria#Keyboard_layout_configuration > > I propose we add: > > * In the installer (if applicable) > > to the list of environments in which the configuration must work. > Technically this is a bit odd because it's in the "Post-install > requirements" section, but it seems a bit excessive to add a duplicate > criterion in the "Installer requirements" section just to be hyper- > correct, I think we can live with it. Alternatively we could move the > whole thing out to a new section, I guess. > +1 to your proposal, including the "it's sort of in the wrong section, but we'll live" part. It's worth fixing the oversight with minimal overhead. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Fedora Linux 35 Final blocker review summary
Tomorrow's email today, since Friday is a "recharge day" at Red Hat.
We're now officially in "late" territory. The new target is target
date #2 (2 November), which means we'd want a new release candidate
compose by Tuesday evening.
Action summary
Accepted blockers
-
1. fedora-third-party — The switch for Fedora Third Party repositories
does not switch them on. — VERIFIED
ACTION: None
2. plasma-discover — Discover doesn't seem to find any RPM packages,
neither locally installed nor in RPM repos (but just under en_US
locale) — MODIFIED
ACTION: QA to verify update FEDORA-2021-1949dabf93
3. fedora-third-party — GNOME Software does not always show packages
from third party repos if enabled via gnome-initial-setup — NEW
ACTION: Maintainers to fix issue
4. kbd — systemd-vconsole-setup.service fails on an arabic system — NEW
ACTION: Maintainers to fix issue
5. LiveCD - KDE — The KDE LiveCD 35 RC does not boot in basic graphics
mode. — NEW
ACTION: Maintainers to fix issue
6. plasma-discover — Install/Remove buttons are cropped, the text is
off-screen — VERIFIED
ACTION: None
Proposed blockers
-
1. kernel — Fedora 35 aarch64 cloud image based openstack VM hangs — NEW
ACTION: Maintainers to diagnose and fix issue
Bug-by-bug detail
=
Accepted blockers
-
1. fedora-third-party —
https://bugzilla.redhat.com/show_bug.cgi?id=2001837 — VERIFIED
The switch for Fedora Third Party repositories does not switch them on.
Enabling third party repos failed, which was sort of fixed in
gnome-initial-setup-41~rc-3.fc35. Fixed in FEDORA-2021-d3cb1609c8.
2. plasma-discover —
https://bugzilla.redhat.com/show_bug.cgi?id=2011333 — MODIFIED
Toggling repo in Discover doesn't redraw the checkbox, confusing users
(but just under en_US locale)
When clicking on the checkbox, repo enablement is toggled, but that is
not reflected in the UI. This could lead to users putting the repos in
an undesired state. Update FEDORA-2021-1949dabf93 contains a fix that
appears to fix this.
3. fedora-third-party —
https://bugzilla.redhat.com/show_bug.cgi?id=2016510 — NEW
GNOME Software does not always show packages from third party repos if
enabled via gnome-initial-setup
Packages provided by third-party repositories sometimes are not shown
in Software if the repo was added via gnome-initial-setup and
PackageKit has not been refreshed (by timer or by adding additiona
repos after install). This is a spinoff of 2001837.
4. kbd — https://bugzilla.redhat.com/show_bug.cgi?id=2015972 — NEW
systemd-vconsole-setup.service fails on an arabic system
The systemd-vconsole-setup service fails, however no functional defect
has been discovered. This appears to be because the 'ara' console
layout appears in xxb, but not in kdb-{misc,legacy}
5. LiveCD - KDE — https://bugzilla.redhat.com/show_bug.cgi?id=2016310 — NEW
The KDE LiveCD 35 RC does not boot in basic graphics mode.
Booting with basic graphics mode on a BIO system ends up with a black
screen. The system does not responsd to Esc, but does to
`Ctrl+Alt+Del`. In EFI mode, it works as expected.
6. plasma-discover —
https://bugzilla.redhat.com/show_bug.cgi?id=2015491 — VERIFIED
Install/Remove buttons are cropped, the text is off-screen
The button labels were off-screen, leaving users to guess that they're
clicking the right button. Update FEDORA-2021-1949dabf93 contains a
verified fix.
Proposed blockers
-
1. kernel — https://bugzilla.redhat.com/show_bug.cgi?id=2011928 — NEW
Fedora 35 aarch64 cloud image based openstack VM hangs
OpenStack aarch64 VMs hang on boot. With the same kernel, this does
not happen on F34 cloud images but does happen on F34 installs from
the Everything media, so this may implicate the BTRFS change. Work to
diagnose this is ongoing, but reproduction seems elusive. We're
working with Vexxhost to see if they can provide additional
troubleshooting help.
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Re: [Fedocal] Reminder meeting : Prioritized bugs and issues
On Tue, Oct 19, 2021 at 7:00 AM wrote: > > You are kindly invited to the meeting: >Prioritized bugs and issues on 2021-10-20 from 11:00:00 to 12:00:00 > America/Indiana/Indianapolis >At fedora-meetin...@libera.chat > > More information available at: > https://docs.fedoraproject.org/en-US/program_management/prioritized_bugs/ > We will discuss the following nominated bug: * gnome-shell: gnome-shell killed by SIGSEGV — https://bugzilla.redhat.com/show_bug.cgi?id=1960938 There are no currently accepted prioritized bugs. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Fedora Linux 35 Final blocker review summary
Many fewer blockers than last week. Hooray! Go/No-Go for target date
#1 is Thursday.
Action summary
Accepted blockers
-
1. geoclue2 — time is transiently incorrect when Automatic Time Zone
is enabled — MODIFIED
ACTION: QA to verify FEDORA-2021-14f2ed62fd
2. selinux-policy — The switch for Fedora Third Party repositories
does not switch them on. — MODIFIED
ACTION: QA to verify FEDORA-2021-d3cb1609c8
3. plasma-discover — Discover shows a misleading state of Flatpak
repos, can't delete disabled repos — NEW
ACTION: Maintainers to fix issue
4. plasma-discover — Discover doesn't seem to find any RPM packages,
neither locally installed nor in RPM repos — NEW
ACTION: Maintainers to fix issue
5. plasma-discover — Toggling repo in Discover doesn't redraw the
checkbox, confusing users — NEW
ACTION: Maintainers to fix issue
6. uboot-tools — RK3399 - SPL: failed to boot from all boot devices — POST
ACTION: Maintainers to submit an update with problematic patch reverted
Proposed blockers
-
1. kernel — Fedora 35 aarch64 cloud image based openstack VM hangs — NEW
ACTION: Maintainers to diagnose and fix issue
2. clevis-pin-tpm2 — clevis - thread 'main' panicked at 'called
`Option::unwrap() — ASSIGNED
ACTION: Maintainers to fix issue
NEEDINFO: pbrobinson
3. dracut — 5.14.9-200.fc34 kernel will not boot on AWS EC2 t2.small
instance — NEW
ACTION: Maintainers to submit an update that includes upstream fix
4. gnome-initial-setup — Online Accounts setup does not appear when
wifi is configured through Gnome Initial Setup — MODIFIED
ACTION: QA to verify FEDORA-2021-14f2ed62fd
5. kscreenlocker — KScreenLocker segfaults when screen dims — NEW
ACTION: Maintainers to fix issue
6. spin-kickstarts — resolv.conf on Cloud images are not empty,
causing cloud-init automatic network configuration to fail — NEW
ACTION: QA to verify kickstarts commit 32b03e0
Bug-by-bug detail
=
Accepted blockers
-
1. geoclue2 — https://bugzilla.redhat.com/show_bug.cgi?id=1991075 — MODIFIED
time is transiently incorrect when Automatic Time Zone is enabled
The displayed time is incorrect in some cases when Automatic Time Zone
is enabled. Both `timedatectl` and the GNOME display show the wrong
time. Update FEDORA-2021-532f05d2e3 contained a partial fix.
Subsequent investigation discovered a change in NetworkManager 1.32
broke glib's network connectivity detection code, which broke geoclue.
Update FEDORA-2021-14f2ed62fd contains a candidate fix.
2. selinux-policy — https://bugzilla.redhat.com/show_bug.cgi?id=2001837 — POST
The switch for Fedora Third Party repositories does not switch them on.
Enabling third party repos failed, which was sort of fixed in
gnome-initial-setup-41~rc-3.fc35. However, when running SELinux in
enforcing mode, it still fails. Several updates to the policy
configuration have been added. Update FEDORA-2021-d3cb1609c8 for
fedora-third-party removes an unneeded chcon call.
3. plasma-discover — https://bugzilla.redhat.com/show_bug.cgi?id=2011291 — NEW
Discover shows a misleading state of Flatpak repos, can't delete disabled repos
4. plasma-discover — https://bugzilla.redhat.com/show_bug.cgi?id=2011322 — NEW
Discover doesn't seem to find any RPM packages, neither locally
installed nor in RPM repos
Discover shows updates in the "Installed" tab, but when no updates are
available, only flatpaks are listed. This isn't universally
reproducible. Updated installations from Beta media seem to work, but
nightlies do not (as least as of 20211011.n.0.iso).
5. plasma-discover — https://bugzilla.redhat.com/show_bug.cgi?id=2011333 — NEW
Toggling repo in Discover doesn't redraw the checkbox, confusing users
When clicking on the checkbox, repo enablement is toggled, but that is
not reflected in the UI. This could lead to users putting the repos in
an undesired state. This is not fixed in Discover 5.23.
6. uboot-tools — https://bugzilla.redhat.com/show_bug.cgi?id=2014182 — POST
RK3399 - SPL: failed to boot from all boot devices
uboot-tools releases 2021.{07,10} do not boot on rk3399 devices.
pbrobinson identified the responsible patch and is testing reversion
on key devices.
Proposed blockers
-
1. kernel — https://bugzilla.redhat.com/show_bug.cgi?id=2011928 — NEW
Fedora 35 aarch64 cloud image based openstack VM hangs
OpenStack aarch64 VMs hang on boot. With the same kernel, this does
not happen on F34 cloud images, so this may implicate the BTRFS
change.
2. clevis-pin-tpm2 —
https://bugzilla.redhat.com/show_bug.cgi?id=2012758 — ASSIGNED
clevis - thread 'main' panicked at 'called `Option::unwrap()
A crash in clevis presents unlocking TPM2 storage, which is part of
the key IoT security functionality. QA tests are passing on F35 and
failing on Rawhide, however the user report came from F35.
3. dracut — https://bugzilla.redhat.com/show_bug.cgi?id=2010058 — NEW
5.14.9-200.fc34 kernel will not boot on AWS EC2 t2.small instance
xen-blkfr
Re: Fedora Linux 35 Final blocker review summary
, which either introduces or uncovers BZ 2011774. 17. plasma-discover — https://bugzilla.redhat.com/show_bug.cgi?id=2011322 — NEW Discover doesn't seem to find any RPM packages, neither locally installed nor in RPM repos Discover shows updates in the "Installed" tab, but when no updates are available, only flatpaks are listed. Proposed blockers - 1. gnome-shell — https://bugzilla.redhat.com/show_bug.cgi?id=2011872 — NEW gnome-shell OSDs show invalid icons most of the time Each time some OSD popup (e.g. for volume changes) is shown and disappears, its icon is "remembered" and used for all future OSDs. This is fixed upstream https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1983 2. gnome-software — https://bugzilla.redhat.com/show_bug.cgi?id=2010660 — NEW certain apps are shown among system repos Some applications are showing in Software among the system repos instead of with applications. Upstream MR 1023 backports the fix to GNOME 41: https://gitlab.gnome.org/GNOME/gnome-software/-/merge_requests/1023 3. kernel — https://bugzilla.redhat.com/show_bug.cgi?id=2008537 — POST 5.14.x defaults to acpi on aarch64 Kernel 5.14.1-300 introduced an accidental change in bahevior on aarch64 where ACPI was used instead of device-tree. This can't be fixed in subsequent updates because changing to device-tree might change which hardware works and how. The patch is reverted and will appear in 5.14.10+. 4. kernel — https://bugzilla.redhat.com/show_bug.cgi?id=2011928 — NEW Fedora 35 aarch64 cloud image based openstack VM hangs OpenStack aarch64 VMs hang on boot. With the same kernel, this does not happen on F34 cloud images, so this may implicate the BTRFS change. 5. kwin — https://bugzilla.redhat.com/show_bug.cgi?id=2001135 — POST kwin_wayland segmentation faulted in KWin::LibInput::Context::closeRestricted when logging out of Plasma with libinput-1.18.901-1.fc35 When logging out of PLasma 5.22.5 on Wayland, the screen goes black and then Plasma restarts. This is fixed in upstream 5.23. adamwill has a scratch build of backports that appears to fix the issue: https://koji.fedoraproject.org/koji/taskinfo?taskID=76835467 6. LiveCD - KDE — https://bugzilla.redhat.com/show_bug.cgi?id=2011889 — NEW The KDE Live does freezes on Dell Precision Tower 7810 Boot checks pass and the boot messages appeared correct, but when the live session opened on this hardware, it freezes immediately. Workstation ISO boots fine on this hardware. 7. openh264 — https://bugzilla.redhat.com/show_bug.cgi?id=2008803 — MODIFIED openh264 crashes for all videos When opening any video, gmpopenh264 crashes. opehnh264-2.1.1-3 should fix this, but needs to be added to Cisco's repo. The person responsible at Cisco is on PTO and should be back next week. 8. plasma-discover — https://bugzilla.redhat.com/show_bug.cgi?id=2011333 — NEW Toggling repo in Discover doesn't redraw the checkbox, confusing users Clicking on the checkbox appears to not toggle the status of the repo, but it actually does, the GUI just doesn't update. 9. plasma-systemsettings — https://bugzilla.redhat.com/show_bug.cgi?id=2011231 — NEW HDMI Audio Device is invisible/inactive unless you manually assign it a profile HDMI devices do not appear in the "quick menu" unless the user first goes to the system settings to assign a profile to the device. Your humble FPgM wonders if this is related to the wireplumber bug (BZ 2010683). 10. uboot-tools — https://bugzilla.redhat.com/show_bug.cgi?id=2010449 — ON_QA uboot-tools-2021.10 is available A new uboot-tools release is available. Not having this in installer images generates additional support effort for the entire stable release cycle. Update FEDORA-2021-b1079b7042 contains the new version. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: [Fedocal] Reminder meeting : Prioritized bugs and issues
On Tue, Oct 5, 2021 at 7:00 AM wrote: > > You are kindly invited to the meeting: >Prioritized bugs and issues on 2021-10-06 from 11:00:00 to 12:00:00 > America/Indiana/Indianapolis >At fedora-meetin...@libera.chat > > More information available at: > https://docs.fedoraproject.org/en-US/program_management/prioritized_bugs/ > We will evaluate the following bug: * gnome-shell: gnome-shell killed by SIGSEGV — https://bugzilla.redhat.com/show_bug.cgi?id=1960938 There are no open accepted prioritized bugs. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Fedora Linux 35 Final blocker review summary
esizing. 4. libreport — https://bugzilla.redhat.com/show_bug.cgi?id=2006632 — ASSIGNED Abort doesn't work well Crash reports from abrt fail. This may be an issue with the retrace server. abrt team is investigating. Upstream PR https://github.com/abrt/retrace-server/pull/434 is a candidate fix for the retrace server. 5. spice-vdagent — https://bugzilla.redhat.com/show_bug.cgi?id=2009304 — NEW Mouse cursor offset in VMs with Wayland (but not X11), possibly due to mouse integration The mouse cursor is offset only in Wayland sessions. Removing "Tablet" and "Channel spice" from the VM config removes the offset, but also results in mouse integration being disabled. adamwill has seen this in previous releases on KDE Plasma, but now it appears on Workstation as well. 6. systemd — https://bugzilla.redhat.com/show_bug.cgi?id=2006393 — NEW [DNS over TLS] following connection to a wifi AP, internet is not available for ~30s In some environments, systemd-resolved makes a DNS over TLS request and gets no response, so it wait until it times out. Disabling DNS over TLS avoids the problem. The issue is present regardless of signal strength and is reproducible with a restart of the NetworkManager service. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora Linux 35 Final blocker review summary
F35 Beta is GO! Time to focus on the Final blockers. Action summary Accepted blockers - 1. mesa — gnome-shell: cogl_texture_get_gl_texture(): gnome-shell killed by SIGSEGV — NEW ACTION: Maintainers to revert the regression-causing commit 2. abrt — abrt-dbus segmentation faulted in abrt_p2_service_dbus when shutting down, rebooting, or logging out of Plasma — ASSIGNED ACTION: Maintainers to diagnose and fix issue 3. xdg-desktop-portal — time is transiently incorrect when Automatic Time Zone is enabled — NEW ACTION: Maintainers to diagnose and fix issue Proposed blockers - 1. cockpit — Non-root user cannot join a domain through Cockpit — POST ACTION: Maintainers include upstream PR in an update 2. gedit — gedit crashes when searching for files — NEW ACTION: Maintainers to diagnose and fix issue 3. spice-vdagent — Mouse cursor position has a horizontal and vertical offset after changing resolution in a VM — NEW ACTION: Maintainers to diagnose and fix issue 4. libreport — Abort doesn't work well — NEW ACTION: abrt teams to continue investigating retrace server issue 5. selinux-policy — The switch for Fedora Third Party repositories does not switch them on. — ASSIGNED ACTION: Maintainers to create SELinux policy that permits the appropriate action 6. systemd — [DNS over TLS] following connection to a wifi AP, internet is not available for ~30s — NEW ACTION: Maintainers to fix issue NEEDINFO: lpoetter 7. webkit2gtk3 — crash happens everytime when try to add a google account to Online Account — MODIFIED ACTION: QA to verify FEDORA-2021-c58350f4c8 Bug-by-bug detail = Accepted blockers - 1. mesa — https://bugzilla.redhat.com/show_bug.cgi?id=1989726 — NEW gnome-shell: cogl_texture_get_gl_texture(): gnome-shell killed by SIGSEGV The Tegra driver in mesa has a regression that causes this bug. Working with upstream on this. This bug was waived from F35 Beta. 2. abrt — https://bugzilla.redhat.com/show_bug.cgi?id=1997315 — ASSIGNED abrt-dbus segmentation faulted in abrt_p2_service_dbus when shutting down, rebooting, or logging out of Plasma The crash reporter crashes (preventing us from receiving a crash report from the crash reporter) when logging out or shutting down a graphical session. It appears to be due to a change between glib2-2.69.0-1.fc35 and glib2-2.69.2-1.fc35. 3. xdg-desktop-portal — https://bugzilla.redhat.com/show_bug.cgi?id=1991075 — NEW time is transiently incorrect when Automatic Time Zone is enabled The displayed time is incorrect in some cases when Automatic Time Zone is enabled. Both `timedatectl` and the GNOME display show the wrong time. This behavior appears to exist on F34 and F35. Proposed blockers - 1. cockpit — https://bugzilla.redhat.com/show_bug.cgi?id=2006028 — POST Non-root user cannot join a domain through Cockpit Non-root users who are members of the "Wheel" group cannot join a FreeIPA or AD domain through Cockpit. Upstream PR https://github.com/cockpit-project/cockpit/pull/16371 contains a fix which appears to work. 2. gedit — https://bugzilla.redhat.com/show_bug.cgi?id=2007602 — NEW gedit crashes when searching for files When searching for a file in gedit, it results in a SIGSEGV. 3. spice-vdagent — https://bugzilla.redhat.com/show_bug.cgi?id=2006746 — NEW Mouse cursor position has a horizontal and vertical offset after changing resolution in a VM Occasionally (1/3 times in kparal's testing), the mouse position was offset in a virtual machine until rebooting. 4. libreport — https://bugzilla.redhat.com/show_bug.cgi?id=2006632 — NEW Abort doesn't work well Crash reports from abrt fail. This may be an issue with the retrace server. abrt team is investigating. 5. selinux-policy — https://bugzilla.redhat.com/show_bug.cgi?id=2001837 — ASSIGNED The switch for Fedora Third Party repositories does not switch them on. Enabling third party repos failed, which was sort of fixed in gnome-initial-setup-41~rc-3.fc35. However, when running SELinux in enforcing mode, it still fails. The `pkexec` run as part of gnome-initial-setup leaves the SELinux context unchanged and the xdm_t type does not have the ability to edit the appropriate files. 6. systemd — https://bugzilla.redhat.com/show_bug.cgi?id=2006393 — NEW [DNS over TLS] following connection to a wifi AP, internet is not available for ~30s In some environments, systemd-resolved makes a DNS over TLS request and gets no response, so it wait until it times out. Disabling DNS over TLS avoids the problem, which may be caused by a "router…of questionable quality." 7. webkit2gtk3 — https://bugzilla.redhat.com/show_bug.cgi?id=2006624 — MODIFIED crash happens everytime when try to add a google account to Online Account Trying to add a Google account causes Online Accounts to crash. Update FEDORA-2021-c58350f4c8 contains a candidate fix. -- Ben Cotton He / Him / His Fedora Program
REMINDER: Fedora Linux 35 Beta Go/No-Go meeting tomorrow
We will be holding the F35 Beta Go/No-Go meeting tomorrow at 1700 UTC in #fedora-meeting. For more information, see the calendar event[1] or wiki page[2]. [1] https://calendar.fedoraproject.org/Fedora%20release/#m10064 [2] https://fedoraproject.org/wiki/Go_No_Go_Meeting -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: [Fedocal] Reminder meeting : Prioritized bugs and issues
On Tue, Sep 21, 2021 at 7:00 AM 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-meetin...@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 ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Fedora Linux 35 Beta blocker status summary
Action summary Accepted blockers - 1. mesa — gnome-shell: cogl_texture_get_gl_texture(): gnome-shell killed by SIGSEGV — NEW ACTION: Maintainers to diagnose and fix issue NEEDINFO: karolherbst 2. freeipa — DNS often stops resolving properly after FreeIPA server upgrade to Fedora 35 or 36 — NEW ACTION: Maintainers and QA to determine if the problem occurs outside of the openQA environment 3. selinux-policy — gnome-initial-setup slow to start up, missing Online Accounts page when SELinux in enforcing mode — VERIFIED ACTION: None Proposed blockers - 1. gnome-softare — a removed package looks still installed in gnome-software, can't be installed again until reboot — NEW ACTION: Maintainers to diagnose and fix issue Bug-by-bug detail = Accepted blockers - 1. mesa — https://bugzilla.redhat.com/show_bug.cgi?id=1989726 — NEW gnome-shell: cogl_texture_get_gl_texture(): gnome-shell killed by SIGSEGV gnome-shell gets SIGSEGV on the Jetson Nano, which is blocking hardware for the aarch64 architecture. Upstream MR 1979 contained a candidate fix, but either the issue persists or a new one (BZ 1999681) arises. It appears to be a driver issue. 2. freeipa — https://bugzilla.redhat.com/show_bug.cgi?id=1999321 — NEW DNS often stops resolving properly after FreeIPA server upgrade to Fedora 35 or 36 After upgrade from F33/34, the server stops returning correct DNS responses (empty when they should not be) about 50% of the time. This only happens with upgrades. It also appears to be limited to cases where the server is upgraded but the client is not. Disabling systemd-resolved does not change the behavior. It's unclear if this behavior is only observed in the openQA environment. 3. selinux-policy — https://bugzilla.redhat.com/show_bug.cgi?id=1997310 — VERIFIED gnome-initial-setup slow to start up, missing Online Accounts page when SELinux in enforcing mode gnome-initial-setup skips the Online Accounts page and boots slowly affter selinux-policy-34.16-1.fc35 landed. Confirmed fix in selinux-policy-34.20-1.fc35. Proposed blockers - 1. gnome-software — https://bugzilla.redhat.com/show_bug.cgi?id=2004604 — NEW a removed package looks still installed in gnome-software, can't be installed again until reboot In some cases, Software shows a package as installed after it has been removed. Restarting the Software background process clears this. This appears likely to be rejected as a Beta blocker based on current votes, but may be considered for Final. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Basic criterion proposal: g-i-s shouldn't take 2 minutes to launch
On Fri, Sep 17, 2021 at 3:35 AM Kamil Paral wrote: > > But I also missed his announcement, and when this discussion was renewed, I > thought the criterion still wasn't finalized and in effect. It seems I wasn't > the only one :o) > I also forgot that I had done it when the discussion picked back up. But yeah, I'm definitely flexible on the timing. I think the reason we went with a number was to avoid getting bogged down in what "reasonable" meant. But the existing criterion has its own ambiguity, so if we can make it better*, we should. * But what does "better" mean?! :-D -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Test request for BZ 1996998
Hi folks, Halfline has provided a candidate fix for BZ 1996998. Please get the build from Koji[1] and test. [1] https://koji.fedoraproject.org/koji/taskinfo?taskID=75662323 -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
