devel September 2022

devel@lists.fedoraproject.org

212 participants
262 discussions

F38 proposal: Node.js Repackaging (Self-Contained Change proposal)
by Ben Cotton 12 Dec '22

12 Dec '22

https://fedoraproject.org/wiki/Changes/NodejsRepackaging This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee. == Summary == We are reworking the Node.js packaging to make Node.js versions available as parallel-installable packages. == Owner == * Name: [[User:SGallagh| Stephen Gallagher]] * Email: sgallagh(a)redhat.com == Detailed Description == We will be creating the packages nodejs-16, nodejs-18 and (in April) nodejs-20. These packages will be parallel-installable (with the exception of the -devel subpackages) and provide `/usr/bin/node-$MAJOR`. We will also take advantage of the `alternatives` subsystem to populate `/usr/bin/node` from the default Node.js version for that release, or if the default is not installed, the highest currently-installed version. Notes: * The default in Fedora 38 will be Node.js 18. If a user was to install Node.js 16 and Node.js 20, but not Node.js 18, then Node.js 20 would provide `/usr/bin/node` * The policy going forward will be to have the most recently-released version of Node.js at the time of Fedora's expected Beta release date be the default for that release throughout its lifetime. == Feedback == [https://lists.fedoraproject.org/archives/list/nodejs@lists.fedoraproject.or… Mailing list thread] Neal Gompa raised the question of using a subpackage to own `/usr/bin/node` instead of using the `alternatives` subsystem, citing python as an example. My response was that the problem with this is that I want `/usr/bin/node` to always be available so long as any `nodejs-$MAJOR` version is installed. It also ensures that the `node(1)` manpage always matches the `/usr/bin/node` executable. == Benefit to Fedora == === User Benefits === * Provides a simple way to have a different (or multiple) Node.js interpreters on their system. No dealing with Modularity. * Enables multiple versions of Node.js on the system (can test code against different versions without using containers) === Packager Benefits === * No more modules to maintain. * Availability of multiple Node.js versions in the buildroot means that other `nodejs-*` packages can test against multiple supported options. == Scope == * Proposal owners: The packaging work is done and can be played with at https://copr.fedorainfracloud.org/coprs/sgallagh/nodejs-alternatives/ today. * Other developers: There should be no need to change any dependent packages, though packagers of Node.js software may wish to take advantage of the testing opportunities afforded. * Release engineering: * Policies and guidelines: We will be updating the Node.js Packaging Guidelines with the new best practices. * Trademark approval: N/A (not needed for this Change) * Alignment with Objectives: N/A == Upgrade/compatibility impact == Systems using the existing nodejs RPM package will be upgraded to the matching `nodejs-$MAJOR` version. Work is pending on how to migrate users of Modular Node.js to the new packages. == How To Test == == User Experience == Done correctly, this should be handled entirely without the user's need to know about it. == Dependencies == == Contingency Plan == * Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change) * Contingency deadline: N/A (not a System Wide Change) * Blocks release? N/A (not a System Wide Change) == Documentation == https://lists.fedoraproject.org/archives/list/nodejs@lists.fedoraproject.or… == Release Notes == Multiple releases of Node.js may now be installed in parallel from the Fedora repositories. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis

14 35

Inactive packagers to be removed after the F37 release
by Ben Cotton 03 Dec '22

03 Dec '22

Hello everyone! I just completed the first run of FESCo's newly approved Inactive Packager Policy[1]. Packagers that have been identified as inactive have a ticket in the find-inactive-packagers repo[2]. One week after the F37 final release, packagers who remain inactive will be removed from the packager group. (Note that pagure.io is one of the systems checked for activity, so commenting on your ticket that you're still around will prevent you from showing up in the second round.) Since this is the first time we've done something like this, it could be a little rough. I appreciate your patience and understanding. If you have suggestions for improvement, look for the open feature issues[3] and file an issue in the find-inactive-packagers repo[4] if it's not there already. For the curious, here are the stats from today's run: 2550 users checked 913 of those had no activity on src.fedoraproject.org or pagure.io 835 of those had no activity in Bodhi 812 of those had no activity on the mailing lists 606 of those (~24% of packagers) had no activity in Bugzilla. The script took a little under three hours to run. [1] https://docs.fedoraproject.org/en-US/fesco/Policy_for_inactive_packagers/ [2] https://pagure.io/find-inactive-packagers/issues?tags=inactive_packager&sta… [3] https://pagure.io/find-inactive-packagers/issues?tags=feature [4] https://pagure.io/find-inactive-packagers/new_issue -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis _______________________________________________ devel-announce mailing list -- devel-announce(a)lists.fedoraproject.org To unsubscribe send an email to devel-announce-leave(a)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/devel-announce@lists.fedorapr… Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

47 166

F37 proposal: Add -fno-omit-frame-pointer to default compilation flags (System-Wide Change proposal)
by Ben Cotton 29 Nov '22

29 Nov '22

https://fedoraproject.org/wiki/Changes/fno-omit-frame-pointer This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee. == Summary == Fedora will add -fno-omit-frame-pointer to the default C/C++ compilation flags, which will improve the effectiveness of profiling and debugging tools. == Owner == * Name: [[User:daandemeyer| Daan De Meyer]], [[User:Dcavalca| Davide Cavalca]], [[ Andrii Nakryiko]] * Email: daandemeyer(a)fb.com, dcavalca(a)fb.com, andriin(a)fb.com == Detailed Description == Credits to Mirek Klimos, whose internal note on stacktrace unwinding formed the basis for this change proposal (myreggg(a)gmail.com) Any performance or efficiency work relies on accurate profiling data. Sampling profilers probe the target program's call stack at regular intervals and store the stack traces. If we collect enough of them, we can closely approximate the real cost of a library or function with minimal runtime overhead. Stack trace capture what’s running on a thread. It should start with clone - if the thread was created via clone syscall - or with _start - if it’s the main thread of the process. The last function in the stack trace is code that CPU is currently executing. If a stack starts with [unknown] or any other symbol, it means it's not complete. === Unwinding === How does the profiler get the list of function names? There are two parts of it: # Unwinding the stack - getting a list of virtual addresses pointing to the executable code # Symbolization - translating virtual addresses into human-readable information, like function name, inlined functions at the address, or file name and line number. Unwinding is what we're interested in for the purpose of this proposal. The important things are: * Data on stack is split into frames, each frame belonging to one function. * Right before each function call, the return address is put on the stack. This is the instruction address in the caller to which we will eventually return — and that's what we care about. * One register, called the "frame pointer" or "base pointer" register (RBP), is traditionally used to point to the beginning of the current frame. Every function should back up RBP onto the stack and set it properly at the very beginning. The “frame pointer” part is achieved by adding push %rbp, mov %rsp,%rbp to the beginning of every function and by adding pop %rbp before returning. Using this knowledge, stack unwinding boils down to traversing a linked list: https://i.imgur.com/P6pFdPD.png === Where’s the catch? === The frame pointer register is not necessary to run a compiled binary. It makes it easy to unwind the stack, and some debugging tools rely on frame pointers, but the compiler knows how much data it put on the stack, so it can generate code that doesn't need the RBP. Not using the frame pointer register can make a program more efficient: * We don’t need to back up the value of the register onto the stack, which saves 3 instructions per function. * We can treat the RBP as a general-purpose register and use it for something else. Whether the compiler sets frame pointer or not is controlled by the -fomit-frame-pointer flag and the default is "omit", meaning we can’t use this method of stack unwinding by default. To make it possible to rely on the frame pointer being available, we'll add -fno-omit-frame-pointer to the default C/C++ compilation flags. This will instruct the compiler to make sure the frame pointer is always available. This will in turn allow profiling tools to provide accurate performance data which can drive performance improvements in core libraries and executables. == Feedback == === Potential performance impact === * Meta builds all its libraries and executables with -fno-omit-frame-pointer by default. Internal benchmarks did not show significant impact on performance when omitting the frame pointer for two of our most performance intensive applications. * Firefox recently landed a change to preserve the frame pointer in all jitted code (https://bugzilla.mozilla.org/show_bug.cgi?id=1426134) No significant decrease in performance was observed. * Kernel 4.8 frame pointer benchmarks by Suse showed 5%-10% regressions in some benchmarks (https://lore.kernel.org/all/20170602104048.jkkzssljsompjdwy@suse.de/T/#u) Should individual libraries or executables notice a significant performance degradation caused by including the frame pointer everywhere, these packages can opt-out on an individual basis as described in https://docs.fedoraproject.org/en-US/packaging-guidelines/#_compiler_flags. === Alternatives to frame pointers === There are a few alternative ways to unwind stacks instead of using the frame pointer: * [https://dwarfstd.org DWARF] data - The compiler can emit extra information that allows us to find the beginning of the frame without the frame pointer, which means we can walk the stack exactly as before. The problem is that we need to unwind the stack in kernel space which isn't implemented in the kernel. Given that the kernel implemented it's own format (ORC) instead of using DWARF, it's unlikely that we'll see a DWARF unwinder in the kernel any time soon. The perf tool allows you to use the DWARF data with --call-graph=dwarf, but this means that it copies the full stack on every event and unwinds in user space. This has very high overhead. * [https://www.kernel.org/doc/html/v5.3/x86/orc-unwinder.html ORC] (undwarf) - problems with unwinding in kernel led to creation of another format with the same purpose as DWARF, just much simpler. This can only be used to unwind kernel stack traces; it doesn't help us with userspace stacks. More information on ORC can be found [https://lwn.net/Articles/728339 here]. * [https://lwn.net/Articles/680985 LBR] - New Intel CPUs have a feature that gives you source and target addresses for the last 16 (or 32, in newer CPUs) branches with no overhead. It can be configured to record only function calls and to be used as a stack, which means it can be used to get the stack trace. Sadly, you only get the last X calls, and not the full stack trace, so the data can be very incomplete. On top of that, many Fedora users might still be using CPUs without LBR support which means we wouldn't be able to assume working profilers on a Fedora system by default. To summarize, if we want complete stacks with reasonably low overhead (which we do, there's no other way to get accurate profiling data from running services), frame pointers are currently the best option. == Benefit to Fedora == Implementing this change will provide profiling tools with easy access to stacktraces of installed libraries and executables which will lead to more accurate profiling data in general. This in turn can be used to implement optimizations to core libraries and executables which will improve the overall performance of Fedora itself and the wider Linux ecosystem. Various debugging tools can also make use of the frame pointer to access the current stacktrace, although tools like gdb can already do this to some degree via embedded dwarf debugging info. == Scope == * Proposal owners: Put up a PR to change the rpm macros to build packages by default with -fno-omit-frame-pointer by default. * Other developers: Review and merge the PR implementing the Change. * Release engineering: [https://pagure.io/releng/issues #Releng issue number]. A mass rebuild is required. * Policies and guidelines: N/A (not needed for this Change) * Trademark approval: N/A (not needed for this Change) * Alignment with Objectives: N/A == Upgrade/compatibility impact == This should not impact upgrades in any way. == How To Test == # Build the package with the updated rpm macros # Profile the binary with `perf record -g <binary>` # Inspect the perf data with `perf report -g 'graph,0.5,caller'` # When expanding hot functions in the perf report, perf should show the full call graph of the hot function (at least for all functions that are part of the binary compiled with -fno-omit-frame-pointer) == User Experience == Fedora users will be more likely to have a streamlined experience when trying to debug/profile system executables/libraries. Tools such as perf will work out of the box instead of requiring to users to provide extra options (e.g. --call-graph=dwarf/LBR) or requiring users to recompile all relevant packages with -fno-omit-frame-pointer. == Dependencies == The rpm macros for Fedora need to be adjusted to include -fno-omit-frame-pointer in the default C/C++ compilation flags. == Contingency Plan == * Contingency mechanism: The new version can be released without every package being rebuilt with fno-omit-frame-pointer. Profiling will only work perfectly once all packages have been rebuilt but there will be no regression in behavior if not all packages have been rebuilt by the time of the release. If the Change is found to introduce unacceptable regressions, the PR implementing it can be reverted and affected packages can be rebuilt. * Contingency deadline: Final freeze * Blocks release? No == Documentation == * Original proposal for in-kernel DWARF unwinder (rejected): https://lkml.org/lkml/2017/5/5/571 == Release Notes == Packages are now compiled with frame pointers included by default. This will enable a variety of profiling and debugging tools to show more information out of the box. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis

39 142

Updating asio in rawhide (and possibly F37) to 1.24.0
by Julian Sikorski 29 Nov '22

29 Nov '22

Dear maintainers, I have updated Fedora asio package from the current 1.16.1 to 1.24.0. I have rebuilt the seven current dependencies and with the exception of OpenSceneGraph, all build fine against the updated asio package. While OpenSceneGraph failed to build, the failure does not seem to have to do anything with asio. I have created a side tag so that the rebuilds can be coordinated: f38-build-side-56604. I do not have provenpacker privileges which means you have to request the rebuilds yourself. You can start once the asio build [1] finishes. Thank you for your cooperation in advance. Best regards, Julian [1] https://koji.fedoraproject.org/koji/taskinfo?taskID=90781633

3 6

fedpkg clone fails with Permission denied (publickey).
by Richard Shaw 26 Nov '22

26 Nov '22

Long story short I lost my home directory where I do all of my packager activities (separate from my main user) so I'm setting things up from scratch. I created new ssh keys and uploaded the public key to admin.fedoraproject.org and pasted into pagure.io. It's been over an hour and I'm still getting: $ fedpkg clone hamlib Cloning into 'hamlib'... hobbes1069(a)pkgs.fedoraproject.org: Permission denied (publickey). fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. Could not execute clone: Failed to execute command. I've also updated my API tokens, which is STILL not well documented. I pasted them in the appropriate spot in "/etc/rpkg/fedpkg.conf" which isn't real intuitive. Thanks, Richard

5 10

Mesa in F37- vaapi support disabled for h264/h265/vc1
by Frantisek Zatloukal 16 Nov '22

16 Nov '22

Hi, since this mesa change ( https://src.fedoraproject.org/rpms/mesa/c/94ef544b3f2125912dfbff4c6ef373fe4… ) in F37 and rawhide, the mesa package lost support for vaapi accelerated encoding and decoding of h264, h265 and decoding of vc1 ( https://bugzilla.redhat.com/show_bug.cgi?id=2123998 ). It seems like a big regression from F36 for users with GPUs with open source drivers (mainly AMD, maybe nVidia/other non x86...), that affects common use-cases of Fedora Workstation, like watching videos, in-house game streaming, attending online meetings and many more. I'd like to ask: - Can somebody elaborate on reasons to change something that was working in Fedora for some time already? - Is there any short/mid/long term plan to improve the situation? - Would it be possible to provide vaapi support at least as an rpmfusion addon to alleviate the fallout in the short term? Thanks! -- Best regards / S pozdravem, František Zatloukal Senior Quality Engineer Red Hat

37 86

CVE Tracking Bugs
by Maxwell G 09 Nov '22

09 Nov '22

Hi Fedorians, I think the security tracking bug filing process needs to be amended. The current process is quite frustrating for me and other contributors. This is especially bad for Go CVEs, which there are lot of. Red Hat Product Security creates a single tracking bug for Fedora{, EPEL} _and_ all Red Hat products and CCs a bunch of Fedora maintainers. They then create separate bugs for each package that they deem affected. The affected packages are oftened determined in a manner that appears overzealous and arbitrary. After the bugs are created, we get spammed with a bunch of notifications about private bugs, RH product errata, and various other things that are completely irrelevant to Fedora. These messages flood my Bugzilla mailbox and obscure actual issues that I need to address. I do not really care whether a Go CVE has been mitigated in Red Hat Advanced Cluster Management for Kubernetes 2.4 for RHEL 8" or "Red Hat Advanced Cluster Management for Kubernetes 2.5 for RHEL 8" or "Red Hat Advanced Cluster Management for Kubernetes 2.6 for RHEL 8." --- Some particularly egregious examples: I maintain an Ansible kubernetes collection, and they reported it as vulnerable to some CVE with a specific Openshift component. The collection not vulnerable. They provided no actionable information, and the description was unclear. When I asked why it was reported, they said that the package "used OpenShift." A couple Go CVEs ago[^1], they created bugs against hundreds of Go libraries. They arbitrarily chose branches and packages. The bugs were not actionable by packagers of individual go libraries. Only applications that provide binaries need to be rebuilt. They were reported shortly before the F34 EOL, so we got a huge amount of emails after the bugs were automatically closed. In fact, a Go packager reported that these messages from the _security_ team DOSed their mail server. To their credit, they have fixed this issue after one of the other Go SIG people talked to them. Now, these bugs are only filed against the golang component. [^1]: Really, it was a couple Go releases ago. There are multiple CVEs reported with each Go release these days. Another time, their automation posted the exact same comment over 200 times. --- First and foremost, there needs to be a clear way for packagers to report problems with this process to prodsec. I don't think Fedora packagers should be CCed on these global trackers. We could create a separate "Security Response" component under the "Fedora" Bugzilla product to create tracker bugs for CVEs that affect multiple Fedora components, or we could ask prodsec to only CC Fedora maintainers on the child, package-level bugs. I guess I could acomplish what I'm proposing by filtering out mails with "X-Bugzilla-Product: Security Response" headers and not have gone on this rant, but I still think this needs to be addressed. Does anyone know how to reach prodsec about this? -- Best, Maxwell G (@gotmax23) Pronouns: He/Him/His

13 17

Fedora SCM requests on the weekend
by Robert-André Mauchin 07 Nov '22

07 Nov '22

Hello, I know a lot of you are working on Fedora during the week days, but for some of us, the weekend is the only time we can spend time on it. The problem is, SCM requests are rarely processed during that time, most of them get stuck from Friday afternoon to Monday afternoon (CEST), so it really hampers my work. Would it be possible for a volunteer to agree to do it on the weekend. Best regards, Robert-André

10 12

Re: Planning to start unifying native and mingw packages
by Sandro Mani 07 Nov '22

07 Nov '22

On 03.09.22 18:09, Richard Shaw wrote: > On Sat, Sep 3, 2022 at 10:33 AM Richard Shaw <hobbes1069(a)gmail.com> wrote: > > On Sat, Sep 3, 2022 at 10:22 AM Sandro Mani <manisandro(a)gmail.com> > wrote: > > > On 03.09.22 17:10, Richard Shaw wrote: > > I'm trying to migrate fltk right now and running into an issue: > > > > Processing files: fltk-debugsource-1.3.8-4.fc38.x86_64 > > > > RPM build warnings: > > > > RPM build errors: > > error: Could not open %files file > > /builddir/build/BUILD/fltk-1.3.8/debugsourcefiles.list: No > such file > > or directory > > > > Building the mingw packages seems to be interfering with the > native build. > > > I put %{?mingw_package_header} in the %{with mingw} (disabled) > conditional this time and the build completed, so something in there > is causing the issue. You actually don't need %{?mingw_package_header} anymore at all (it actually should just be a no-op with a current mingw-filesystem). Sandro

3 3

F37 Final blocker status update
by Ben Cotton 04 Nov '22

04 Nov '22

Fedora Linux 37 Final freeze begins Tuesday 4 October. Action summary ==================== Accepted blockers ----------------- 1. anaconda — Custom partitioning with 2 drives selected, bootloader fails to install due to one drive not having a BIOS Boot partition — ON_QA ACTION: QA to verify FEDORA-2022-c20d42f3bc 2. gnome-contacts — When a single contact is edited, it results in multiple contacts of the same name. — ON_QA ACTION: QA to verify FEDORA-2022-acbfee2ce8 3. gnome-initial-setup — Unable to set up enterprise account with gnome-initial-setup, clicking continue does not join the domain — ASSIGNED ACTION: dgilmore to test https://koji.fedoraproject.org/koji/taskinfo?taskID=92037333 4. gnome-shell — GNOME Initial Setup uses the English keyboard, instead of the default keyboard — ASSIGNED ACTION: Upstream to diagnose and resolve issue 5. gnome-shell — Attempting to disconnect VPN connection from system menu does nothing — VERIFIED ACTION: (none) 6. gnome-software — Can't install a local rpm package anymore, Install button missing (for certain RPMs) — VERIFIED ACTION: (none) 7. greenboot — greenboot-grub2-set-counter.service fails on 38 IoT with "cannot open `/boot/grub2/grubenv.new`: No such file or directory." — NEW ACTION: Maintainers to diagnose issue 8. grub2 — Windows with bitlocker enabled can't be booted, needs to use bootnext instead of chainloader — NEW ACTION: Maintainers to diagnose issue or provide status update 9. mesa — totem: nouveau_pushbuf_data(): totem killed by SIGABRT — NEW ACTION: Maintainers to update mesa with fixes for F37 10. uboot-tools — Regression booting Fedora on rockchip devices installed on PCIe NVME drives — ON_QA ACTION: QA to verify FEDORA-2022-c1d9e8daa9 Proposed blockers ----------------- 1. chrome-gnome-shell — Project name and source repository changed to gnome-browser-connector — NEW ACTION: Reviewer to approve new gnome-browser-connector package. 2. gnome-shell — screencast doesn't record the top layer — NEW ACTION: QA to verify if behavior still exists 3. gnome-shell-extension-background-logo — Update gnome-shell-extension-background-logo to 43.0 — NEW ACTION: Maintainer to update package 4. systemd — Czech qwerty layout configured in anaconda, but qwertz layout used in disk unlock and in VT console — NEW ACTION: kbd maintainers to reconsider the -legacy subpackage split Bug-by-bug detail ============= Accepted blockers ----------------- 1. anaconda — https://bugzilla.redhat.com/show_bug.cgi?id=2088113 — ON_QA Custom partitioning with 2 drives selected, bootloader fails to install due to one drive not having a BIOS Boot partition When using custom partitioning on two drives with /boot on a RAID 1 device, the installer only creates one BIOS boot. grub2-install is run against both drives, but the second fails because it has no BIOS boot partition. FEDORA-2022-c20d42f3bc contains a candidate fix. 2. gnome-contacts — https://bugzilla.redhat.com/show_bug.cgi?id=2111003 — ON_QA When a single contact is edited, it results in multiple contacts of the same name. Editing a contact results in the contact being properly updated, but an empty contact is created with the same name. FEDORA-2022-acbfee2ce8 contains a candidate fix. 3. gnome-initial-setup — https://bugzilla.redhat.com/show_bug.cgi?id=2123494 — ASSIGNED Unable to set up enterprise account with gnome-initial-setup, clicking continue does not join the domain Initially the buttons were missing. Update FEDORA-2022-50e585b456 fixed that issue, however clicking the button does not joing the domain. Instead, the user is returned to the domain credentials screen, resulting in an endless loop. https://koji.fedoraproject.org/koji/taskinfo?taskID=92037333 contains a backport of upstream's change which may fix it. 4. gnome-shell — https://bugzilla.redhat.com/show_bug.cgi?id=2121110 — ASSIGNED GNOME Initial Setup uses the English keyboard, instead of the default keyboard Regardless of the default keyboard setting, g-i-s uses the English keyboard. Relatedly, new users have the English keyboard selected, even though another language is shown as the default. FEDORA-2022-52cdfc7920 failed to fix this issue. 5. gnome-shell — https://bugzilla.redhat.com/show_bug.cgi?id=2125252 — VERIFIED Attempting to disconnect VPN connection from system menu does nothing Disabling a VPN doesn't disable the VPN. Fixed in FEDORA-2022-50e585b456. 6. gnome-software — https://bugzilla.redhat.com/show_bug.cgi?id=2124869 — VERIFIED Can't install a local rpm package anymore, Install button missing (for certain RPMs) What it says on the tin. Fixed in FEDORA-2022-b6246d02fa. 7. greenboot — https://bugzilla.redhat.com/show_bug.cgi?id=2121944 — NEW greenboot-grub2-set-counter.service fails on 38 IoT with "cannot open `/boot/grub2/grubenv.new`: No such file or directory." greenboot service fails on a file-not-found error. This also results in rebase tests failing because of conflicts with the rebase triggered by the greenboot failure. 8. grub2 — https://bugzilla.redhat.com/show_bug.cgi?id=2049849 — NEW Windows with bitlocker enabled can't be booted, needs to use bootnext instead of chainloader Dual-booting recent Windows 10 system with TPM 2.0 fails because bitlocker can't be unsealed by the TPM. This was waived to F37 under the "difficult to fix" exception. No additional updates have been provided. 9. mesa — https://bugzilla.redhat.com/show_bug.cgi?id=2123274 — NEW totem: nouveau_pushbuf_data(): totem killed by SIGABRT totem plays ~1 second of video and then crashes. This appears to happen with all video formats. This appears to be an issue in multithreading support in the nouveau driver, which is fixed upstream. The fix is large and may not be suitable for backporting, but would be available in a mesa-22.3 update. 10. uboot-tools — https://bugzilla.redhat.com/show_bug.cgi?id=2124127 — ON_QA Regression booting Fedora on rockchip devices installed on PCIe NVME drives uboot-tools introducted a regression when used with 5.19.x kernels. FEDORA-2022-c1d9e8daa9 contains a candidate fix. Proposed blockers ----------------- 1. chrome-gnome-shell — https://bugzilla.redhat.com/show_bug.cgi?id=2106868 — NEW Project name and source repository changed to gnome-browser-connector Upstream has split this into two packages. Package review pending for renamed package: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2127314 2. gnome-shell — https://bugzilla.redhat.com/show_bug.cgi?id=2125439 — NEW screencast doesn't record the top layer Typing and popup windows don't show when recording a screencast. This may be fixed in pipewire-gstreamer-0.3.57-1. 3. gnome-shell-extension-background-logo — https://bugzilla.redhat.com/show_bug.cgi?id=2127192 — NEW Update gnome-shell-extension-background-logo to 43.0 The Fedora logo is not displayed and the package is not compatible with gnome-shell 43. 4. systemd — https://bugzilla.redhat.com/show_bug.cgi?id=2121106 — NEW Czech qwerty layout configured in anaconda, but qwertz layout used in disk unlock and in VT console The wrong keymap is used when unlocking disks or virtual terminals. It looks like this may have never worked. It looks like an issue with how layouts are mapped between console and xkb. Adam is thinking about how to approach this: https://bugzilla.redhat.com/show_bug.cgi?id=2121106#c24 -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis

2 8

← Newer
1
2
3
4
5
6
7
...
27
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

devel September 2022