#fedora-meeting: Fedora QA meeting
Meeting started by adamw at 15:01:54 UTC. The full logs are available at
* 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
* 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,
* Test Day / community event status (adamw, 15:41:16)
* LINK: https://testdays.fedoraproject.org/events/142 (coremodule,
* 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.
* adamw to activate the Bitlocker amendment this week if nobody pops up
to oppose it
Action Items, by person
* adamw to activate the Bitlocker amendment this week if nobody pops
up to oppose it
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
IRC: adamw | Twitter: adamw_ha
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.
Completely randomly, my laptop sometimes emits a loud PC speaker beep while
rebooting/powering off Fedora 37. The beep is very strong, and as a PC
speaker sound, it of course ignores any configured volume level, mute
status, and even headphones plugged in. I fortunately am in a different
room than the rest of my family sleeps in, but if I were in the same room,
and were I just a regular user, this would probably be the last day of
Fedora on that laptop. The beep is that loud and uncomfortable, especially
I wonder if somebody else running F37 noticed it as well? Any hints what
might cause it and how we can fix it? It never happened on F36 on the same
After upgrading from Fedora 36 testing to Fedora 37 testing the following first glance issues appeared:
Display: The desktop wallpaper was lost; monitor refresh rate had to be readjusted.
Nautilus (43.0-1.fc37): Column settings were lost; there seems to be a scrolling issue; the star column can´t be hidden with the "visible columns" menu.
I wonder if I'm the only one who sees an occasional gnome-shell crash on
Fedora 37 when the system is resumed from suspend, or possibly even woken
up from idle (screen turned off)? It happens to me a few times per week,
completely randomly, I can't reproduce it intentionally.
I reported the crash here:
And this might be the upstream issue:
It might be caused by gnome-shell-extension-appindicator-42-3.fc37.noarch,
but given how seldomly it happens, it's hard for me to verify that.
I'm running an actual install of F37. I have had this experience twice
now. I run the updates in a virtual console using dnf, they
complete successfully, they have a firmware package among the updates.
I then start X to run LXDE, and it starts without complaint. But when
I try to run either nightly from /usr/local or firefox from /usr/bin in
a terminal, they start and just hang. There are no messages in the
journal or in the terminal, and when I look at them using ps they are
in interruptable sleep.
In both cases, I killed them, and exited X, restarted X, and tried to
run them again. No change. But, when I reboot the computer,
everything starts working again the way I would expect; firefox starts.
Is this a change in F37 that requires a reboot after the install of
firmware packages? I know that Gnome, and I think KDE, now require a
reboot after every update. Has it moved to other desktops? Can I
turn it off, if it has? Is there a command I can run from the command
line to do the equivalent of a reboot? Or is it all just coincidence,
and there is another reason?
When trying to upgrade to Fedora 37 Beta with the system-upgrade Plugin like so:
sudo dnf system-upgrade download --releasever=37
I get the following error:
Error: Transaction test error:
file /usr/bin/WebKitWebDriver from install of webkit2gtk4.1-2.37.91-1.fc37.x86_64 conflicts with file from package webkit2gtk3-2.38.0-2.fc36.x86_64
file /usr/bin/WebKitWebDriver from install of webkit2gtk5.0-2.37.91-1.fc37.x86_64 conflicts with file from package webkit2gtk3-2.38.0-2.fc36.x86_64
Fedora Linux 37 Final freeze begins Tuesday 4 October.
1. anaconda — Custom partitioning with 2 drives selected, bootloader
fails to install due to one drive not having a BIOS Boot partition —
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 —
ACTION: dgilmore to test
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
6. gnome-software — Can't install a local rpm package anymore, Install
button missing (for certain RPMs) — VERIFIED
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
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
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.
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
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
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.
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
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:
He / Him / His
Fedora Program Manager
Just a quick heads up that the GNOME 43.0 final release megaupdate is
now in F37 updates-testing:
This is the GNOME version that's we'll be shipping F37 Final with, so
please make sure to test it and file issues for things that would need
fixing before F37 GA. I'd suggest starting upstream at gitlab.gnome.org
for most issues, and then letting me (and other people) know in
#fedora-workstation if anything needs backporting to Fedora (since there
won't be any more upstream releases before F37 Final). If anything looks
to be release blockery, then please also file issues downstream at
bugzilla.redhat.com as soon as possible and mark them as blockers using
the blockerbugs page,
At the same time, please don't block the update with -1 karma unless
there's something really amiss: We need the megaupdate to go stable and
we can iterate from there.
It all passed my own smoke testing and things were calm upstream and
it's mostly just bug fixes at this point, compared to 43.rc.
Thanks everybody and let's make this a good release!