The beta release for Fedora Linux 42 is here. Read the release announcement on Fedora Magazine, and make sure to check out F42 Common Issues. If you run into any problems, or have any questions, just Ask Fedora!
16 Likes
Is there a WSL2 image and instructions for beta testing?
Only getting “404 Not Found” errors here in Europe, Matthew @mattdm , apparently one or more mirrors are not cooperating..: https://mirror.theory7.net/fedora/…
Sorry if I’m missing the obvious but I can’t seem to find the link to download the Cosmic Spin beta? Just downloaded the KDE beta.
It doesn’t look like it exists yet. However, the compose group appears to exist. You might be able to test it with dnf install @cosmic-desktop-environment.
I noticed a slight wrinkle on the website - presumably it’s to do with KDE getting equal billing with Workstation in 42.
On the KDE download page at its old URL (Fedora KDE Plasma Desktop | The Fedora Project) you can download either the 41 ISO, or the 42 beta ISO, according to the value of the “Show Beta downloads” toggle.
On the new URL (Fedora KDE Plasma Desktop | The Fedora Project) only 42 beta is available. If you turn off the “Show Beta downloads” toggle, you aren’t offered 41.
It would be a pity if somebody lands on the new page and thinks there isn’t a stable Fedora KDE release available to download!
Technically, KDE got promoted to edition in F42, and that’s why there is no KDE F41 edition download - there is no KDE F41 edition, “just” a KDE F41 spin. A link to that page might not hurt, though.
Indeed, but it’s not very obvious from looking at those pages. The old page has /spins/ in its URL, but it doesn’t use the “spin” terminology anywhere in the body of the page - it uses “Fedora KDE Plasma Desktop” not “Fedora KDE Spin”.
And when you land on the new page (Fedora KDE Plasma Desktop | The Fedora Project) you see in 36px text “Download Fedora KDE Plasma Desktop 41” - yet it is not in fact possible to download Fedora KDE 41 from that page.
To someone who doesn’t know the history, it would be pretty opaque why those two pages behave differently. There’s nothing in their text that really explains why they would.
I tried to put myself in the position of a new user who has been recommended Fedora KDE and is enthusiastic to try it. So I did this:
- DuckDuckGo’d “fedora” and followed the top link (https://fedoraproject.org/)
- Moused over “Get Fedora” at the top right of the page
- A menu opens showing “Editions”, with “KDE Plasma” prominently placed at the top middle of the editions on offer. Great! I clicked on “KDE Plasma”, taking me to The Next Generation Personal Desktop | The Fedora Project
- Clicked the “Download Now” button on that page, taking me to Fedora KDE Plasma Desktop | The Fedora Project
- That’s the page that prominently displays “Download Fedora KDE Plasma Desktop 41” but then shows “No files available for this version.”
- Maybe if I clicked around some more, I’d see the “Show Beta downloads” toggle and see that 42 beta is available. Maybe I’m happy with a beta version, maybe not.
Now, from the point of view of someone who already has the “inside baseball” knowledge that KDE was hitherto classified as a Spin, yes, you might think to look somewhere different. In fact if at step 3 I’d looked beyond the headline “Editions” and moused down to “Spins”, I’d have found the right page to download KDE.
But it’s unfortunate if the current website UX deters newcomers without the “inside baseball” knowledge from getting Fedora KDE.
As I understood the the website is automated now. As soon as F42 Is stable there will be the download link of the F42 stable version.
Further questions about the KDE Spin/Eddition location can be made here:
Fedora KDE Desktop (Spins) F41 versus Fedora KDE Plasma F42 eddition
This is nice, I have just downloaded the latest F42 beta image and I have installed httpd, caddy and it works fine. I tried installing firewalld and start the service but it fails, I think there might be missing dependencies I guess.
I am testing it on Windows Server 2022
F42 is beta, please create a independent topic, out of the announcements. This way we might be able to debug it, and while it gets released as stable it can be fixed.
Please see this in context with firewalld. It might causes issues.
2 Likes
I just set up a VM for F42 Workstation, so far it’s working perfectly. The Anaconda installer looks much better! I’ll keep my eyes open for any bugs or crashes. Anyways congratulations on the Beta release!
1 Like
The WSL build is available here to test.
You can find the instructions from the test day to set up the WSL environment.
2 Likes
F42 beta Xfce spin is pretty good!
I tried fips=1 and Xfce terminal would crash on maximize (problem reporter hinted it being related to FIPS/algos).
Edit: wine couldn’t run stuff (up-to-date F42 beta Xfce about 2 hours ago). I don’t think it’s the new Wow64 mode, but .exe’s wouldn’t execute (logging with regular WINEDEBUG output didn’t show anything obvious).
This with winetricks failed for me (it downloaded the .msi’s but eventually reported failure):
WINEPREFIX=~/'.wine/osu!' winetricks -q 'dotnet48' 'gdiplus'
wine still seems to not work on Fedora-Workstation-Live-42-1.1.x86_64.iso; above winetricks command gives this eventually (other exes also do the ntdll.dll error):
warning: Running /usr/bin/wineserver -w. This will hang until all wine processes in prefix=/home/espionage724/.wine/osu! terminate
------------------------------------------------------
Executing cd /home/espionage724/.cache/winetricks/dotnet40
Executing wine dotNetFx40_Full_x86_x64.exe /q /c:install.exe /q
002c:fixme:winediag:loader_init wine-staging 10.4 is a testing version containing experimental patches.
002c:fixme:winediag:loader_init Please mention your exact version when filing bug reports on winehq.org.
0024:fixme:winediag:loader_init wine-staging 10.4 is a testing version containing experimental patches.
0024:fixme:winediag:loader_init Please mention your exact version when filing bug reports on winehq.org.
012c:err:environ:init_peb starting L"Y:\\dotnet40\\dotNetFx40_Full_x86_x64.exe" in experimental wow64 mode
wine: failed to load L"\\??\\C:\\windows\\syswow64\\ntdll.dll" error c0000135
Application could not be started, or no application associated with the specified file.
ShellExecuteEx failed: 0024:err:start:fatal_error FormatMessage failed
------------------------------------------------------
warning: Note: command wine dotNetFx40_Full_x86_x64.exe /q /c:install.exe /q returned status 1. Aborting.
------------------------------------------------------
Installing wine.i686 and using /usr/bin/wine32 with a fresh 32-bit prefix also didn’t work.
Xeyes not working in 42 beta. Thank you for your work.
You will need to report the problem using the fedora bug tracker. See How to file a bug :: Fedora Docs
This topic was automatically closed after 30 days. New replies are no longer allowed.