To expose the various capabilities via vaapi for encode/decode - fedora strips patent encumbered bits from mesa by default. IME people forget to run the dnf swap bits after adding rpmfusion .
You can check what is exposed by installing libva-utils and running vainfo.
The xz vulnerability was fixed a while ago. BUTā¦ There are some zero-day security vulnerabilities on other packages. It happens! They are already fixed in our package repos, but the fixes are not on the install images. Make sure to promptly upgrade after a fresh F40 install.
Anybody seeing the fingerprint reader stop working after update? My machine seems otherwise fine, and the fingerprint reader worked fine under Fedora 39. But now, no dice. I also tried deleting my saved fingerprints and re-registering them, but it doesnāt even detect my finger now.
Note: fwupdmgr sees my finger print reader, and its version is the correct one:
Iāve tried the usual rebooting, as well as full power off and restart. Gnome fingerprint enrollment shows the enrollment UI, but when it asks me to touch the sensor, it doesnāt detect my fingerprint, it just waits.
Hi, I updated my Framework 13 Intel 12Gen from Fedora 39 to 40 (Gnome) a few minutes back and I noticed, that I can`t play sound anymore. When I use the speaker keys (F1 to F3), it shows that hdmi/display port is the output.
Firefox crashes constantly and I canāt play music or videos o_O
I briefly had some issues with sound when I booted into F40 for the first time, but that seemed to be more of an issue with the default audio output being changed. I changed that back in the settings panel and audio started working normally again. Iām running F40 now on a custom desktop (amd cpu + gpu) as well as my Framework 13 AMD laptop. There may be some hints to the problem in your journalctl.
Sounds like youāll have to reset your fingerprint scanner.
The symptoms sound identical to the Windows-Linux dual boot issue. Instructions can be found in that thread!
After the update to Fedora 40 all sound devices didnāt work anymore for my Framework. It turns out, that the format of the wireplumber-config-file has changed (I didnāt run rpmconf after the update ).
I deleted the wireplumber.conf, selected the audio device in the Gnome settings and everything works and sounds fine : sudo rm /etc/wireplumber/wireplumber.conf
I searched and found some threads on this issue, and in the end, while none of the python scripts to reset my fingerprint storage worked (nor did the app-image) I think that running fprintd-delete $USER (which I think achieved nothing, as the command line output said there were no enrolled prints) and then manually re-enrolling on the command line seems to have worked.
If upgrading from Fedora 39, we recommend backing up your home directory and doing a clean installation.
I wonder why this recommendation to do clean install exists here. Fedora is known for quite reliable update between major releases. Are there any particular risks/known issues on FW HW ? On all of my PCs and laptops upgrades were smooth almost ~100% so far.
Iām also experiencing this. Pressing the brightness keys, or Fn + brightness keys, or the brightness keys on my Apple Magic Keyboard 2 always triggers the corresponding function key.
Otherwise, the upgrade has been fairly smooth on my 12th gen Intel Framework 13.
Before the upgrade, in the Software app in the box that said āFedora Linux 40 availableā, when I clicked āRestart & upgradeā, I got a warning dialog saying that blender was incompatible. When I clicked the āremoveā button in the dialog, Software showed a toast saying āThere was a problemā and then when the system restarted, the update didnāt begin.
I had to manually uninstall blender from Software and then press āRestart & upgradeā again for the update to start.
Back up your data before performing a system-wide upgrade as every system upgrade is potentially risky. As a precaution, download the Fedora Workstation Live image in the event something goes wrong.
A system-wide upgrade is fundamentally a risky proposition compared to a clean install.
If it helps, I upgraded from 39 to 40 by following the official upgrade guide. I didnāt run into any issues. However, with the optional post-upgrade steps, the process is quiet a bit of work (and I got confused on the BIOS update step). A clean install could be easier for many users in comparison.
I personally always upgrade, but I also always have my data backed up in case something goes wrong. Irrespective of whether you choose a clean install or an upgrade, please be sure to have a backup before you begin (in case something goes wrong).
I have my systemd-homed managed home dir on 1TB Frameworkās module. I also have a user on internal disk for admin purposes. Before upgrading Iāll remove external 1TB module and Iāll run update with that another admin user. This should be safe enough as I havenāt customized my install, just added proper SELinux for homed. This should survive the upgrade. If the upgrade is successful, Iāll plug 1TB module back to my laptop and should be able to log in to my homed managed user normally.
As I couldnāt hear any specific upgrade issues or conditions to avoid, Iāll proceed with upgrading it and not doing clean install.
.
).
: