Comments
pjones wrote:
"I honestly don't think anyone has been using it - or that it has even worked in several years."
Neither of those statements are true.
"I honestly don't think anyone has been using it"
That is not true, I still have at least a dozen x86_64 devices which boot with a 32 bit UEFI. And as the person who has been doing most of the kernel side hw-enablement for Intel Bay Trail systems which typically ship with a 32 bit UEFI firmware I can tell you that I still regularly get inquires, bug reports and regression reports about these systems. These systems not only include many smaller laptops (the last generation where 10" laptops where common which some people like) but also various top-set-boxes / NUC style devices used for things like pihole setups and home assistant setups. IOW quite a few people are still using this.
"or that it has even worked in several years."
Again this is also simply not true. I just booted a F43 workstation liveusb on an Asus T100TA (which still is a very popular mini laptop) which has 32 bit UEFI and it boots just fine. So shim-ia32 was working fine until it was disabled.
Please re-enable the shim-ia32 builds and after that we will need to undo all the changes to the various x86_64 compose which were made because of this being disabled out of the blue.
If you insist on disabling shim-ia32 builds for F44 then IMHO you MUST create a change proposal for F44 for this as this will drop support for a whole bunch of hardware which still works fine in F43.
Thanks I can confirm that this release fixes BZ#2158627
Was the split of the linux-firmware package not supposed to be a Fedora 37 feature? Since this is breaking peoples system left and right IMHO a new update reverting the split should be pushed for F36 and this should be made a F37 only thing? :
https://fedoraproject.org/wiki/Changes/Linux_Firmware_Minimization
For examples of the issues caused by this see:
https://bugzilla.redhat.com/show_bug.cgi?id=2125536 https://bugzilla.redhat.com/show_bug.cgi?id=2125774
Thanks, I've tested this and I can confirm that this fixes bug 1945585
jwrdegoede
commented & provided feedback
on gnome-shell-extension-topicons-plus-27-6.20210319.295026a.fc34
4 years ago
I can confirm that this fixes the TopIcons extension with GNOME40.
I can confirm that this fixes bug 1856399 and everything else seems to work fine too.
This breaks deps for funguloids and cegui-ogre-renderer.
Please unpush this and don't push the Fedora 33 until these issues are resolved (and in that case include the fixed packages in the new update).
Works for me and this fixes the cursor being 90 degrees rotated on devices with a non upright (90 degree rotated) mounted panel. This also fixes the cursor hotspot being wrong inside virtual-machines.
This fixes build failures on F32 for me.
I can confirm that this fixes the audio issues I was seeing on devices using Intel SST audio.
I can confirm that this fixes the audio issues I was seeing on devices using Intel SST audio.
devil24g, I've added your comment to: https://bugzilla.redhat.com/show_bug.cgi?id=1667014
Lets discuss this further there.
I can confirm that this fixes the crash when trying to play a recording.
I can confirm that the 1.12.6-3 build fixes wifi no longer working on a device with a brcmfmac43241b4-sdio nic.
This update breaks wifi for me too, same "missing credentials" error as andilinux. This is with a brcmfmac43241b4 card. I've filed a bug with logs here: https://bugzilla.redhat.com/show_bug.cgi?id=1656157
Works for me and fixes the Xorg crashes, +1
An update fixing gstreamer1-plugins-bad-free, which is the package which a bunch of others depends on is available here: FEDORA-2018-cfa159de56
I've rebuild of other (leaf) packages depending on soundtouch pending and I will create a separate update for those.
This fixed the dependency issues I caused for F27 (so sorry about that), +1
About pushing this to stable, I've deliberately disabled auto-pushing to get more testing done before pushing this to stable.
Lets wait about 1 more week for people to get back from holidays and if there are no regression reports in a week then push it to stable.