test September 2022

test@lists.fedoraproject.org

34 participants
40 discussions

reversible dual-boot test station
by Chris Murphy 23 Feb '24

23 Feb '24

Hi, I mentioned this in a QA meeting, and have given it enough testing that I think it's broadly usable. If desired it can be copied out of my user account and put up somewhere where QA folks will see it and can modify it as issues or improvements are discovered. What is it? The idea is to produce a system that can confidently be used for baremetal testing, without risking the primary operating system. While VM's are a great way to test, it's also a really idealized environment that tends to not expose an assortment of bugs that affect particular hardware. But then quite a lot of folks reasonably don't want to upgrade their daily use hardware early on, because they don't want to always have to debug things, or have to figure out how to undo the upgrade if it really goes badly. Therefore, I present a dual-boot setup offering: * no re-partitioning; * no installation step, instead system upgrade is used; * reversibility, or undoability, i.e. with just a few steps you can delete the "test OS". https://fedoraproject.org/wiki/User:Chrismurphy/Draft/dualboot_teststation -- Chris Murphy

2 5

Re: Thoughts welcome: interface between automated test gating and the "critical path"
by Adam Williamson 16 Aug '23

16 Aug '23

On Fri, 2022-09-02 at 08:37 +0000, Zbigniew Jędrzejewski-Szmek wrote: > > > > Now, because I glued openQA to the critpath because it was handy, there > > are two sets of consequences to a package being in critical path: > > > > 1. Tighter Bodhi requirements > > 2. openQA tests are run, and results gate the update (except Rawhide) > > > > So, one of the implicit questions here is, is it OK to keep twinning > > these two sets of consequences, or should we split them up? Splitting > > them up kinda implies answer 2) from my original mail: "Keep the > > current "critical path" concept but define a broader group > > of "gated packages" somewhere". Because we would then need some new > > concept that isn't "critical path". As I said, that's more *work* - > > it'd require us to write new code in several places[0]. Even if we > > decide it'd be nice to do this, is it nice *enough* to be worth doing > > that work? > > I'd still vote for keeping a single critpath list and using it as > "the list of packages that require extra care and testing". > > As you describe, the original meaning of critpath has shifted, but > it's because the way we do updates and QA has also shifted. Doing > gating tests for a package seems much more useful than just keeping > it longer in 'updates-testing' in hope that somebody discovers an > important regresion in the second week. Well, there's a caveat there - openQA doesn't test everything. On the whole we cover quite a lot with the set of tests that gets run on updates, but there's certainly lots of potential for there to be important bugs it misses, that a human tester might catch. So I think there is still a case for the higher karma requirements too. > > So yeah, I don't think it makes sense to do the extra work to split > the concepts. Also because we have way too many concepts and processes > in Fedora already. On the whole, though, I agree with you. I just don't trust my own opinion because it's obviously biased by what's convenient for me. :D > > If we don't think it's worth doing that work, then we're kinda stuck > > with openQA glomming onto the critpath definition to decide which > > updates to test and gate, because I don't have any other current viable > > choices for that, really. And we'd have to figure out a critpath > > definition that's as viable as possible for both purposes. > > > > > > BTW, one other thought I've had in relation to all this is that we > > could enhance the current critpath definition somewhat. Right now, it's > > built out of package groups in comps which are kinda topic-separated: > > there's a critpath-kde, a critpath-gnome, a critpath-server, and so on. > > But the generated critical path package list is a monolith: it doesn't > > distinguish between a package that's on the GNOME critpath and a > > package that's on the KDE critpath, you just get a big list of all > > critpath packages. It might be nice if we actually did distinguish > > between those - the critpath definition could keep track of which > > critpath topic(s) a package is included in, and Bodhi could display > > that information in the web UI and provide it via the API. That way > > manual testers could get a bit more info on why a package is critpath > > and what areas to test, and openQA could potentially target its test > > runs to conserve resources a bit, though this might require a bit more > > coding work on the gating stuff now I think about it. > > That sounds useful. We only need a volunteer to figure out the details > and do the work ;) I actually did a huge rewrite of the thing that generates the critpath data this week, and it probably wouldn't be tooooo much work, honestly. The most annoying bit would be the Bodhi frontend stuff, but that's because I'm bad at frontend dev in general. :P But yeah, this is definitely off in sky-castle land. I'll add it to my ever-growing list of sky-castle projects to do when I get a couple of years of spare time... -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net

3 4

Plan / proposal: enable openQA update testing and potentially gating on Rawhide updates
by Adam Williamson 09 Jun '23

09 Jun '23

Hi folks! We've had openQA testing of updates for stable and branched releases, and gating based on those tests, enabled for a while now. I believe this is going quite well, and I think we addressed the issues reported when we first enabled gating - Bodhi's gating status updates work more smoothly now, and openQA respects Bodhi's "re-run tests" button so failed tests can be re-triggered. A few weeks ago, I enabled testing of Rawhide updates in the openQA lab/stg instance. This was to see how smoothly the tests run, how often we run into unexpected failures or problems, and whether the hardware resources we have are sufficient for the extra load. So far this has been going more smoothly than I anticipated, if anything. The workers seem to keep up with the test load, even though one out of three worker systems for the stg instance is currently out of commission (we're using it to investigate a bug). We do get occasional failures which seem to be related to Rawhide kernel slowness (e.g. operations timing out that usually don't otherwise time out), but on the whole, the level of false failures is (I would say) acceptably low, enough that my current regime of checking the test results daily and restarting failed ones that don't seem to indicate a real bug should be sufficient. So, I'd like to propose that we enable Rawhide update testing on the production openQA instance also. This would cause results to appear on the Automated Tests tab in Bodhi, but they would be only informational (and unless the update was gated by a CI test, or somehow otherwise configured not to be pushed automatically, updates would continue to be pushed 'stable' almost immediately on creation, regardless of the openQA results). More significantly, I'd also propose that we turn on gating on openQA results for Rawhide updates. This would mean Rawhide updates would be held from going 'stable' (and included in the next compose) until the gating openQA tests had run and passed. We may want to do this a bit after turning on the tests; perhaps Fedora 37 branch point would be a natural time to do it. Currently this would usually mean a wait from update submission to 'stable push' (which really means that the build goes into the buildroot, and will go into the next Rawhide compose when it happens) of somewhere between 45 minutes and a couple of hours. It would also mean that if Rawhide updates for inter-dependent packages are not correctly grouped, the dependent update(s) will fail testing and be gated until the update they depend on has passed testing and been pushed. The tests for the dependent update(s) would then need to be re- run, either by someone hitting the button in Bodhi or an openQA admin noticing and restarting them, before the dependent update(s) could be pushed. In the worst case, if updated packages A and B both need the other to work correctly but the updates are submitted separately, both updates may fail tests and be blocked. This could only be resolved by waiving the failures, or replacing the separate updates with an update containing both packages. All of those considerations are already true for stable and branched releases, but people are probably more used to grouping updates for stable and branched than doing it for Rawhide, and the typical flow of going from a build to an update provides more opportunity to create grouped updates for branched/stable. For Rawhide the easiest way to do it if you need to do it is to do the builds in a side tag and use Bodhi's ability to create updates from a side tag. As with branched/stable, only critical path updates would have the tests run and be gated on the results. Non-critpath updates would be unaffected. (There's a small allowlist of non-critpath packages for which the tests are also run, but they are not currently gated on the results). I think doing this could really help us keep Rawhide solid and avoid introducing major compose-breaking bugs, at minimal cost. But it's a significant change and I wanted to see what folks think. In particular, if you find the existing gating of updates for stable/branched releases to cause problems in any way, I'd love to hear about it. Thanks folks! -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net

3 4

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

F37 GPU thread crash on Ryzen 6000 iGPU: GL_OUT_OF_MEMORY in glReadPixels
by Leon White 10 Oct '22

10 Oct '22

Hello, first time posting here. I have an Ryzen 6000 with iGPU (Radeon 680M) hardware compatibility bug that I can reproduce under Fedora 37, as well as 36 a number of other distros. To reproduce, install Fedora, install VS Code (or any other Electron app such as Slack or Spotify) and go to fullscreen or attempt to resize the window diagonally for a few seconds, or attempt to wake from sleep. This will result in a GPU thread crash (visible with `sudo journalctl _UID=1000`) and kernel core dump (`sudo dmesg`). In some cases the system can recover, but stability is poor until the system is rebooted. Using the dGPU results in some improvement, but still crashes when waking from sleep. Fedora 37 Beta (all updates installed) Kernel: 5.19.11 Gnome: 43.0 Hardware: Lenovo Z16 Gen 1 (UEFI 1.22) amdgpu issue thread: https://gitlab.freedesktop.org/drm/amd/-/issues/2149 video of the issue recorded for Lenovo support: https://www.loom.com/share/a474ff44a09c422698cb588a8e206a15 inxi: Graphics: Device-1: AMD Navi 24 [Radeon RX 6400 / 6500 XT] vendor: Lenovo driver: amdgpu v: kernel arch: RDNA-2 pcie: speed: 16 GT/s lanes: 16 bus-ID: 03:00.0 chip-ID: 1002:743f Device-2: AMD Rembrandt [Radeon 680M] vendor: Lenovo driver: amdgpu v: kernel arch: RDNA-2 pcie: speed: 16 GT/s lanes: 16 ports: active: eDP-1 empty: DP-1, DP-2, DP-3, DP-4, DP-5, DP-6, DP-7 bus-ID: 67:00.0 chip-ID: 1002:1681 Device-3: Chicony Integrated Camera type: USB driver: uvcvideo bus-ID: 1-4:2 chip-ID: 04f2:b78b Device-4: Chicony Integrated IR Camera type: USB driver: N/A bus-ID: 5-1:2 chip-ID: 04f2:b78c Display: wayland server: X.org v: 1.20.14 with: Xwayland v: 22.1.3 compositor: gnome-shell v: 43.0 driver: gpu: amdgpu display-ID: 0 Monitor-1: eDP-1 model: Samsung 0x4165 res: 3840x2400 dpi: 284 diag: 406mm (16") OpenGL: renderer: REMBRANDT (rembrandt LLVM 15.0.0 DRM 3.47 5.19.11-300.fc37.x86_64) v: 4.6 Mesa 22.2.0 direct render: Yes journalctl: Sep 28 16:07:29 fedora gnome-shell[7910]: Failed to scan out client buffer: drmModeAtomicCommit: Cannot allocate memory Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: Failed to allocate a buffer: Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: size : 37683200 bytes Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: alignment : 2097152 bytes Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: domains : 4 Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: flags : 6 Sep 28 16:07:29 fedora gnome-shell[7910]: Failed to scan out client buffer: drmModeAtomicCommit: Cannot allocate memory Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: Failed to allocate a buffer: Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: size : 38928384 bytes Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: alignment : 2097152 bytes Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: domains : 4 Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: flags : 6 Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: Failed to allocate a buffer: Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: size : 38928384 bytes Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: alignment : 2097152 bytes Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: domains : 4 Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: flags : 6 Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: Failed to allocate a buffer: Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: size : 38764544 bytes Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: alignment : 2097152 bytes Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: domains : 4 Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: flags : 6 Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: Failed to allocate a buffer: Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: size : 38764544 bytes Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: alignment : 2097152 bytes Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: domains : 4 Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: flags : 6 Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: Failed to allocate a buffer: Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: size : 38764544 bytes Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: alignment : 2097152 bytes Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: domains : 4 Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: flags : 6 Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: Failed to allocate a buffer: Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: size : 38764544 bytes Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: alignment : 2097152 bytes Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: domains : 4 Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: flags : 6 Sep 28 16:07:29 fedora gnome-shell[9533]: (WW) glamor: Failed to allocate 3844x2340 FBO due to GL_OUT_OF_MEMORY. Sep 28 16:07:29 fedora gnome-shell[9533]: (WW) glamor: Expect reduced performance. Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: Failed to allocate a buffer: Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: size : 35942400 bytes Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: alignment : 2097152 bytes Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: domains : 2 Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: flags : 0 Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: Failed to allocate a buffer: Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: size : 35942400 bytes Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: alignment : 2097152 bytes Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: domains : 2 Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: flags : 0 Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: Failed to allocate a buffer: Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: size : 35942400 bytes Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: alignment : 2097152 bytes Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: domains : 2 Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: flags : 0 Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: Failed to allocate a buffer: Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: size : 35942400 bytes Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: alignment : 2097152 bytes Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: domains : 2 Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: flags : 0 Sep 28 16:07:29 fedora gnome-shell[9533]: EE ../src/gallium/drivers/radeonsi/si_texture.c:1917 si_texture_transfer_map - failed to create temporary texture to hold untiled copy Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) glamor0: GL error: GL_OUT_OF_MEMORY in glReadPixels Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) Backtrace: Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) 0: /usr/bin/Xwayland (0x5655542ed000+0x16d1b2) [0x56555445a1b2] Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) 1: /usr/lib64/dri/radeonsi_dri.so (0x7fd6c1af9000+0x1151ea) [0x7fd6c1c0e1ea] Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) 2: /usr/lib64/dri/radeonsi_dri.so (0x7fd6c1af9000+0x2fdbb6) [0x7fd6c1df6bb6] Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) 3: /usr/lib64/dri/radeonsi_dri.so (0x7fd6c1af9000+0x33ce42) [0x7fd6c1e35e42] Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) 4: /usr/lib64/dri/radeonsi_dri.so (0x7fd6c1af9000+0x2fe7a1) [0x7fd6c1df77a1] Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) 5: /usr/lib64/dri/radeonsi_dri.so (0x7fd6c1af9000+0x2fea36) [0x7fd6c1df7a36] Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) 6: /usr/bin/Xwayland (0x5655542ed000+0x69c4e) [0x565554356c4e] Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) 7: /usr/bin/Xwayland (0x5655542ed000+0x5896f) [0x56555434596f] Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) 8: /usr/bin/Xwayland (0x5655542ed000+0x5924d) [0x56555434624d] Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) 9: /usr/bin/Xwayland (0x5655542ed000+0x1abc63) [0x565554498c63] Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) 10: /usr/bin/Xwayland (0x5655542ed000+0x1ac3ce) [0x5655544993ce] Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) 11: /usr/bin/Xwayland (0x5655542ed000+0x53526) [0x565554340526] Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) 12: /usr/bin/Xwayland (0x5655542ed000+0xf49bf) [0x5655543e19bf] Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) 13: /usr/bin/Xwayland (0x5655542ed000+0xd21e9) [0x5655543bf1e9] Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) 14: /usr/bin/Xwayland (0x5655542ed000+0xf7345) [0x5655543e4345] Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) 15: /usr/bin/Xwayland (0x5655542ed000+0x94a4e) [0x565554381a4e] Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) 16: /usr/bin/Xwayland (0x5655542ed000+0x4c046) [0x565554339046] Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) 17: /usr/bin/Xwayland (0x5655542ed000+0xd1d82) [0x5655543bed82] Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) 18: /usr/bin/Xwayland (0x5655542ed000+0xd4d03) [0x5655543c1d03] Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) 19: /usr/bin/Xwayland (0x5655542ed000+0xa2980) [0x56555438f980] Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) 20: /usr/bin/Xwayland (0x5655542ed000+0xab6a8) [0x5655543986a8] Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) 21: /usr/bin/Xwayland (0x5655542ed000+0x38bd1) [0x565554325bd1] Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) 22: /lib64/libc.so.6 (0x7fd6c3e75000+0x23510) [0x7fd6c3e98510] Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) 23: /lib64/libc.so.6 (__libc_start_main+0x89) [0x7fd6c3e985c9] Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) 24: /usr/bin/Xwayland (0x5655542ed000+0x3a3f5) [0x5655543273f5] Sep 28 16:07:29 fedora gnome-shell[9533]: (EE) Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: Failed to allocate a buffer: Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: size : 36864000 bytes Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: alignment : 2097152 bytes Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: domains : 2 Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: flags : 0 Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: Failed to allocate a buffer: Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: size : 36864000 bytes Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: alignment : 2097152 bytes Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: domains : 2 Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: flags : 0 Sep 28 16:07:29 fedora gnome-shell[9533]: (WW) glamor: Failed to allocate 36864000 bytes PBO due to GL_OUT_OF_MEMORY. Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: Failed to allocate a buffer: Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: size : 36864000 bytes Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: alignment : 2097152 bytes Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: domains : 2 Sep 28 16:07:29 fedora gnome-shell[9533]: amdgpu: flags : 0 Sep 28 16:07:30 fedora gnome-shell[9533]: amdgpu: Failed to allocate a buffer: Sep 28 16:07:30 fedora gnome-shell[9533]: amdgpu: size : 36864000 bytes Sep 28 16:07:30 fedora gnome-shell[9533]: amdgpu: alignment : 2097152 bytes Sep 28 16:07:30 fedora gnome-shell[9533]: amdgpu: domains : 2 Sep 28 16:07:30 fedora gnome-shell[9533]: amdgpu: flags : 0 Sep 28 16:07:30 fedora gnome-shell[9533]: EE ../src/gallium/drivers/radeonsi/si_texture.c:1917 si_texture_transfer_map - failed to create temporary texture to hold untiled copy Sep 28 16:07:30 fedora gnome-shell[9533]: (EE) glamor0: GL error: GL_OUT_OF_MEMORY in glReadPixels Sep 28 16:07:30 fedora gnome-shell[9533]: (EE) Sep 28 16:07:30 fedora gnome-shell[9533]: (EE) Backtrace: Sep 28 16:07:30 fedora gnome-shell[9533]: (EE) 0: /usr/bin/Xwayland (0x5655542ed000+0x16d1b2) [0x56555445a1b2] Sep 28 16:07:30 fedora gnome-shell[9533]: (EE) 1: /usr/lib64/dri/radeonsi_dri.so (0x7fd6c1af9000+0x1151ea) [0x7fd6c1c0e1ea] Sep 28 16:07:30 fedora gnome-shell[9533]: (EE) 2: /usr/lib64/dri/radeonsi_dri.so (0x7fd6c1af9000+0x2fdbb6) [0x7fd6c1df6bb6] Sep 28 16:07:30 fedora gnome-shell[9533]: (EE) 3: /usr/lib64/dri/radeonsi_dri.so (0x7fd6c1af9000+0x33ce42) [0x7fd6c1e35e42] Sep 28 16:07:30 fedora gnome-shell[9533]: (EE) 4: /usr/lib64/dri/radeonsi_dri.so (0x7fd6c1af9000+0x2fe7a1) [0x7fd6c1df77a1] Sep 28 16:07:30 fedora gnome-shell[9533]: (EE) 5: /usr/lib64/dri/radeonsi_dri.so (0x7fd6c1af9000+0x2fea36) [0x7fd6c1df7a36] Sep 28 16:07:30 fedora gnome-shell[9533]: (EE) 6: /usr/bin/Xwayland (0x5655542ed000+0x69c4e) [0x565554356c4e] Sep 28 16:07:30 fedora gnome-shell[9533]: (EE) 7: /usr/bin/Xwayland (0x5655542ed000+0x5e99f) [0x56555434b99f] Sep 28 16:07:30 fedora gnome-shell[9533]: (EE) 8: /usr/bin/Xwayland (0x5655542ed000+0x628bb) [0x56555434f8bb] Sep 28 16:07:30 fedora gnome-shell[9533]: (EE) 9: /usr/bin/Xwayland (0x5655542ed000+0x63ab2) [0x565554350ab2] Sep 28 16:07:30 fedora gnome-shell[9533]: (EE) 10: /usr/bin/Xwayland (0x5655542ed000+0xf7fd0) [0x5655543e4fd0] Sep 28 16:07:30 fedora gnome-shell[9533]: (EE) 11: /usr/bin/Xwayland (0x5655542ed000+0xe183a) [0x5655543ce83a] Sep 28 16:07:30 fedora gnome-shell[9533]: (EE) 12: /usr/bin/Xwayland (0x5655542ed000+0xe16d8) [0x5655543ce6d8] Sep 28 16:07:30 fedora gnome-shell[9533]: (EE) 13: /usr/bin/Xwayland (0x5655542ed000+0xe16d8) [0x5655543ce6d8] Sep 28 16:07:30 fedora gnome-shell[9533]: (EE) 14: /usr/bin/Xwayland (0x5655542ed000+0xda2dc) [0x5655543c72dc] Sep 28 16:07:30 fedora gnome-shell[9533]: (EE) 15: /usr/bin/Xwayland (0x5655542ed000+0xaab3f) [0x565554397b3f] Sep 28 16:07:30 fedora gnome-shell[9533]: (EE) 16: /usr/bin/Xwayland (0x5655542ed000+0x38bd1) [0x565554325bd1] Sep 28 16:07:30 fedora gnome-shell[9533]: (EE) 17: /lib64/libc.so.6 (0x7fd6c3e75000+0x23510) [0x7fd6c3e98510] Sep 28 16:07:30 fedora gnome-shell[9533]: (EE) 18: /lib64/libc.so.6 (__libc_start_main+0x89) [0x7fd6c3e985c9] Sep 28 16:07:30 fedora gnome-shell[9533]: (EE) 19: /usr/bin/Xwayland (0x5655542ed000+0x3a3f5) [0x5655543273f5] Sep 28 16:07:30 fedora gnome-shell[9533]: (EE) Sep 28 16:07:30 fedora gnome-shell[9533]: amdgpu: Failed to allocate a buffer: Sep 28 16:07:30 fedora gnome-shell[9533]: amdgpu: size : 37683200 bytes Sep 28 16:07:30 fedora gnome-shell[9533]: amdgpu: alignment : 2097152 bytes Sep 28 16:07:30 fedora gnome-shell[9533]: amdgpu: domains : 4 Sep 28 16:07:30 fedora gnome-shell[9533]: amdgpu: flags : 6 dmesg: [ 143.221178] code: page allocation failure: order:0, mode:0x104dc4(GFP_USER|GFP_DMA32|__GFP_RETRY_MAYFAIL|__GFP_ZERO), nodemask=(null),cpuset=user.slice,mems_allowed=0 [ 143.221189] CPU: 1 PID: 9613 Comm: code Not tainted 5.19.11-300.fc37.x86_64 #1 [ 143.221192] Hardware name: LENOVO 21D4000HUS/21D4000HUS, BIOS N3GET42W (1.22 ) 09/06/2022 [ 143.221193] Call Trace: [ 143.221196] <TASK> [ 143.221201] dump_stack_lvl+0x44/0x5c [ 143.221206] warn_alloc+0xfb/0x120 [ 143.221210] ? psi_task_change+0x85/0x110 [ 143.221214] __alloc_pages_slowpath.constprop.0+0xcfe/0xd60 [ 143.221217] __alloc_pages+0x201/0x220 [ 143.221220] ttm_pool_alloc+0x2af/0x5a0 [ttm] [ 143.221227] amdgpu_ttm_tt_populate+0x35/0x90 [amdgpu] [ 143.221327] ttm_tt_populate+0x9d/0x140 [ttm] [ 143.221330] ttm_bo_handle_move_mem+0x1ac/0x1c0 [ttm] [ 143.221334] ttm_bo_validate+0xb5/0xf0 [ttm] [ 143.221337] ? drm_vma_offset_add+0x59/0x60 [ 143.221340] ? drm_vma_offset_add+0x2f/0x60 [ 143.221342] ttm_bo_init_reserved+0x178/0x250 [ttm] [ 143.221345] amdgpu_bo_create+0x1b2/0x460 [amdgpu] [ 143.221421] ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu] [ 143.221495] ? unix_stream_recvmsg+0x68/0x80 [ 143.221499] amdgpu_bo_create_user+0x24/0x40 [amdgpu] [ 143.221576] amdgpu_gem_create_ioctl+0x121/0x360 [amdgpu] [ 143.221652] ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu] [ 143.221727] ? amdgpu_gem_force_release+0x130/0x130 [amdgpu] [ 143.221802] drm_ioctl_kernel+0xa1/0x150 [ 143.221807] drm_ioctl+0x21f/0x420 [ 143.221809] ? amdgpu_gem_force_release+0x130/0x130 [amdgpu] [ 143.221884] ? ioctl_has_perm.constprop.0.isra.0+0xaa/0xf0 [ 143.221887] ? ktime_get_ts64+0x4c/0xf0 [ 143.221891] amdgpu_drm_ioctl+0x4a/0x80 [amdgpu] [ 143.221964] __x64_sys_ioctl+0x90/0xd0 [ 143.221968] do_syscall_64+0x5b/0x80 [ 143.221971] ? syscall_exit_to_user_mode+0x17/0x40 [ 143.221973] ? do_syscall_64+0x67/0x80 [ 143.221974] ? syscall_exit_to_user_mode+0x17/0x40 [ 143.221976] ? do_syscall_64+0x67/0x80 [ 143.221977] ? syscall_exit_to_user_mode+0x17/0x40 [ 143.221979] ? do_syscall_64+0x67/0x80 [ 143.221980] ? syscall_exit_to_user_mode+0x17/0x40 [ 143.221981] ? do_syscall_64+0x67/0x80 [ 143.221983] entry_SYSCALL_64_after_hwframe+0x63/0xcd [ 143.221986] RIP: 0033:0x7fe50730a87f [ 143.222023] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00 [ 143.222024] RSP: 002b:00007ffc99411fc0 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 [ 143.222026] RAX: ffffffffffffffda RBX: 000039e003da3700 RCX: 00007fe50730a87f [ 143.222027] RDX: 00007ffc99412060 RSI: 00000000c0206440 RDI: 0000000000000017 [ 143.222028] RBP: 00007ffc99412060 R08: 000039e003da3700 R09: 00000000000000a0 [ 143.222029] R10: 000039e000265a08 R11: 0000000000000246 R12: 00000000c0206440 [ 143.222029] R13: 0000000000000017 R14: 000000000087e000 R15: 0000000000000013 [ 143.222033] </TASK> [ 143.222034] Mem-Info: [ 143.222036] active_anon:3974 inactive_anon:1176507 isolated_anon:0 active_file:367429 inactive_file:1097328 isolated_file:0 unevictable:1768 dirty:387 writeback:0 slab_reclaimable:47631 slab_unreclaimable:73611 mapped:391973 shmem:22515 pagetables:30639 bounce:0 kernel_misc_reclaimable:0 free:4682330 free_pcp:56 free_cma:0 [ 143.222039] Node 0 active_anon:15896kB inactive_anon:4706028kB active_file:1469716kB inactive_file:4389312kB unevictable:7072kB isolated(anon):0kB isolated(file):0kB mapped:1567892kB dirty:1548kB writeback:0kB shmem:90060kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 2048kB writeback_tmp:0kB kernel_stack:50256kB pagetables:122556kB all_unreclaimable? no [ 143.222043] Node 0 DMA free:6880kB boost:0kB min:32kB low:44kB high:56kB reserved_highatomic:0KB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB writepending:0kB present:15996kB managed:15360kB mlocked:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB [ 143.222046] lowmem_reserve[]: 0 1713 31287 31287 31287 [ 143.222049] Node 0 DMA32 free:3556kB boost:0kB min:3696kB low:5448kB high:7200kB reserved_highatomic:0KB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB writepending:0kB present:1869324kB managed:1801348kB mlocked:0kB bounce:0kB free_pcp:224kB local_pcp:0kB free_cma:0kB [ 143.222051] lowmem_reserve[]: 0 0 29574 29574 29574 [ 143.222054] Node 0 Normal free:18718884kB boost:0kB min:63852kB low:94132kB high:124412kB reserved_highatomic:0KB active_anon:15896kB inactive_anon:4706028kB active_file:1469716kB inactive_file:4389312kB unevictable:7072kB writepending:1548kB present:30903296kB managed:30291884kB mlocked:7072kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB [ 143.222057] lowmem_reserve[]: 0 0 0 0 0 [ 143.222059] Node 0 DMA: 0*4kB 0*8kB 0*16kB 1*32kB (U) 1*64kB (U) 1*128kB (U) 0*256kB 1*512kB (U) 0*1024kB 1*2048kB (M) 1*4096kB (M) = 6880kB [ 143.222105] Node 0 DMA32: 29*4kB (U) 62*8kB (U) 0*16kB 0*32kB 0*64kB 1*128kB (U) 1*256kB (U) 1*512kB (U) 0*1024kB 1*2048kB (U) 0*4096kB = 3556kB [ 143.222115] Node 0 Normal: 9843*4kB (UME) 8861*8kB (UME) 2839*16kB (UME) 1770*32kB (UME) 835*64kB (UME) 420*128kB (UME) 214*256kB (UME) 71*512kB (ME) 36*1024kB (UME) 14*2048kB (UME) 4454*4096kB (ME) = 18719780kB [ 143.222124] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=1048576kB [ 143.222125] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=2048kB [ 143.222126] 1215680 total pagecache pages [ 143.222127] 0 pages in swap cache [ 143.222127] Swap cache stats: add 0, delete 0, find 0/0 [ 143.222128] Free swap = 8388604kB [ 143.222129] Total swap = 8388604kB [ 143.222129] 8197154 pages RAM [ 143.222130] 0 pages HighMem/MovableOnly [ 143.222130] 170006 pages reserved [ 143.222131] 0 pages cma reserved [ 143.222131] 0 pages hwpoisoned [ 143.292958] amdgpu 0000:67:00.0: amdgpu: 000000009d692800 pin failed [ 143.292964] [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -12 [ 143.396867] amdgpu 0000:67:00.0: amdgpu: 00000000d10f4251 pin failed [ 143.396873] [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -12

3 4

Fedora 37 CoreOS Test Week is happening NOW!
by Sumantro Mukherjee 01 Oct '22

01 Oct '22

Hey Folks, F37 CoreOS Test week starts today and will run for a week! As most of you might know, CoreOS will come forth in this cycle as an "Edition". This opens us with more requirements for testing and ironing out bugs well ahead of time. This test week aims to serve community members an opportunity to get together and explore everything from the FCOS itself to the documentation! The wiki[0] has the details, all that's required to be known. The test day app[1] is where the testers can submit the test results. [0] https://fedoraproject.org/wiki/Test_Day:Fedora_37_CoreOS_2022-09-29 [1] https://testdays.fedoraproject.org/events/143 Thanks -- //sumantro Fedora QE TRIED AND PERSONALLY TESTED, ERGO TRUSTED

2 1

Release criteria proposal: except BitLocker-enabled installs from Windows dual-boot criterion bootloader requirement
by Adam Williamson 30 Sep '22

30 Sep '22

For background here, see: https://bugzilla.redhat.com/show_bug.cgi?id=2049849 right now, when installing Fedora alongside a Windows install with BitLocker enabled, trying to boot Windows from the Fedora boot menu does not work. We waived the bug as a blocker for Fedora 36 on the basis upstream did not consider it fixable within the F36 timeframe. We agreed that if upstream still couldn't get this fixed for F37, we'd consider revising the criteria. Well, we're approaching F37 Final and the bug is still open, and there's no appreciable movement upstream, so I'm proposing the criteria change. I propose we change this: "The installer must be able to install into free space alongside an existing clean Windows installation and install a bootloader which can boot into both Windows and Fedora." to say: "The installer must be able to install into free space alongside an existing clean Windows installation. As long as the Windows installation does not have BitLocker enabled, the installer must also install a bootloader which can boot into both Windows and Fedora." -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net

3 3

F37 Beta Cannot Install KODI
by Earnest Henderson 30 Sep '22

30 Sep '22

I have a clean install of Fedora 37 beta on a desktop (not a VM). When I try to install kodi (from rpmfusion-free) I encounter a conflict with firewalld: Error: Transaction test error: file /usr/lib/firewalld/services/kodi-eventserver.xml from install of kodi-firewalld-19.4-4.fc37.x86_64 conflicts with file from package firewalld-1.2.0-3.fc37.noarch This was reported a few months ago on Arch linux and a bug was filed against firewalld as both were trying to provide the same file. According to github, the firewalld update was reverted back in July: https://github.com/firewalld/firewalld/pull/1002 Apparently that has not made it into Fedora 37 yet? I have all updates installed as of 23 September. I'd appreciate any advice. Thanks

4 5

ssh rsa key - Bad server host key: Invalid key length
by Carlos Martinez 29 Sep '22

29 Sep '22

After updating to Fedora 37 beta, I was not able to login to a device that uses rsa to authenticate anymore. The message shown is: "Bad server host key: Invalid key length" [jcm@fedora ~]$ ssh sysadmin(a)192.168.225.130 -vvvv OpenSSH_8.8p1, OpenSSL 3.0.5 5 Jul 2022 debug1: Reading configuration data /etc/ssh/ssh_config debug3: /etc/ssh/ssh_config line 55: Including file /etc/ssh/ssh_config.d/50-redhat.conf depth 0 debug1: Reading configuration data /etc/ssh/ssh_config.d/50-redhat.conf debug2: checking match for 'final all' host 192.168.225.130 originally 192.168.225.130 debug3: /etc/ssh/ssh_config.d/50-redhat.conf line 3: not matched 'final' debug2: match not found debug3: /etc/ssh/ssh_config.d/50-redhat.conf line 5: Including file /etc/crypto-policies/back-ends/openssh.config depth 1 (parse only) debug1: Reading configuration data /etc/crypto-policies/back-ends/openssh.config debug3: gss kex names ok: [gss-curve25519-sha256-,gss-nistp256-sha256-,gss-group14-sha256-,gss-group16-sha512-] debug3: kex names ok: [curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512] debug1: configuration requests final Match pass debug2: resolve_canonicalize: hostname 192.168.225.130 is address debug1: re-parsing configuration debug1: Reading configuration data /etc/ssh/ssh_config debug3: /etc/ssh/ssh_config line 55: Including file /etc/ssh/ssh_config.d/50-redhat.conf depth 0 debug1: Reading configuration data /etc/ssh/ssh_config.d/50-redhat.conf debug2: checking match for 'final all' host 192.168.225.130 originally 192.168.225.130 debug3: /etc/ssh/ssh_config.d/50-redhat.conf line 3: matched 'final' debug2: match found debug3: /etc/ssh/ssh_config.d/50-redhat.conf line 5: Including file /etc/crypto-policies/back-ends/openssh.config depth 1 debug1: Reading configuration data /etc/crypto-policies/back-ends/openssh.config debug3: gss kex names ok: [gss-curve25519-sha256-,gss-nistp256-sha256-,gss-group14-sha256-,gss-group16-sha512-] debug3: kex names ok: [curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512] debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts' -> '/home/jcm/.ssh/known_hosts' debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts2' -> '/home/jcm/.ssh/known_hosts2' debug3: ssh_connect_direct: entering debug1: Connecting to 192.168.225.130 [192.168.225.130] port 22. debug3: set_sock_tos: set socket 3 IP_TOS 0x48 debug1: Connection established. debug1: identity file /home/jcm/.ssh/id_rsa type -1 debug1: identity file /home/jcm/.ssh/id_rsa-cert type -1 debug1: identity file /home/jcm/.ssh/id_dsa type -1 debug1: identity file /home/jcm/.ssh/id_dsa-cert type -1 debug1: identity file /home/jcm/.ssh/id_ecdsa type -1 debug1: identity file /home/jcm/.ssh/id_ecdsa-cert type -1 debug1: identity file /home/jcm/.ssh/id_ecdsa_sk type -1 debug1: identity file /home/jcm/.ssh/id_ecdsa_sk-cert type -1 debug1: identity file /home/jcm/.ssh/id_ed25519 type -1 debug1: identity file /home/jcm/.ssh/id_ed25519-cert type -1 debug1: identity file /home/jcm/.ssh/id_ed25519_sk type -1 debug1: identity file /home/jcm/.ssh/id_ed25519_sk-cert type -1 debug1: identity file /home/jcm/.ssh/id_xmss type -1 debug1: identity file /home/jcm/.ssh/id_xmss-cert type -1 debug1: Local version string SSH-2.0-OpenSSH_8.8 debug1: Remote protocol version 2.0, remote software version dropbear_2022.82 debug1: compat_banner: no match: dropbear_2022.82 debug2: fd 3 setting O_NONBLOCK debug1: Authenticating to 192.168.225.130:22 as 'sysadmin' debug1: load_hostkeys: fopen /home/jcm/.ssh/known_hosts2: No such file or directory debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory debug3: order_hostkeyalgs: no algorithms matched; accept original debug3: send packet: type 20 debug1: SSH2_MSG_KEXINIT sent debug3: receive packet: type 20 debug1: SSH2_MSG_KEXINIT received debug2: local client KEXINIT proposal debug2: KEX algorithms: curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,ext-info-c debug2: host key algorithms: ssh-ed25519-cert-v01@openssh.com,ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,sk-ssh-ed25519-cert-v01@openssh.com,sk-ecdsa-sha2-nistp256-cert-v01@openssh.com,rsa-sha2-512-cert-v01@openssh.com,rsa-sha2-256-cert-v01@openssh.com,ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,sk-ssh-ed25519@openssh.com,sk-ecdsa-sha2-nistp256@openssh.com,rsa-sha2-512,rsa-sha2-256 debug2: ciphers ctos: aes256-gcm@openssh.com,chacha20-poly1305@openssh.com,aes256-ctr,aes128-gcm@openssh.com,aes128-ctr debug2: ciphers stoc: aes256-gcm@openssh.com,chacha20-poly1305@openssh.com,aes256-ctr,aes128-gcm@openssh.com,aes128-ctr debug2: MACs ctos: hmac-sha2-256-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha2-256,hmac-sha1,umac-128@openssh.com,hmac-sha2-512 debug2: MACs stoc: hmac-sha2-256-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha2-256,hmac-sha1,umac-128@openssh.com,hmac-sha2-512 debug2: compression ctos: none,zlib(a)openssh.com,zlib debug2: compression stoc: none,zlib(a)openssh.com,zlib debug2: languages ctos: debug2: languages stoc: debug2: first_kex_follows 0 debug2: reserved 0 debug2: peer server KEXINIT proposal debug2: KEX algorithms: curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp521,ecdh-sha2-nistp384,ecdh-sha2-nistp256,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1,kexguess2@matt.ucc.asn.au debug2: host key algorithms: rsa-sha2-256,ssh-rsa,ssh-dss debug2: ciphers ctos: chacha20-poly1305(a)openssh.com,aes128-ctr,aes256-ctr debug2: ciphers stoc: chacha20-poly1305(a)openssh.com,aes128-ctr,aes256-ctr debug2: MACs ctos: hmac-sha1,hmac-sha2-256 debug2: MACs stoc: hmac-sha1,hmac-sha2-256 debug2: compression ctos: zlib(a)openssh.com,none debug2: compression stoc: zlib(a)openssh.com,none debug2: languages ctos: debug2: languages stoc: debug2: first_kex_follows 0 debug2: reserved 0 debug1: kex: algorithm: curve25519-sha256 debug1: kex: host key algorithm: rsa-sha2-256 debug1: kex: server->client cipher: chacha20-poly1305(a)openssh.com MAC: <implicit> compression: none debug1: kex: client->server cipher: chacha20-poly1305(a)openssh.com MAC: <implicit> compression: none debug1: kex: curve25519-sha256 need=64 dh_need=64 debug1: kex: curve25519-sha256 need=64 dh_need=64 debug3: send packet: type 30 debug1: expecting SSH2_MSG_KEX_ECDH_REPLY debug3: receive packet: type 31 debug1: SSH2_MSG_KEX_ECDH_REPLY received Bad server host key: Invalid key length When trying with another edge distro like opensuse tumbleweed, I get OpenSSH_8.9p1, OpenSSL 1.1.1q 5 Jul 2022 debug1: Reading configuration data /usr/etc/ssh/ssh_config debug1: /usr/etc/ssh/ssh_config line 24: include /etc/ssh/ssh_config.d/*.conf matched no files debug1: /usr/etc/ssh/ssh_config line 25: include /usr/etc/ssh/ssh_config.d/*.conf matched no files debug1: /usr/etc/ssh/ssh_config line 27: Applying options for * debug2: resolve_canonicalize: hostname 192.168.225.130 is address debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts' -> '/home/carlos/.ssh/known_hosts' debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts2' -> '/home/carlos/.ssh/known_hosts2' debug3: ssh_connect_direct: entering debug1: Connecting to 192.168.225.130 [192.168.225.130] port 22. debug3: set_sock_tos: set socket 3 IP_TOS 0x10 debug1: Connection established. debug1: identity file /home/carlos/.ssh/id_rsa type -1 debug1: identity file /home/carlos/.ssh/id_rsa-cert type -1 debug1: identity file /home/carlos/.ssh/id_ecdsa type -1 debug1: identity file /home/carlos/.ssh/id_ecdsa-cert type -1 debug1: identity file /home/carlos/.ssh/id_ecdsa_sk type -1 debug1: identity file /home/carlos/.ssh/id_ecdsa_sk-cert type -1 debug1: identity file /home/carlos/.ssh/id_ed25519 type -1 debug1: identity file /home/carlos/.ssh/id_ed25519-cert type -1 debug1: identity file /home/carlos/.ssh/id_ed25519_sk type -1 debug1: identity file /home/carlos/.ssh/id_ed25519_sk-cert type -1 debug1: identity file /home/carlos/.ssh/id_xmss type -1 debug1: identity file /home/carlos/.ssh/id_xmss-cert type -1 debug1: identity file /home/carlos/.ssh/id_dsa type -1 debug1: identity file /home/carlos/.ssh/id_dsa-cert type -1 debug1: Local version string SSH-2.0-OpenSSH_8.9 debug1: Remote protocol version 2.0, remote software version dropbear_2022.82 debug1: compat_banner: no match: dropbear_2022.82 debug2: fd 3 setting O_NONBLOCK debug1: Authenticating to 192.168.225.130:22 as 'sysadmin' debug3: record_hostkey: found key type RSA in file /home/carlos/.ssh/known_hosts:1 debug3: load_hostkeys_file: loaded 1 keys from 192.168.225.130 debug1: load_hostkeys: fopen /home/carlos/.ssh/known_hosts2: No such file or directory debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory debug3: order_hostkeyalgs: prefer hostkeyalgs: rsa-sha2-512-cert-v01@openssh.com,rsa-sha2-256-cert-v01@openssh.com,rsa-sha2-512,rsa-sha2-256 debug3: send packet: type 20 debug1: SSH2_MSG_KEXINIT sent debug3: receive packet: type 20 debug1: SSH2_MSG_KEXINIT received debug2: local client KEXINIT proposal debug2: KEX algorithms: curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,sntrup761x25519-sha512@openssh.com,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1,ext-info-c debug2: host key algorithms: rsa-sha2-512-cert-v01@openssh.com,rsa-sha2-256-cert-v01@openssh.com,rsa-sha2-512,rsa-sha2-256,ssh-ed25519-cert-v01@openssh.com,ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,sk-ssh-ed25519-cert-v01@openssh.com,sk-ecdsa-sha2-nistp256-cert-v01@openssh.com,ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,sk-ssh-ed25519@openssh.com,sk-ecdsa-sha2-nistp256@openssh.com debug2: ciphers ctos: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com debug2: ciphers stoc: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com debug2: MACs ctos: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1 debug2: MACs stoc: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1 debug2: compression ctos: none,zlib(a)openssh.com,zlib debug2: compression stoc: none,zlib(a)openssh.com,zlib debug2: languages ctos: debug2: languages stoc: debug2: first_kex_follows 0 debug2: reserved 0 debug2: peer server KEXINIT proposal debug2: KEX algorithms: curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp521,ecdh-sha2-nistp384,ecdh-sha2-nistp256,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1,kexguess2@matt.ucc.asn.au debug2: host key algorithms: rsa-sha2-256,ssh-rsa,ssh-dss debug2: ciphers ctos: chacha20-poly1305(a)openssh.com,aes128-ctr,aes256-ctr debug2: ciphers stoc: chacha20-poly1305(a)openssh.com,aes128-ctr,aes256-ctr debug2: MACs ctos: hmac-sha1,hmac-sha2-256 debug2: MACs stoc: hmac-sha1,hmac-sha2-256 debug2: compression ctos: zlib(a)openssh.com,none debug2: compression stoc: zlib(a)openssh.com,none debug2: languages ctos: debug2: languages stoc: debug2: first_kex_follows 0 debug2: reserved 0 debug1: kex: algorithm: curve25519-sha256 debug1: kex: host key algorithm: rsa-sha2-256 debug1: kex: server->client cipher: chacha20-poly1305(a)openssh.com MAC: <implicit> compression: none debug1: kex: client->server cipher: chacha20-poly1305(a)openssh.com MAC: <implicit> compression: none debug1: kex: curve25519-sha256 need=64 dh_need=64 debug1: kex: curve25519-sha256 need=64 dh_need=64 debug3: send packet: type 30 debug1: expecting SSH2_MSG_KEX_ECDH_REPLY debug3: receive packet: type 31 debug1: SSH2_MSG_KEX_ECDH_REPLY received debug1: Server host key: ssh-rsa SHA256:oH0saNfFWms66HfgQF/Bn/FazwRdg6AGCFtV6xuL6z8 debug3: record_hostkey: found key type RSA in file /home/carlos/.ssh/known_hosts:1 debug3: load_hostkeys_file: loaded 1 keys from 192.168.225.130 debug1: load_hostkeys: fopen /home/carlos/.ssh/known_hosts2: No such file or directory debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory debug1: Host '192.168.225.130' is known and matches the RSA host key. debug1: Found key in /home/carlos/.ssh/known_hosts:1 debug3: send packet: type 21 debug2: ssh_set_newkeys: mode 1 debug1: rekey out after 134217728 blocks debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug3: receive packet: type 21 debug1: SSH2_MSG_NEWKEYS received debug2: ssh_set_newkeys: mode 0 debug1: rekey in after 134217728 blocks debug1: get_agent_identities: bound agent to hostkey debug1: get_agent_identities: ssh_fetch_identitylist: agent contains no identities debug1: Will attempt key: /home/carlos/.ssh/id_rsa debug1: Will attempt key: /home/carlos/.ssh/id_ecdsa debug1: Will attempt key: /home/carlos/.ssh/id_ecdsa_sk debug1: Will attempt key: /home/carlos/.ssh/id_ed25519 debug1: Will attempt key: /home/carlos/.ssh/id_ed25519_sk debug1: Will attempt key: /home/carlos/.ssh/id_xmss debug1: Will attempt key: /home/carlos/.ssh/id_dsa debug2: pubkey_prepare: done debug3: send packet: type 5 debug3: receive packet: type 7 debug1: SSH2_MSG_EXT_INFO received debug1: kex_input_ext_info: server-sig-algs=<ssh-ed25519,sk-ssh-ed25519@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,sk-ecdsa-sha2-nistp256@openssh.com,rsa-sha2-256,ssh-rsa,ssh-dss> debug3: receive packet: type 6 debug2: service_accept: ssh-userauth debug1: SSH2_MSG_SERVICE_ACCEPT received debug3: send packet: type 50 debug3: receive packet: type 51 debug1: Authentications that can continue: publickey,password debug3: start over, passed a different list publickey,password debug3: preferred publickey,keyboard-interactive,password debug3: authmethod_lookup publickey debug3: remaining preferred: keyboard-interactive,password debug3: authmethod_is_enabled publickey debug1: Next authentication method: publickey debug1: Trying private key: /home/carlos/.ssh/id_rsa debug3: no such identity: /home/carlos/.ssh/id_rsa: No such file or directory debug1: Trying private key: /home/carlos/.ssh/id_ecdsa debug3: no such identity: /home/carlos/.ssh/id_ecdsa: No such file or directory debug1: Trying private key: /home/carlos/.ssh/id_ecdsa_sk debug3: no such identity: /home/carlos/.ssh/id_ecdsa_sk: No such file or directory debug1: Trying private key: /home/carlos/.ssh/id_ed25519 debug3: no such identity: /home/carlos/.ssh/id_ed25519: No such file or directory debug1: Trying private key: /home/carlos/.ssh/id_ed25519_sk debug3: no such identity: /home/carlos/.ssh/id_ed25519_sk: No such file or directory debug1: Trying private key: /home/carlos/.ssh/id_xmss debug3: no such identity: /home/carlos/.ssh/id_xmss: No such file or directory debug1: Trying private key: /home/carlos/.ssh/id_dsa debug3: no such identity: /home/carlos/.ssh/id_dsa: No such file or directory debug2: we did not send a packet, disable method debug3: authmethod_lookup password debug3: remaining preferred: ,password debug3: authmethod_is_enabled password debug1: Next authentication method: password sysadmin(a)192.168.225.130's password: debug3: send packet: type 50 debug2: we sent a password packet, wait for reply debug3: receive packet: type 52 Authenticated to 192.168.225.130 ([192.168.225.130]:22) using "password". debug1: channel 0: new [client-session] debug3: ssh_session2_open: channel_new: 0 debug2: channel 0: send open debug3: send packet: type 90 debug1: Entering interactive session. debug1: pledge: filesystem debug3: receive packet: type 91 debug2: channel_input_open_confirmation: channel 0: callback start debug2: fd 3 setting TCP_NODELAY debug3: set_sock_tos: set socket 3 IP_TOS 0x10 debug2: client_session2_setup: id 0 debug2: channel 0: request pty-req confirm 1 debug3: send packet: type 98 debug1: Sending environment. debug3: Ignored env SHELL debug3: Ignored env SESSION_MANAGER debug3: Ignored env COLORTERM debug3: Ignored env XDG_CONFIG_DIRS debug3: Ignored env LESS debug3: Ignored env XDG_MENU_PREFIX debug3: Ignored env MACHTYPE debug3: Ignored env G_BROKEN_FILENAMES debug3: Ignored env HISTSIZE debug3: Ignored env HOSTNAME debug3: Ignored env FROM_HEADER debug3: Ignored env MINICOM debug3: Ignored env JAVA_ROOT debug3: Ignored env JAVA_HOME debug3: Ignored env AUDIODRIVER debug3: Ignored env JRE_HOME debug3: Ignored env SSH_AUTH_SOCK debug3: Ignored env CPU debug3: Ignored env JAVA_BINDIR debug3: Ignored env DESKTOP_SESSION debug3: Ignored env GPG_TTY debug3: Ignored env PWD debug3: Ignored env QEMU_AUDIO_DRV debug3: Ignored env XDG_SESSION_DESKTOP debug3: Ignored env LOGNAME debug3: Ignored env XDG_SESSION_TYPE debug3: Ignored env MANPATH debug3: Ignored env SYSTEMD_EXEC_PID debug3: Ignored env XAUTHORITY debug3: Ignored env LS_OPTIONS debug3: Ignored env XKEYSYMDB debug3: Ignored env XNLSPATH debug3: Ignored env HOME debug3: Ignored env USERNAME debug1: channel 0: setting env LANG = "en_US.UTF-8" debug2: channel 0: request env confirm 0 debug3: send packet: type 98 debug3: Ignored env LS_COLORS debug3: Ignored env XDG_CURRENT_DESKTOP debug3: Ignored env PYTHONSTARTUP debug3: Ignored env VTE_VERSION debug3: Ignored env WAYLAND_DISPLAY debug3: Ignored env OSTYPE debug3: Ignored env GNOME_TERMINAL_SCREEN debug3: Ignored env LESS_ADVANCED_PREPROCESSOR debug3: Ignored env GNOME_SETUP_DISPLAY debug3: Ignored env LESSCLOSE debug3: Ignored env XDG_SESSION_CLASS debug3: Ignored env TERM debug3: Ignored env G_FILENAME_ENCODING debug3: Ignored env HOST debug3: Ignored env XAUTHLOCALHOSTNAME debug3: Ignored env LESSOPEN debug3: Ignored env USER debug3: Ignored env GNOME_TERMINAL_SERVICE debug3: Ignored env MORE debug3: Ignored env CSHEDIT debug3: Ignored env DISPLAY debug3: Ignored env SHLVL debug3: Ignored env WINDOWMANAGER debug3: Ignored env PAGER debug3: Ignored env XDG_RUNTIME_DIR debug3: Ignored env MANPATHISSET debug3: Ignored env XDG_DATA_DIRS debug3: Ignored env VENDOR debug3: Ignored env PATH debug3: Ignored env GDMSESSION debug3: Ignored env DBUS_SESSION_BUS_ADDRESS debug3: Ignored env PROFILEREAD debug3: Ignored env MAIL debug3: Ignored env HOSTTYPE debug3: Ignored env LESSKEY debug3: Ignored env _ debug3: Ignored env OLDPWD debug2: channel 0: request shell confirm 1 debug3: send packet: type 98 debug2: channel_input_open_confirmation: channel 0: callback done debug2: channel 0: open confirm rwindow 24576 rmax 32759 debug3: receive packet: type 99 debug2: channel_input_status_confirm: type 99 id 0 debug2: PTY allocation request accepted on channel 0 debug3: receive packet: type 99 debug2: channel_input_status_confirm: type 99 id 0 debug2: shell request accepted on channel 0

3 2

2022-09-26 - Fedora QA Meeting - Minutes
by Adam Williamson 27 Sep '22

27 Sep '22

================================== #fedora-meeting: Fedora QA meeting ================================== Meeting started by adamw at 15:01:54 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting/2022-09-26/fedora-qa.2022-… . Meeting summary --------------- * Roll Call (adamw, 15:02:01) * Previous meeting follow-up (adamw, 15:07:41) * "adamw to work on F37 Beta common issues" - did that, I think everything nominated was covered. (adamw, 15:08:37) * Fedora 37 status (adamw, 15:11:28) * LINK: https://gitlab.gnome.org/GNOME/gnome-maps/-/issues/491 (lruzicka, 15:19:19) * Release criteria proposal status (adamw, 15:19:42) * Windows Bitlocker criterion amendment proposal is live, currently doesn't seem to have any opposition (adamw, 15:35:02) * ACTION: adamw to activate the Bitlocker amendment this week if nobody pops up to oppose it (adamw, 15:35:15) * the GNOME Shell extension criterion proposal was not supported by the desktop team, so I'm considering that dropped for now (adamw, 15:35:44) * Test Day / community event status (adamw, 15:41:16) * LINK: https://testdays.fedoraproject.org/events/142 (coremodule, 15:42:22) * IoT Test Day went off last week: https://testdays.fedoraproject.org/events/142 (adamw, 15:42:52) * test day publicity was lacking lately as sumantro was out sick and we missed arranging cover, apologies for that (adamw, 15:51:16) * CoreOS and upgrade test days are coming soon (adamw, 15:53:42) * Open floor (adamw, 15:53:47) Meeting ended at 15:57:42 UTC. Action Items ------------ * adamw to activate the Bitlocker amendment this week if nobody pops up to oppose it Action Items, by person ----------------------- * adamw * adamw to activate the Bitlocker amendment this week if nobody pops up to oppose it * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * adamw (41) * zodbot (16) * tablepc_ (16) * bcotton (7) * lruzicka (7) * coremodule (6) * SumantroMukherje (5) * kparal (4) * Southern_Gentlem (2) * pboy (1) Generated by `MeetBot`_ 0.4 .. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

test September 2022