/rss20.xml">

Fedora People

Updates and reboots on Fedora infrastructure

Posted by Fedora Infrastructure Status on 2026-11-19 22:00:00 UTC

Fedora Infrastructure team will be applying updates to servers and rebooting them.

Many services will be affected, most should only be down for a short time as their particular resources are rebooted HOWEVER some will be upgraded to F45 from earlier releases and may take a bit longer.

Hacking Wordle: A New User's Guide to the Power of the Linux Terminal

Posted by Fedora Magazine on 2026-11-18 08:00:00 UTC

For new Linux users the terminal can be like the Sphinx, quiet, mysterious, and offering no help to those who do not already speak its language. Here we'll show you how to get comfortable with the terminal by using some common commands to analyze a text file of words used by the popular online game, Wordle.

This analysis has real tasks to work on, giving you hands-on experience with the Linux command line. You'll be able to apply this experience to also work with logs, configuration files, and search for text inside files. These are fundamental skills an experienced user needs. Plus, you'll have some fun with Wordle.

I've Been Living Under A Rock. What's Wordle?

Wordle is an oddly addictive word game hosted by the New York Times. The goal of Wordle is to guess a five-letter word in no more than six guesses. The rules are simple. Guess a five-letter word. Wordle will mark letters that are not used, letters used but in the incorrect location, and letters in the correct location with different colors. Guess another word using the previous word's clues. Keep guessing until you've guessed the word or run out of guesses.

Wordle uses a curated list of words, so not every possible five-letter word can be a Wordle word. Offensive words, words with special characters or spaces, words using non-American spellings, and names (words that should be capitalized) are not used. Only certain plural and past tense words are accepted. Take a look at the full Wordle rules. These word rules narrow down possible Wordle words from some 20,000 dictionary five-letter words to about 2,500 words in the curated list.

Can the tools shown here be used to cheat at Wordle? If you play against others, the answer is yes. Being smart and clever about games is fun. Cheating is not fun....for anyone. Use this power for good only.

The Sphinx Speaks - First Look at the Terminal

If you're new to the terminal, let's take a quick tour. The application that let's you access the terminal from your desktop is a terminal emulator. On Fedora Workstation it is called Terminal. Fedora KDE uses a terminal emulator called Konsole. Open your terminal emulator application, and let's take a look around.

At the top left of the terminal window you see the prompt. The blinking cursor shows you where to type commands. The terminal uses software called a shell to communicate with the operating system. The terminal can use different shells, but we're going to use the default shell used by almost all Linux distributions, bash. You are probably already using bash, but let's confirm. To check your shell, type this command and hit Enter:

user@host:~$ echo $SHELL
/bin/bash

If the response is /bin/bash, you're set. If you get other responses (e.g., /bin/csh, /bin/ksh/, /bin/zsh), you're using a different shell. You may have problems with some of the tools we'll use. You can still follow along and run most of the commands, but you may encounter some issues.

The echo command just tells the terminal to "echo back" the item ($SHELL) to you. The item in question is a variable the system uses to hold the location to the preferred shell of the logged-in user.

Assuming you are using bash on Fedora, your prompt should look something like this:

user@host:~$

On some other Linux distributions, you may see a prompt that looks like this:

 [user@host ~]$

Either way, the prompt gives us four pieces of important information:

  1. The username of the current user in to the terminal. In the example this is "user".
  2. The hostname of the system. In the example the hostname is "host".
  3. The current working directory is user's home directory (~). You will see the tilde (~) used frequently in the terminal. It represents the /home/user/ directory. Remember, there's no place like ~.
  4. The $ at the end tells us we currently have non-root permissions. We're not going to make any system-wide changes, so this is perfect for us. It also indicates the shell is ready for more input.

Put the Terminal to Work - Create a Workspace

Let's make a directory we can store our data in. We'll assume you have a standard desktop install with pre-made folders like Documents, Music, Pictures, Downloads, etc. We're going to put our work in the Documents folder. Inside the Documents folder, we're going to make a new folder called 'wordle'. We use the terms 'folder' and 'directory' to mean the same thing. Old school Linux users prefer 'directory' as that is how they are referred to on the command line. Keep an eye on your prompt to see how it changes when you change directories.

First, change directories (cd) to the Documents directory:

user@host:~$ cd Documents

Now, make a new directory (mkdir) called 'wordle':

user@host:~/Documents$ mkdir wordle

Change directories (cd) to 'wordle':

user@host:~/Documents$ cd wordle

Your new working directory should be /Documents/wordle. Let's confirm that. Tell the terminal to print the name of the current working directory (pwd):

user@host:/Documents/wordle$ pwd
/home/user/Documents/wordle

Knowing which directory the terminal is in is important. The commands you issue will happen inside the current working directory unless you explicitly tell the command to use a different directory. Everything we're going to do should happen inside this directory.

Anytime you need help with a command, type the command followed by a space and --help to get a brief note on the basics of the command. Most linux commands have these flags you can use to modify the basic command. Some flags, like --help, are whole words and prefixed by two dashes. Other flags are just one letter preceded by a single dash. These flags are known as options. Try it with:

user@host:~/Documents/wordle$ pwd --help

You can also try using the --help option with other commands:

 mkdir --help

Now that you have your workspace set, we won't show the whole prompt. We'll show only the commands issued, like the one above.

Practice with the --help option as much as you want with the commands we've already used - cd, mkdir, pwd. Warning: If you try

echo --help

Well, see what happens. To get the help text for echo, use:

help echo

If you move out of the directory or close the terminal, you can easily get back to our 'wordle' directory by issuing the command:

cd ~/Documents/wordle

Let's Go Surfing - Finding a Wordle Word List to Analyze

Your Linux system comes with its own dictionary. It is a list of words applications can use to do things like check spelling. Wordle uses a curated word list, so the system dictionary won't be much help. There are many such curated Wordle word lists on the Internet, but you don't need to go searching for one. We've found a good list for you. Just open this link in a new browser tab:
https://raw.githubusercontent.com/Kinkelin/WordleCompetition/refs/heads/main/data/official/shuffled_real_wordles.txt

Take a few moments to study the file in the browser. Note the following things:

  1. The first line in the file starts with a #, but the rest of the file is five-letter words (all in lowercase) with each word on its own line. That may seem like a waste of visual space, but this is exactly the type of file Linux loves. Word processor documents, spreadsheets, tables, and columns all make the job of reading the file harder for Linux. This simple text file is perfect for us.
  2. The first line says the file has 2,315 words. Pretty close to the number of curated words used by Wordle.
  3. The words are not in alphabetical order. That might nag at our human sense of order, but it won't affect the analysis Linux will do.
  4. What about letter pairs (th, ou)? How often do they come up? In English, letter pairs are called digraphs. If both lettters are vowels, the pair is called a dipthong (shoutout to English teachers everywhere).

Ok, this is a good list. Let's download it into our workspace.

Back to the Terminal!

Click back into the terminal. Make sure you are in the correct workspace, the directory called wordle. Tell the terminal to download the file.

 wget https://raw.githubusercontent.com/Kinkelin/WordleCompetition/refs/heads/main/data/official/shuffled_real_wordles.txt

The command wget is a tool for downloading files from web servers. When the command tells you its done, confirm you have the file in the directory with a ls command. The ls command tells the terminal to list files and directories in a directory:

ls
shuffled_real_wordles.txt

We can also look at the contents of the file in the terminal. The cat (from the word catenate) command will do that, but it has a small hitch. See if you can spot it when we run the command:

 cat shuffled_real_wordles.txt

As you can see, the cat command just spits out the entire file contents. And since the file has 2,000+ lines, you can't see the whole thing. We should use the less command.

 less shuffled_real_wordles.txt

Aha! Now you see the top of the file, but not the end of the file. The less command shows you just one page of the file at a time. If you want to see the next page, just hit the spacebar or the PgDn/PgUp keys. The down/up arrow keys work, too, but only move one line at a time. You can do this as much as you like until you quit less. Move up and down a few pages and lines using the different navigation key options. To quit less, just tap the Q key. By the way, less is known as a pager command, because it shows output in pages.

One more command we want to use to inspect this file is wc or word counter. wc does exactly what its name says -- it counts words in a file. Try it:

 wc shuffled_real_wordles.txt
2316 2335 14000 shuffled_real_wordles.txt

wc displays line, word, and then byte counts. The three numbers match up with our expectations -- 2,315 lines plus a one-line description at the top, for a total of 2,316 lines and 2,335 words. If we want wc to show only lines, use wc -l or for words, wc -w. Try it:

wc -l shuffled_real_wordles.txt
2316 shuffled_real_wordles.txt

wc -w shuffled_real_wordles.txt
2335 shuffled_real_wordles.txt

Use wc --help to see how to count characters. We won't use it here, but it may be good to know.

See how that first sentence is keeping us from exactly matching the number of Wordle words? It's going to confuse Linux, too. We don't want that sentence in our analysis, so let's edit our file and get rid of it.

Terminal, Edit Me a Story

A good practice to follow before we edit a file is to make a copy of it first. That will let us have an original copy. In the terminal, we'll do this with the cp (copy command). In this case, we're going to give the command two filenames -- the original name and the new name. Also, let's give our working copy a shorter name:

 cp shuffled_real_wordles.txt words.txt

When we get no messages back, we can assume the command worked.

Now we edit our working file with with nano. Nano is the current default editor in Fedora. There are other editors that can be run in the terminal -- vim, emacs, micro, just to name a few. If you want to use a different editor, that's OK. We'll stick with nano here.

 nano words.txt

Once you are in nano, there are two important commands to remember. CTRL+O will write/save the file. Nano will ask you to confirm the name. Hit enter. The second command quits nano -- CTRL+X. If you make changes and try to quit without saving, nano will ask you if you want to save changes to the file (Save modified buffers?). You can press Y, N, or CTRL+C (cancel and return to nano), depending on what you want to do.

Delete that first line. Don't leave any blank spaces between the first word and the top of the file. Save the file and exit nano.

Let's check the wc output now:

 wc -lw words.txt
2315 2315 words.txt

Perfect. 2,315 lines and 2,315 words. See how we combined the -l and -w options? Many commands will let us do this. Keep this in mind as you gain experience with the terminal.

Let the Analyzing Begin!

Analysis is an intimidating word that just means asking questions and finding answers about a thing by breaking that thing down into its component parts. Take another look at our word list and its component parts, letters. What questions could we ask about them? Here are the questions we're going to work on in our analysis.

  1. What is the total letter frequency in the possible word list?
  2. What are the most frequent letters at the start of a word?
  3. What are the most frequent letters at the end of a word?
  4. What about letter pairs (th, ou)? How often do they come up?
    In English, letter pairs are called digraphs. If the letters are both vowels, the pair is called a dipthong (shoutout to English teachers everywhere).

You could easily come up with more questions. Make a note of them. After you get some experience, start hunting for answers on your own. For now, we'll focus on some simple text analysis questions.

I'll Grep You, My Pretty

The grep command's function is simple and powerful. It finds text based on a pattern you give it, and outputs what it finds. It can find exactly what we're looking for, or it can find things that come close to what we're looking for. In fact, grep is going to be the cornerstone of our analysis work, so we should spend some time learning the basics.

You tell grep what you want to find in the file by giving it a pattern or regular expression (also called a regex) and a place to search. Let's say you want to see if the word 'eater' is in our words.txt file. A recommended practice is to put the pattern in quotes, so we'll do that here:

 grep "eater" words.txt
eater

The response shows us grep found 'eater' in the file. Try this one:

 grep "eaton" words.txt

grep found nothing so nothing is returned. Remember, Wordle does not use proper nouns, so that makes sense (sorry, Eaton, Ohio).

What if we want to find all of the words with 'eat' in them? Simple enough:

grep "eat" words.txt
treat
wheat
cleat
heath
great
bleat
eater
eaten
cheat
death
sweat
pleat
meaty

Wow! Now we can begin to see the true power of grep.

When we are building our search pattern for grep, we can use special characters called wildcards and anchors. A wildcard is a placeholder for unspecified letters. We can use a dot (.) to represent any single character. The star/asterisk (*) character represents the previous character any number of times, including no character at all. Combine the dot and star (.*) to match any number of any character. Let's try wildcards out to see how they work with grep.

Words with a single character between 'e' and 'at':

grep "e.at" words.txt
begat
elate

Words with any number of (including zero) characters between 'e' and 'at'

grep "e.*at" words.txt
treat
wheat
cleat
heath
great
bleat
eater
eaten
cheat
death
sweat
begat
elate
pleat
meaty
eclat

The "e.*at" pattern matches all of the words the "eat" pattern PLUS begat, elate, and eclat.

Anchors tell grep where we want the search to be focused in a line. We can tell grep to search at the start (^) of the line or at the end of the line ($). This is exactly what we'll need when we check for the most frequent starting and ending letters in our words. Let's search for words with 'eat' at the start of the line in our words.txt file:

grep "^eat" words.txt
eater
eaten

How about words with 'eat' and the end of the line?

grep "eat$" words.txt
treat
wheat
cleat
great
bleat
cheat
sweat
pleat

The grep command has several available options, but we need to be aware of two of them. If you read grep --help, you'll see that grep has a count (-c) option that reports the number of lines matched by the pattern. If a word has two of the same letter, it will match that, but only count the line once.

 grep -c "a" words.txt
909

The grep command found 909 words that contain the letter 'a.'

The second grep option we need is -o, which prints out every match of the pattern it finds. Given a single line with two matches, the grep -o command prints out both matches. Let's see how it works:

grep -o "a" words.txt
a
a
a
.....

That time we asked grep to print out every occurence of a. It did that dutifully, printing out 'a' more times than we want to count. Let's give grep a little help with a pipe. We'll review pipes in greater detail next, but let's just add one to our last command.

grep -o "a" words.txt | wc -l
979

Here, we took our never ending lines of 'a' and sent them to wc to count. We came up with 979 occurrences. So, we can say that the letter 'a' is found in 909 words, but appears 979 times, thanks to repeated letters in words (e.g., alarm).

Say Hello to My Little Friend(s) -- Pipes and Filter Commands

The pipe symbol (|) tells the terminal to start the pipe process. The pipe tells the first command to send its output to the next command. The second command then receives the input, processes it, and spits it out in its own format. The commands and pipes together are called a pipeline. The commands receiving the output are filter commands. Almost any command can be a filter command, but there are a few commonly used filter commands we want to focus on -- sort, uniq, head, column, and tee. Briefly, here's what each does:

  • sort orders input. When used with -n, it can sort numbers, and with -r it can do a reverse sort.
  • uniq identifies and acts on repeated matches. When used with the -c option, it returns the occurence and the number of times the occurence was found.
  • head just displays the first 10 lines of ouput. The command can be adjusted to show a specific number of lines. head has a brother called tail that works on the last lines.
  • column formats input into multiple columns. This command is a gem when dealing with a long list of simple outputs.
  • tee copies output sent to our display and sends it to another location, like a file. It does not supress the output to the terminal. This helps us capture the output in a more permanent way, while still displaying output in the terminal.

Let's build a pipeline as an example

Say we want the output of one of our grep command to appear in alphabetical order, and we just want to see the first 5 lines.

grep "eat" words.txt | sort | head -5
bleat
cheat
cleat
death
eaten

Remember how the command grep -o "a" words.txt just printed out 'a' repeatedly? We piped the number of lines to wc -l to count the lines. The uniq -c does something similar, with a slightly different output:

grep -o "a" words.txt | uniq -c
979 a

The uniq command has the advantage over wc -l of being able to group together and count matching output. That will let us get the output of a grep command using wildcards while keeping an accurate count of each letter.

Let's count all the letters. We can use the (.) wildcard instead of typing every single letter. We'll add head to the end of our pipeline to keep our terminal tidy:

grep -o "." words.txt | uniq -c | head
1 s
1 c
1 o
1 w
1 l
1 w
1 a
1 g
1 e
1 r

What happened? grep sent the uniq command the data for each line. So, uniq told us the word 'scowl' has one 's', one 'c', etc. We want to know the total occurences for letters in all lines, not just the individual letters. We have to insert a sort to arrange the output of grep by letter before it gets sent to uniq. We'll use head to keep from filling the terminal with so much output:

grep -o "." words.txt | sort | uniq -c | head
979 a
281 b
477 c
393 d
1233 e
230 f
311 g
389 h
671 i
27 j

We're getting warm. We see that the letters are listed alphabetically, rather than by order of frequency. Let's throw in another sort. This one will sort the output by frequency or count. Remember to use a reverse number sort, so the letters are listed by order of their frequency, highest to lowest. This time, we want to see data on all of the letters, so let's replace head with column:


grep -o "." words.txt | sort | uniq -c | sort -nr | column
1233 e 729 t 575 n 393 d 311 g 195 w 29 q
979 a 719 l 477 c 389 h 281 b 153 v 27 j
899 r 671 i 467 u 367 p 230 f 40 z
754 o 669 s 425 y 316 m 210 k 37 x

That's it! We have listed letters in our Wordle words.txt file by order of frequency. Let's store this output in a file with the tee command.

 grep -o "." words.txt | sort | uniq -c | sort -nr | column | tee letter-freq.txt

We see in the display the same output as earlier. Check the letter-freq.txt file:

 cat letter-freq.txt

Bingo! Question #1 of our analysis is complete!

Now we need to answer questions #2 and #3.

Recall they are:

  1. What are the most frequent letters at the start of a word?
  2. What are the most frequent letters at the end of a word?

Since we've already figured out how to get total letter frequency in the file, all we have to do is adjust our grep command to check the first and last letters of each word. As we mentioned before, we can tell grep to do this by using the caret (^) or dollar sign ($) characters in our search pattern. Let's try it first before committing the results to a file.

grep -o "^." words.txt | sort | uniq -c | sort -nr | column
366 s 142 p 111 d 83 w 41 o 23 q 3 z
198 c 141 a 107 m 72 e 37 n 20 k
173 b 136 f 105 r 69 h 34 i 20 j
149 t 115 g 88 l 43 v 33 u 6 y

Too easy! Let's add the output to another file.

 grep -o "^." words.txt | sort | uniq -c | sort -nr | column | tee starting-letter-freq.txt

The terminal should display the same output as the previous command but the output is also stored in the file starting-letter-freq.txt.

Now, let's do the ending letters:

 grep -o ".$" words.txt | sort | uniq -c | sort -nr | column | tee ending-letter-freq.txt

We now have three files -- letter-freq.txt, starting-letter-freq.txt, and ending-letter-freq.txt -- that answer our first three questions.

Looking For Letter Pairs

In the final part of our analysis, question #4, we want to see which letter pairs are used most frequently. This time, instead of counting each instance of a letter pair, including repeated appearances in a single word, we only want to count the number of words that contain a specific letter pair. Using grep -c, we can create letter pairs once, and then count the number of words that contain that pair. Given that all of our words have only five letters, it's reasonable to conclude that our word count will not be too different from a total letter pair count. The only downside with the word count is that we'll find several letter pairs are not used at all. We can live with that. Let's get to work.

We can make letter pairs right in the terminal, automatically. We'll use a bash function called "brace expansion" to do just that. If you're using a shell other than bash, you'll have to check the documentation to see how your shell does brace expansion.

Brace expansion in bash is designed to generate unique strings given a base string and two or more items in a list. Typically, you'd want to use this to name related files. Here's an example:

 echo {dinner,lunch,breakfast}-menu.txt
dinner-menu.txt lunch-menu.txt breakfast-menu.txt

A nice feature of brace expansion is that bash understands sequential letter and number braces with a little shorthand trick:

 echo {a..z}
a b c d e f g h i j k l m n o p q r s t u v w x y z

and

 echo {1..7}
1 2 3 4 5 6 7

So, bash treats {a..z} as all of the letters of the English alpahabet in order, lowercase, and {1..7} as all numbers 1-7 in order.

How can we apply this to our letter pair problem? Let's try something simple first, like creating all the possible letter pairs that begin with 'a'. How about:

 echo a{a..z}
aa ab ac ad ae af ag ah ai aj ak al am an ao ap aq ar as at au av aw ax ay az

We're on the right track, but we want all letter pairs.

 echo {a..z}{a..z}
aa ab ac ad ae af ag ah ai aj ak al am an ao ap aq ar as at au av aw ax ay az ba bb bc bd be bf bg bh bi bj bk bl bm bn bo bp bq br bs bt bu bv bw bx by bz ca cb cc cd ce cf cg ch ci cj ck cl cm cn co cp cq cr cs ct cu cv cw cx cy cz da db dc dd de df dg dh di dj dk dl dm dn do dp dq dr ds dt du dv dw dx dy dz ea eb ec ed ee ef eg eh ei ej ek el em en eo ep eq er es et eu ev ew ex ey ez fa fb fc fd fe ff fg fh fi fj fk fl fm fn fo fp fq fr fs ft fu fv fw fx fy fz ga gb gc gd ge gf gg gh gi gj gk gl gm gn go gp gq gr gs gt gu gv gw gx gy gz ha hb hc hd he hf hg hh hi hj hk hl hm hn ho hp hq hr hs ht hu hv hw hx hy hz ia ib ic id ie if ig ih ii ij ik il im in io ip iq ir is it iu iv iw ix iy iz ja jb jc jd je jf jg jh ji jj jk jl jm jn jo jp jq jr js jt ju jv jw jx jy jz ka kb kc kd ke kf kg kh ki kj kk kl km kn ko kp kq kr ks kt ku kv kw kx ky kz la lb lc ld le lf lg lh li lj lk ll lm ln lo lp lq lr ls lt lu lv lw lx ly lz ma mb mc md me mf mg mh mi mj mk ml mm mn mo mp mq mr ms mt mu mv mw mx my mz na nb nc nd ne nf ng nh ni nj nk nl nm nn no np nq nr ns nt nu nv nw nx ny nz oa ob oc od oe of og oh oi oj ok ol om on oo op oq or os ot ou ov ow ox oy oz pa pb pc pd pe pf pg ph pi pj pk pl pm pn po pp pq pr ps pt pu pv pw px py pz qa qb qc qd qe qf qg qh qi qj qk ql qm qn qo qp qq qr qs qt qu qv qw qx qy qz ra rb rc rd re rf rg rh ri rj rk rl rm rn ro rp rq rr rs rt ru rv rw rx ry rz sa sb sc sd se sf sg sh si sj sk sl sm sn so sp sq sr ss st su sv sw sx sy sz ta tb tc td te tf tg th ti tj tk tl tm tn to tp tq tr ts tt tu tv tw tx ty tz ua ub uc ud ue uf ug uh ui uj uk ul um un uo up uq ur us ut uu uv uw ux uy uz va vb vc vd ve vf vg vh vi vj vk vl vm vn vo vp vq vr vs vt vu vv vw vx vy vz wa wb wc wd we wf wg wh wi wj wk wl wm wn wo wp wq wr ws wt wu wv ww wx wy wz xa xb xc xd xe xf xg xh xi xj xk xl xm xn xo xp xq xr xs xt xu xv xw xx xy xz ya yb yc yd ye yf yg yh yi yj yk yl ym yn yo yp yq yr ys yt yu yv yw yx yy yz za zb zc zd ze zf zg zh zi zj zk zl zm zn zo zp zq zr zs zt zu zv zw zx zy zz

And there is our letter pair list, all 676 of them.

So how are we going to run all of these through grep? The pipeline commands we used would work, but we would have to manually enter each letter pair as the pattern. We need something to send the output of the brace expansion to grep. And we have just such a solution called a "for loop". Let's take a look at a simple for loop in the terminal:

 for n in {1..5}; do echo $n; done
1
2
3
4
5

What's happening here? We tell bash for each number (n) in the list created by the brace expansion of {1..5}, do the echo command on that number, then finish.

You see that each step in the loop construct is separated by a semicolon. We gave the individual items in the brace expansion a name (n). The n is called a variable, and when we use it again, we refer to it as $n so bash knows it is a variable name.

This is a lot of work going on in one line, so bash allows us to use new lines instead of the semicolons, as shown below. When you hit enter after the first line, bash knows you haven't given it a full command yet, so it goes to the next line, and adds a '>' to the front of the display. When you've given bash a complete command, after you type 'done,' bash goes to work.

 for n in {1..5}
>do echo $n
>done
1
2
3
4
5

Multiple commands can occur in the loop. We just add them to the list of commands after the 'do', like this:

 for n in {1..5} 
do echo "The number is..."
echo $n
done
The number is...
1
The number is...
2
The number is...
3
The number is...
4
The number is...
5

As easy as this is to do, it's still a bunch of typing. Any mistakes we make will mean we have to go back and re-type the whole command. We should put it into a file that we can execute without typing the whole thing out.

Welcome to shell scripting!

We could write the script just like we've done in the terminal, but that won't be very readable for humans. Let's use a couple readability tricks for our script. When scripting a for loop, many experienced scripters use this format:
for n in {1..5}; do
 echo "The number is..."
 echo $n
done

We put the "for" and "do" statements on the same line, separated by a semicolon. This lets the reader see a loop is coming, and keeps the list of commands in the format we would use directly on the command line, one command per line. We also indented each command, so they are nestled between the 'for/do' and 'done' statements.

Now we're ready to create a shell script to count letter pair frequency. Let's create a filename called 'lpcount.sh' The '.sh' at the end is called a filename extension. It will tell the terminal this is a script file.

nano lpcount.sh

Add this text to the file:

 #!/bin/bash
for n in {a..z}{a..z}; do
 pcount=$(grep -c $n words.txt)
 echo $pcount $n
done

Save and close the file with CTRL+O, ENTER, CTRL+X. Next, we have to make the file executable. We do this with the chmod (change file mode bits):

chmod +x ctofive.sh

We have our first script! Don't dismiss the script because of its small size. you'll find other situations where short scripts like these can save you tons of time. Experienced users usually have a collection of these home-made scriptlets or snippets to make their work easier. Let's finish up our analysis by using our new script in a pipeline.

First, we just want to test the script to make sure it works. We'll use the head command in a pipeline so we only get the first 10 lines, rather than all 676.

 ./lpcount.sh | head
0 aa
29 ab
52 ac
49 ad
1 ae
18 af
26 ag
2 ah
47 ai
2 aj

Perfect! Let's run the command again. This time, we'll do a reverse number sort, format the output into columns and send the output of all 676 letter pair word counts to a file.

Question 4 has been answered! Later, you may want to look for starting or ending letter pairs. We've already done starting and ending single letters, so finding starting and ending letter pairs won't be too difficult.

Summary and Next Steps

We took our first steps into the linux terminal and bash by doing some analysis on a Wordle word list. You can easily apply these skills to other tasks, like log and config file reviews. The techniques used here are useful, but in some cases, not optimal. As you learn bash, you'll find better ways to do the simple things we've done here. You also wrote a small program that does something useful. If I've whetted your appetite to do more text analysis, I recommend you learn a dedicated language like Python or Perl. As powerful as bash scripting is, those two programming languages will outstrip bash in capability and speed very quickly when it comes to text analysis.

Login issues with Forge & Bodhi

Posted by Fedora Infrastructure Status on 2026-11-17 10:00:00 UTC

Update: Now resolved, there was a configuration issue with our OIDC setup.

We are aware of an issue logging into the Forge & Bodhi. We are investigating.

Since the Forge is down, please log issues in #admin:fedoraproject.org for now.

Dictate into any app on Fedora with TuxTalk

Posted by Fedora Magazine on 2026-11-16 08:00:00 UTC

TuxTalk is a free voice dictation tool for Linux. You hold a key, talk, and let go. What you say appears wherever your cursor is located: a document, an email, a chat box or a terminal. The speech model runs on your own computer, so your voice never leaves it and there is no account to create. This is provided under the MIT license and the code is on GitHub.

This article walks through installing it on Fedora Workstation or Fedora KDE Plasma Desktop, what the first run changes on your system and why, using it day to day, and removing it if you wish.

Before you start

You need a working microphone and a 64-bit Fedora install on x86_64. No graphics card is required. The default speech model is fast on an ordinary processor, and if you have an NVIDIA, AMD or Intel graphics chip, TuxTalk can use it through Vulkan.

TuxTalk isn't in the Fedora repositories and there's no Copr build. You install the RPM from the project's GitHub releases page and check it against the checksum file published with it.

Install the RPM

Download both tuxtalk-0.23.1-1.x86_64.rpm and SHA256SUMS.txt from the latest release at https://github.com/ronb1964/TuxTalk/releases into the same folder. Then check the RPM against the checksum file:

$ cd ~/Downloads
$ sha256sum -c --ignore-missing SHA256SUMS.txt
tuxtalk-0.23.1-1.x86_64.rpm: OK

If it says anything other than OK, delete the file and download it again. Then install it with dnf, which also pulls in the few system libraries it needs:

$ sudo dnf install ./tuxtalk-0.23.1-1.x86_64.rpm

dnf warns that it skipped the OpenPGP check for the package. This is because the RPM isn't signed with a key and why the checksum step, indicated above, matters.

The package installs into /opt/talktype (the folder kept the app's old name so upgrades replace files in place), adds a tuxtalk command, and puts TuxTalk in your applications menu.

Installing on Atomic Desktops

For Silverblue and the other Fedora Atomic desktops, download the AppImage from the same release page indicated above (see the Assets section). Make it executable and run it:

$ chmod +x TuxTalk-v0.23.1-x86_64.AppImage
$ ./TuxTalk-v0.23.1-x86_64.AppImage

What the first run changes

Start TuxTalk from your applications menu. The first-run screen looks at your graphics card and your language and recommends a setup. The default is NVIDIA's Parakeet model, which covers English and 24 other European languages. If you need another language, OpenAI's Whisper covers 99 of them. Either one downloads once and then works offline.

TuxTalk's first-run welcome screen on Fedora KDE Plasma, listing its key features and the three steps: hold F8, talk, let go.
The first-run screen

The first run also asks for your admin password once, to set up two things:

  • The hotkey helper. On Wayland an ordinary program cannot detect keys pressed in other windows, so TuxTalk needs help to notice F8. A small helper program runs as a systemd service, tuxtalk-hotkeys, and it's the only part of TuxTalk that reads the keyboard. It doesn't run as root. It runs as a throwaway user (systemd's DynamicUser) whose only extra right is the input group, with no network, no access to home folders, a read-only system and no way to gain more privileges. It only reports hotkeys, never what you type: F-keys and the few other keys that never type anything, Right Ctrl or Right Alt on their own, or a key held together with two of Ctrl, Alt and Super. Letters, numbers and Enter are never reported. And it only reports them to the user who's at the screen. The file it runs sits in a root-owned folder, /usr/local/libexec/tuxtalk, so nothing you run as yourself can change it.
  • A udev rule that gives /dev/uinput to the user at the screen, the same way Steam's rule does for game controllers. TuxTalk uses it to type, through its own virtual keyboard. A program can press keys with /dev/uinput, but it can't read them.

A restart is not needed. You can look at the helper yourself:

$ systemctl status tuxtalk-hotkeys
$ systemd-analyze security tuxtalk-hotkeys

The second command rates it 0.6, "SAFE".

On Fedora Workstation, TuxTalk also offers to install its GNOME Shell extension, which puts its menu in the top bar. GNOME only loads a new extension after you log out and back in once. On KDE Plasma it shows a tray icon instead.

Dictate

Click where you want the text to go, hold F8, say what you want, and let go. A moment later the text appears. If you'd rather not hold a key for a long dictation, tap F9 to start and tap it again to stop.

KWrite on Fedora KDE Plasma with two dictated sentences: This is a test of the dictation system. Is that right?
Two sentences dictated into KWrite

A few things that make it more useful:

  • Say punctuation and it appears: "comma", "period", "question mark", "new paragraph".
  • Say an email address the way you'd say it out loud. "john at gmail dot com" comes out as john@gmail.com.
  • In a terminal it leaves off the capital letter and the period, so a dictated command is ready to run.
  • Names and terms it keeps getting wrong go in Your Words in Preferences, spelled your way. Or say "fix that word" right after a dictation.
  • For hands-free use, turn on the double-tap option under Preferences → General. Then double-tap F9, talk as long as you like, and it stops by itself when you stop talking.

If your F-keys need the Fn key, Preferences → General also offers Right Ctrl, Right Alt, Scroll Lock or Left Ctrl+Space.

There's more in TuxTalk Labs under Preferences → Advanced. Each feature in this menu is off until you turn it on. The newest feature is running the desktop by voice: opening apps, snapping windows, and a numbered mouse grid you can click with by voice.

Remove TuxTalk

Open Preferences, go to Updates & Backup and click Uninstall TuxTalk…. It asks for your password once and removes everything it set up: the program, the hotkey helper, the udev rule, the downloaded models and the GNOME extension. Your settings are retained unless you tick the box to delete them as well. If TuxTalk won't open, the same thing can run from a terminal:

$ tuxtalk --uninstall

Removing only the package with sudo dnf remove tuxtalk takes the hotkey helper with it, but leaves your settings and the downloaded models in your home folder.

Feedback

TuxTalk is a hobby project, and it gets better when people tell me what doesn't work for them. Questions, problems and ideas are welcome in the Discussion section in the GitHub project at: https://github.com/ronb1964/TuxTalk/discussions

A note on how this was made:

I can't write code. TuxTalk is written by Claude, Anthropic's AI, and I test it and use it every day. I do my best to make sure the code is held to a standard a human developer can respect. Claude also helped me draft this article. I went through it and changed it to sound more like me, and I've checked every step in it. (Assisted-by: Claude)

New badge: F50 i18n Test Day Participant !

Posted by Fedora Badges on 2026-11-16 07:52:19 UTC
F50 i18n Test Day ParticipantYou helped testing Fedora 50 i18n features

New badge: F49 i18n Test Day Participant !

Posted by Fedora Badges on 2026-11-16 07:51:30 UTC
F49 i18n Test Day ParticipantYou helped testing Fedora 49 i18n features

New badge: F48 i18n Test Day Participant !

Posted by Fedora Badges on 2026-11-16 07:50:51 UTC
F48 i18n Test Day ParticipantYou helped testing Fedora 48 i18n features

New badge: F47 i18n Test Day Participant !

Posted by Fedora Badges on 2026-11-16 07:50:13 UTC
F47 i18n Test Day ParticipantYou helped testing Fedora 47 i18n features

New badge: F46 i18n Test Day Participant !

Posted by Fedora Badges on 2026-11-16 07:49:21 UTC
F46 i18n Test Day ParticipantYou helped testing Fedora 46 i18n features

New badge: Fedora 50 CoreOS Test Day !

Posted by Fedora Badges on 2026-11-16 06:38:57 UTC
Fedora 50 CoreOS Test DayYou helped solidify the core for the Fedora 50 rebase!

New badge: Fedora 49 CoreOS Test Day !

Posted by Fedora Badges on 2026-11-16 06:38:26 UTC
Fedora 49 CoreOS Test DayYou helped solidify the core for the Fedora 49 rebase!

New badge: Fedora 48 CoreOS Test Day !

Posted by Fedora Badges on 2026-11-16 06:37:47 UTC
Fedora 48 CoreOS Test DayYou helped solidify the core for the Fedora 48 rebase!

New badge: Fedora 47 CoreOS Test Day !

Posted by Fedora Badges on 2026-11-16 06:37:20 UTC
Fedora 47 CoreOS Test DayYou helped solidify the core for the Fedora 47 rebase!

New badge: Fedora 46 CoreOS Test Day !

Posted by Fedora Badges on 2026-11-16 06:35:19 UTC
Fedora 46 CoreOS Test DayYou helped solidify the core for the Fedora 46 rebase!

New badge: Fedora 45 CoreOS Test Day !

Posted by Fedora Badges on 2026-11-16 06:34:33 UTC
Fedora 45 CoreOS Test DayYou helped solidify the core for the Fedora 45 rebase!

Installing the official Claude Desktop Linux beta on Fedora Linux

Posted by Fedora Magazine on 2026-11-13 08:00:00 UTC

Anthropic released a Linux beta of Claude Desktop, but only as a .deb package for Debian and Ubuntu. claude-desktop-rpm is a small Bash script that installs that same package on Fedora. This article covers what the script checks, what it changes on your system, and how to remove it again.

Before you start: what this is and what it costs

Claude Desktop is proprietary software from Anthropic, released under Anthropic's own terms. The install script described here is MIT licensed. It is not made by Anthropic and it does not redistribute any of Anthropic's files: it downloads the package from Anthropic's own repository each time.

You need a Claude account to use the app. Chat works on every plan, including the free one. Claude Code and Cowork, the two features most people install the desktop app for, need a paid plan (Pro, Max, Ultra, Team or Enterprise). Anthropic's download page lists the current plans and prices.

If you would rather use free and open source tools for this kind of work, there are good options that run on Fedora too, such as OpenCode and Hermes Agent. This article is for people who already use Claude and want the official app on Fedora.

What the script checks before installing

Anthropic publishes the Linux beta as a signed APT repository. The script described here reads that repository the same way APT would, and stops if any check fails:

  1. Anthropic's public key must match a fingerprint pinned in the script.
  2. The repository index (InRelease) must be signed by that key, and its Valid-Until date must not have passed.
  3. The package list's checksum must match the signed index.
  4. The .deb's checksum must match the package list.

Only if all these checks are passed does it unpack the .deb. A reader on Fedora Discussion found a gap in the first version (the index could be signed by any key in the key file, not only the pinned one). That is fixed, and the test suite now runs each of these checks against a tampered copy of the repository.

Installing it

The script needs four packages that most Fedora Workstation systems already have. You might verify that these are available:

sudo dnf install curl gnupg2 binutils tar

Next, download the Claude script from the latest release into a folder and run it as your normal user:

curl -fLO https://github.com/ajithakdev/claude-desktop-rpm/releases/latest/download/claude-desktop-rpm.sh

chmod +x claude-desktop-rpm.sh && ./claude-desktop-rpm.sh install

Each release also publishes a checksum file, SHA256SUMS. To check the downloaded script before running it, fetch that file into the same folder used to contain the script and compare:

curl -fLO https://github.com/ajithakdev/claude-desktop-rpm/releases/latest/download/SHA256SUMS

sha256sum -c SHA256SUMS

The script is a single Bash file so you can also read it before running it.

The installation does NOT use sudo. Everything goes into ~/.local (the app, a launcher, the menu entry and icons) and ~/.config (a systemd user timer for updates). The script also copies itself to ~/.local/bin/claude-desktop-rpm, so from then on you can run it by name.

Open Claude from the application menu and sign in. If something looks wrong, run:

claude-desktop-rpm doctor

This checks the installation, the launcher, automatic updates, the tray icon, the keyring that stores your sign-in, and the Cowork prerequisites. Each warning comes with the command that fixes it.

Why the app stays light in dark mode

On GNOME, the app stays light even when the desktop is set to dark. Electron apps on Linux read the GTK theme name, and GNOME's dark style does not change that name. It sets a separate color-scheme preference that Electron ignores.

The script does not touch Anthropic's files. Instead, the launcher created checks GNOME's color-scheme setting when you start the app, and sets GTK_THEME=Adwaita:dark for Claude only when it is dark. If you set GTK_THEME yourself, the launcher leaves it alone.

GNOME also hides tray icons by default, and Claude's tray menu is where Quit lives. The doctor command tells you how to turn on the AppIndicator extension if you want the icon.

Setting up Cowork

Cowork runs tasks inside a small virtual machine, so it needs KVM, QEMU, UEFI firmware and virtiofsd. On Fedora all of these come from Fedora's own repositories. Run this once:

claude-desktop-rpm cowork

This is the only command that uses sudo. It performs the following steps:

  • installs qemu-system-x86-core, edk2-ovmf and virtiofsd with dnf
  • writes /etc/modules-load.d/vhost_vsock.conf and loads the vhost_vsock module
  • adds you to the kvm group

Log out and back in for the group change to take effect. The command does not change any file that a package owns, so rpm -V stays clean. An earlier version did replace two firmware links that edk2-ovmf ships. That was a mistake, and the current version restores the packaged links if it finds the old ones.

Plan for disk space

The app's Cowork virtual machine files take about 12 GB in ~/.config/Claude.

Updates

The script installs a systemd user timer that checks Anthropic's repository once a day. Each update goes through the same checks as the first install. If Claude is open when an update arrives, the script downloads and verifies it but waits, and the launcher puts it in place the next time you start the app.

To turn the daily check off or on again use these commands:

claude-desktop-rpm auto-update off

claude-desktop-rpm auto-update on

Note: If the app shows its own "Update available" button, ignore it. Its link points to APT. The timer handles updates, or you can quit Claude and run claude-desktop-rpm update.

A second account

Some people keep separate Claude accounts for work and personal use. Version 1.2.0 added profiles for that:

claude-desktop-rpm profile add work

This adds "Claude (work)" to the app menu. It opens with its own sign-in and chats in ~/.config/Claude-work, and it can run next to your normal Claude window. The launcher passes Chromium's --user-data-dir flag to do this. Anthropic does not document that flag for Claude Desktop, so a future version could ignore it. If that happens, both menu entries open your normal account and nothing is lost. Both tray icons also look the same; the tray menu, which shows each account's plan, tells them apart.

What does not work yet

  • Computer Use is not in Anthropic's Linux build on any distribution yet.
  • The script is tested on Fedora 44 Workstation (GNOME, x86_64), and its automated install test also passes on Fedora 45. A user reported it working on KDE Plasma on Aurora, an atomic Fedora variant. Other desktops and RHEL-based systems have not been tested much.
  • Anthropic officially supports only Debian and Ubuntu for now. If something breaks after an update, the problem may be in the script, so please report it on the project's issue tracker rather than to Anthropic. (See the project link in the Links section below)

Removing it

claude-desktop-rpm uninstall

This removes everything the install added to ~/.local and ~/.config, including the timer and any profile menu entries, and rebuilds the menu, file-type and icon caches.

Your chats and sign-in in ~/.config/Claude stay, in case you reinstall. Delete that folder (and any Claude-NAME folders) to erase them too.

The uninstall never uses sudo, so the Cowork setup stays: remove the packages with dnf and delete /etc/modules-load.d/vhost_vsock.conf if you no longer need them.

Links

AI Use

Assisted-by: Claude (drafting help for the script and this article; the author reviewed every part and tested each command on Fedora 44).

Fedora Copr outage - updating servers

Posted by Fedora Infrastructure Status on 2026-11-12 10:30:00 UTC

There will be a Fedora Copr outage while we upgrade infrastructure machines to the latest Copr packages.

The build queue processing will be stopped during the outage, and the Frontend/Web-UI will be down most of the time (no new tasks accepted). The DNF packages and repositories (hosted on copr-backend …

TWIF: November 02 to 08, 2026

Posted by Fedora Community Blog on 2026-11-11 17:02:45 UTC

This Week in Fedora (TWIF) is the Fedora community’s weekly report on project news, decisions, and contribution opportunities. Across the Fedora ecosystem this week, the primary focus was the highly anticipated release of Fedora Linux 45, with teams including Release Engineering, Quality, Infrastructure, Server, and Docs finalizing release candidates, deploying updates, and immediately transitioning into Fedora 46 planning. Beyond the release cycle, a major shared initiative is the Bootable Image Unification (“Atomic Fusion”) project, which dominated the agendas for the Council, Atomic, IoT, and Hummingbird groups as they prepared proof-of-concept demos. Infrastructure and tooling migrations also commanded significant cross-team collaboration; the Council, FESCo, and Quality teams are actively evaluating a potential transition from Bugzilla to a Forgejo-integrated issue tracker, while FESCo, Release Engineering, and ELN are coordinating the complete removal of the legacy DNF4 stack. Finally, adapting to upstream shifts and reinforcing system security were key technical themes, highlighted by FESCo and the KDE SIG managing the deprecation of X11 in KDE Plasma 6.8, alongside widespread security patching and cryptographic upgrades—such as the adoption of %openpgpverify—across the Perl, Rust, Cloud, and Infrastructure teams.

NOTE: This is an experiment of translating the This Week in Fedora report into a Fedora Community Blog series. Do you have feedback? Reply to the Fedora Discussion topic attached to this post and let us know your thoughts.

This Week in Fedora is generated with AI assistance, and this Community Blog edition was prepared with AI assistance too. AI-assisted summaries can be wrong, so please check anything important against the linked sources. If you spot a problem, open an issue in the TWIF repository or reply to this post’s Fedora Discussion topic.

Announcements

Announcements

The highly anticipated release of Fedora Linux 45 is now officially available, as announced across the project forums, community posts, and the announce and devel-announce mailing lists. This milestone brings exciting updates across the ecosystem, including Fedora Workstation 45 featuring GNOME 51’s reworked frame scheduling, and the KDE Plasma Desktop Edition highlighting KDE Plasma 6.8, the 30th-anniversary release of KDE. Hardware support continues to expand with the Fedora Asahi Remix 45 introducing out-of-the-box support for Apple M3 chips, alongside community-maintained RISC-V GA images available for testing, providing a great opportunity for contributors to report hardware enablement issues. For immutable OS users, detailed instructions are available for rebasing to Silverblue 45, while Fedora Atomic Desktops now utilize the new Anaconda Web UI and have migrated their repositories to the atomic-desktops organization, offering streamlined engagement for future contributors.

To avoid disruptive surprises, users and system administrators should note several key technical shifts in this release. The Anaconda installer now includes native support for Stratis storage configuration, simplifying advanced local storage management through an easy-to-use interface. Additionally, the unmaintained NetworkManager-vpnc and NetworkManager-fortisslvpn plugins are officially retired in Fedora 45, requiring users to migrate to actively supported VPN alternatives to maintain enterprise connectivity. Finally, on the infrastructure side, a brief planned server outage occurred on November 6th to reboot main VPN, email, and bastion servers into a new kernel for CVE mitigation, ensuring the ongoing security of the project’s backend services.

AI

AI

The AI/ML SIG discussed new package reviews, notably OpenShell, an NVIDIA-driven tool for agent sandboxing. Packaging updates were announced, with the latest AI and ROCm packages now available in COPRs for released distributions, and new LLM servers like Gufo and Colibri landing in Rawhide. The group is also collaborating on a Fedora Magazine article highlighting the use of the pi-coding-agent to help Fedora contributors, which may evolve into a broader series exploring how AI is utilized within the Fedora ecosystem. Other chat discussions touched on integrating hardware volunteering for AI tasks and addressing Wayland compatibility issues for freelance time-tracking tools.

Decisions

  • The latest AI and ROCm packages are now available for general use in COPRs for released Fedora distributions.
  • New LLM servers, Gufo and Colibri, have been packaged and are available in Rawhide.
  • The SIG will pitch and publish a Fedora Magazine article focusing on the pi-coding-agent, potentially kicking off a series on how AI is used in Fedora.

Contribution opportunities

Learn more about the AI team.

Ambassadors

Ambassadors

The Ambassadors group saw two forum discussions this week. A new contributor asked for help setting up their Fedora Campus Ambassador profile, including access to the wiki, Fedora People, and Libravatar, and received troubleshooting steps from the community. Additionally, a member started an organizational thread to coordinate a meetup for Fedora, CentOS, AlmaLinux, and RockyLinux contributors attending SFSCON 2026 in Bolzano, Italy.

Contribution opportunities

  • Contributors attending SFSCON 2026 in Bolzano, Italy (Nov 13-14) are invited to connect and team up with other community members.

Learn more about the Ambassadors team.

Atomic

Atomic

This week, the Atomic group focused on bootable image unification (“Atomic Fusion”) with an upcoming presentation to the Workstation WG and a seed proof-of-concept demo (Meeting Agenda). In addition, there are ongoing discussions about rebasing Fedora Atomic Desktops on Fedora Bootc base images, which will modernize the build flow (Issue #88).

Several technical issues were also addressed, including a bug where systemd-oomd fails to intervene during memory exhaustion on Kinoite 44 (Issue #130), a syncing issue with the Fedora Cosmic-Atomic image (Issue #137), and an anomaly where rpm-ostree stable commits occasionally bundle packages from the updates-testing repository (Discussion).

Decisions

  • Systemd services in Atomic images will use ConditionPathIsMountPoint=/sysroot instead of checking for /run/ostree-booted to ensure compatibility with the composefs backend (Issue #133).
  • The Fedora Cosmic-Atomic update failure was identified as a release tooling script issue and moved to a releng ticket (Issue #137).

Contribution opportunities

  • Help is needed to file a releng ticket to investigate why rpm-ostree stable commits occasionally pull packages from the updates-testing repository (Discussion).
  • Contributors are invited to help create and review test cases for the upcoming Fedora Atomic Desktops Test Week, covering installations and upgrades via rpm-ostree, gnome-software, and plasma-discover (Issue #87).
  • Assistance is requested to test and provide a controlled reproducer for a memory exhaustion bug where systemd-oomd fails to intervene on Kinoite 44 (Issue #130).

Learn more about the Atomic team.

Cloud

Cloud

This week, the Cloud group focused on image configuration and distribution infrastructure. A key update involves adding the SUSPEND_SAFE_FPR guest OS feature to Fedora Cloud GCP images to address a page reporting suspend UAF vulnerability (CVE-2026-74481), which is now being applied to new nightly builds (Issue 449). Additionally, following the announcement that the HCP Vagrant Registry is shutting down on December 31, the group is discussing setting up a self-hosted Vagrant registry to ensure continued availability of Vagrant boxes, drawing inspiration from AlmaLinux’s recent implementation (Issue 450).

Contribution opportunities

  • Help is needed to set up a self-hosted Vagrant registry for Fedora to replace the retiring HCP Vagrant Registry before December 31 (Issue 450).

Learn more about the Cloud team.

COPR

COPR

This week, the COPR team successfully completed a scheduled server upgrade on November 3rd, bringing new features and bug fixes to the platform. Following the upgrade, an ongoing data migration to Pulp temporarily affected several projects (alphabetically from “sar” to “siddharthvipul1”), causing some 404 errors and pending builds which are expected to resolve as the migration progresses. Additionally, the team discussed the timeline for IPv6 support on the Pulp instance, estimating a fix for early next year, and provided support for building bleeding-edge Rust packages with vendored crates in Copr.

Decisions

  • Completed the scheduled COPR server upgrade on November 3rd to deploy new features and bug fixes. Details can be found in the mailing list thread, the Fedora Infra ticket, and the release notes.
  • Proceeded with the ongoing data migration to Pulp, which temporarily causes 404 errors and pending builds for affected project owners while their specific data is being migrated.

Contribution opportunities

  • Help is welcome to set up automation that recognizes new copr-cli tags being pushed, creates the sdist tarball, and automatically uploads it to PyPI.

Learn more about the COPR team.

CoreOS

CoreOS

This week, the CoreOS team celebrated the general availability release of Fedora Linux 45. The testing stream has been successfully rebased to version 45.20261030.2.1, bringing notable changes such as native Butane support in Ignition, the use of chunkah for better layer reuse in container images, the relocation of RPM repository configs out of /etc, and the update to Podman 6.0. The team is currently in the post-release cleanup phase and has already opened the tracker for the upcoming Fedora 46 rebase. In addition to the release activities, the team addressed several critical bugs and infrastructure tasks. A fix for the IPv4 TCP use-after-free vulnerability (CVE-2026-98432) was shipped in the stable stream, and workarounds are being tested for an ext4 /boot corruption issue affecting upgrades. The team also approved a proposal to switch Konflux-driven streams to a Jenkins poll-based import model to simplify downstream pipeline management.

Decisions

Contribution opportunities

Learn more about the CoreOS team.

Council

Council

This week, the Council focused on the long-term future of Fedora’s issue tracking and ongoing image unification efforts. A major discussion was initiated regarding the potential transition from Bugzilla to a Forgejo-integrated system (related to FESCO#3664), weighing the necessity of adopting modern, open-source infrastructure against concerns over Forgejo’s current maturity and feature parity. Additionally, the agenda for the November 5th Bootable Image Unification (“Atomic Fusion”) meeting was published, featuring a review of the project board, a seed proof-of-concept demo, and a planned presentation to the Workstation Working Group.

Contribution opportunities

Learn more about the Council team.

Design

Design

The Design team focused on the initial sketches for the F46 wallpaper, discussing the use of alternative geometric shapes for bubbles while prioritizing iridescence. They also reviewed poster designs, noting layout inconsistencies and the need for better text hierarchy and spacing, and successfully closed the F45 Virtual Release Party graphics ticket. Additionally, the team discussed accessibility improvements for international audiences, agreeing to spell out acronyms like DEI. In the Matrix chat, automated alerts indicated that the “Fix time of day path” action failed in both the main and f45-backgrounds branches of the backgrounds repository.

Decisions

  • Iridescence will remain the primary visual focus for the F46 wallpaper bubbles, regardless of the final geometric shape chosen.
  • The Fedora logo and mascots will not be included in the wallpaper to comply with guidelines and avoid clutter; instead, mascot concepts will be repurposed for promotional art.
  • Acronyms such as DEI (Diversity, Equity, and Inclusion) will be spelled out in designs to improve accessibility and clarity for international audiences.

Learn more about the Design team.

Docs

Docs

The Fedora Docs team successfully navigated the Fedora 45 release, merging numerous release notes covering updates like GNOME 51, KDE Plasma 6.8, and various system changes. Following the release, the team is restructuring the release notes repository to stop versioning; future notes will be built directly from the main branch, displaying the three most recent supported releases on a single page while older notes remain available via the Internet Archive.

Additionally, the team is revamping its infrastructure by transitioning the site-builder repository to build from main rather than prod. They are also evaluating “Bruce,” a new broken-link detection script, for CI integration to automatically generate static reports and eventually file issues for broken links. Furthermore, discussions are ongoing regarding Antora component consolidation to allow cross-repository module inclusion and integrating the Fedora Design Suite documentation.

Decisions

  • Stop versioning the release notes repository and build them exclusively from the main branch, preserving only the three most recent supported releases (Meeting, Issue #449).
  • Transition the site-builder repository (formerly docs-fp-o) to drop the prod branch and build the production site directly from main (Meeting, Issue #61).
  • Integrate the “Bruce” link-checking script into the CI pipeline in phases, starting with generating a static HTML report before moving to automated issue creation (Issue #69).
  • Retain docsbuilder.sh as a wrapper for local documentation previews while updating the underlying container to support Aarch64 and dropping npm dependencies (Issue #65).

Contribution opportunities

  • Review and merge open pull requests for the Fedora 45 Release Notes, as requested by community members (Forum Topic).
  • Help replace legacy {partialsdir} includes with the partial$ syntax across documentation repositories to align with current Antora standards (Issue #38).
  • Assist in documenting the Fedora Docs site build and monitoring process for the prod and stg branches (Issue #59).
  • Provide feedback on the proposed integration of the Fedora Design Suite documentation into the official Fedora Docs website (Issue #68).
  • Test and provide feedback on the proposed Antora module inclusion methods (component merge vs. Antora extension) to improve cross-SIG documentation discoverability (Issue #66).

Learn more about the Docs team.

ELN

ELN

The ELN SIG held a meeting on November 3, 2026 (meeting log). Key updates include the complete removal of dnf-4 from ELN, the completion of rebuilds for libxml2 2.15, and the replacement of perl-Params-Util with perl-Params-SomeUtil. Additionally, the Content Resolver now displays daily diffs. On the RISC-V front, approximately 140 packages have been built, though progress is currently paused pending fixes for toolchains like gcc, golang, and rust. The group also discussed ongoing issues with KDE Discover (Issue #633) and the unmaintained libappstream-glib (Issue #486), as well as upcoming libical4 rebuilds.

Decisions

  • dnf-4 has been completely removed from ELN and will not be included in RHEL 11.
  • perl-Params-Util has been replaced with perl-Params-SomeUtil.

Learn more about the ELN team.

EPEL

EPEL

This week in EPEL, discussions highlighted a known daily cache delay in the CentOS Stream repo for Fedora’s Koji, which temporarily caused scratch build failures in epel9-next (URL). Security updates were a major focus, with uv (v0.13.5) and ruff (v0.17.2) being pushed to stable for the EPEL10 leading branch to address multiple RUSTSEC vulnerabilities and the eMudhra CA compromise (URL). Additionally, pipx is being retired from EPEL9 due to 23 security vulnerabilities that cannot be practically patched on the older Python 3.9 stack (URL). Other activities included the EPEL 10.2 retirement announcement, progress on bringing mailman to EPEL10, and participation in the release party CLE presentation.

Decisions

  • The pipx package is being retired from EPEL9 due to severe security vulnerabilities and incompatible Python version requirements (URL).
  • Versions 0.13.5 of uv and 0.17.2 of ruff were pushed to stable for the EPEL10 leading branch to address critical security flaws (URL).

Learn more about the EPEL team.

Fedora Join

Fedora Join

Andrew Heath introduced himself to the Fedora community, sharing his extensive background in enterprise Linux, infrastructure automation, and image building. He expressed interest in contributing to packaging, image building, QA, and infrastructure automation. In response, he was welcomed by the community and advised to engage with the packaging team in their Matrix room to find a sponsor and initial tasks.

Contribution opportunities

  • Andrew Heath is seeking a packaging sponsor and looking for good first tasks, particularly in co-maintaining existing packages or picking up orphaned ones in the automation and sysadmin tooling space.
  • Opportunities exist to mentor or collaborate with Andrew in areas like image building (osbuild), QA testing, and infrastructure automation.

Learn more about the Fedora Join team.

FESCo

FESCo

During this week, FESCo celebrated the release of Fedora 45 and announced upcoming elections. The committee held a meeting and processed numerous tickets, focusing heavily on the future of Fedora’s issue tracking system, with extensive debate on whether to migrate to Forgejo or maintain a community-run Bugzilla instance. Other major topics included the coordinated removal of the legacy DNF4 stack and Modularity, as well as handling the deprecation of X11 support in KDE Plasma 6.8 for stable releases.

Decisions

  • Rejected the request to revert the removal of plasma-workspace-x11 from Fedora 44 and 45 in Ticket #3707.
  • Approved the pull request clarifying the responsibilities of the Engineering representative for the Council in Ticket #3613.
  • Rejected the Thin LTO Build Flag (F47) change proposal due to a lack of votes over five weeks in Ticket #3692.
  • Transferred maintainership of python-authlib to a new co-maintainer following the non-responsive maintainer policy in Ticket #3697.

Contribution opportunities

  • Community members are asked to help identify tools and scripts that depend on the legacy DNF4 stack or libmodulemd to assist with their planned removal in Ticket #3702.
  • Volunteers interested in maintaining a community-run Bugzilla instance are invited to put forward a proposal to the Fedora Infrastructure group, as discussed in Ticket #3664.

Learn more about the FESCo team.

Hummingbird

Hummingbird

The Hummingbird group prepared for their upcoming “Atomic Fusion” (bootable image unification) meeting on November 5, 2026. The agenda included a project board review, a potential demo of a seed proof-of-concept, and preparations for presenting to the Workstation Working Group.

Contribution opportunities

Learn more about the Hummingbird team.

Infrastructure

Infrastructure

The Infrastructure team successfully navigated the Fedora 45 release, officially lifting the infrastructure freeze on November 4th. The week involved significant maintenance and troubleshooting, including resolving a storage-related outage on Fedora Forge by resizing its Persistent Volume Claim and NetApp volume, and investigating persistent login issues with Fedora Accounts (FAS) linked to FreeIPA OTP interactions.

In addition to routine maintenance, the team began planning the deployment of Siguldry to the production environment for RPM and OSTree signing. They also scheduled a mass upgrade and reboot of infrastructure servers for November 19th, and discussed ongoing efforts to optimize AWS resource usage and clean up untagged cloud instances.

Decisions

  • The infrastructure freeze for the Fedora 45 release was officially lifted on November 4th. (URL)
  • A mass upgrade and reboot of most infrastructure servers is scheduled for November 19th at 22:00 UTC, which will cause short outages for many contributor services. (URL)
  • Mirrors that transparently redirect HTTP traffic to HTTPS will be updated in MirrorManager to explicitly use HTTPS URLs only, improving crawler compatibility. (URL)
  • The Limestone Networks mirror (mirror.lstn.net) was disabled in MirrorManager due to an expired TLS certificate. (URL)
  • New FAS groups were created for chromium-sig, sysadmin-oraculum, napkinstack-labs, tablepro, and nanlang.

Contribution opportunities

  • Help is needed to investigate and resolve the persistent Unauthorized: bad credentials login errors on accounts.fedoraproject.org, which appear to be related to FreeIPA OTP module interactions. (URL)
  • Contributors can help clean up NetApp and host storage, including moving older releases to archive volumes, increasing partition sizes on alerting hosts, and compressing logs. (URL)
  • Assistance is requested to set up a Zabbix HTTP check for Oraculum and retire its old watchdog email alerts. (URL)
  • There is an opportunity to help set up Zabbix monitoring for the staging autosign service by implementing checks for AMQP, RPMs, OSTree, and CoreOS metrics. (URL)
  • Help is needed to create an announcebot Discourse service user and API key for sending compose announcements. (URL)
  • A new contributor expressed interest in helping with virtualization and infrastructure tasks, presenting an opportunity for onboarding and mentorship. (URL)

Learn more about the Infrastructure team.

IoT

IoT

This week, the IoT group focused on bootable image unification and resolving a system upgrade issue. Laura Santamaria shared the agenda for the “Atomic Fusion” meeting, which included a seed proof-of-concept demo and a presentation to the Workstation Working Group (URL). Additionally, a user reported a bug where upgrading to Fedora 45 fails due to a missing GPG public key in rpm-ostree. The issue was resolved locally by updating the gpgkeypath in the fedora-iot.conf file to point to /usr/share/pki/rpm-gpg/ (URL).

Contribution opportunities

Learn more about the IoT team.

KDE

KDE

This week, the Fedora KDE group navigated discussions regarding Plasma 6.8 updates and overall desktop stability. Notably, the update to Plasma 6.8 officially drops X11 session support upstream, resulting in the obsoletion of kwin-x11 and plasma-workspace-x11 packages in Fedora 44. Users relying on X11 were advised that locking packages might prevent future UI updates, though community workarounds like Copr repositories have emerged. Additionally, the community discussed the marketing and perceived stability of Fedora KDE, with maintainers emphasizing that upstream KDE’s rapid release cadence inherently involves trade-offs. Users seeking long-term support might look toward LTS distributions, while those experiencing bugs are encouraged to contribute directly to upstream bug resolution.

Decisions

  • The update to Plasma 6.8 proceeds with the obsoletion of X11 packages (kwin-x11 and plasma-workspace-x11) due to upstream dropping X11 session support, as discussed in Why the Obsoletes: kwin-x11 and plasma-workspace-x11 in 6.8?.
  • The replacement of kwallet with oo7-daemon is currently deferred for KDE Plasma and Plasma Mobile variants due to a lack of time for integration, as noted in Issue #700.
  • The screen package will not be added to the Kinoite base image; users are advised to use package layering or system extensions instead (Issue #723).

Contribution opportunities

  • Contribute to upstream KDE bug resolution to improve the stability of the Plasma desktop environment, as suggested in the discussion on Fedora KDE stability.
  • Assist with testing and providing feedback on whether KDE processes crashing on boot is still an ongoing issue.
  • Help integrate oo7-daemon and build automatic migration paths from kwallet for future releases (Issue #700).

Learn more about the KDE team.

Legal

In a discussion regarding the koneko license and copyright, Cristian Le followed up on concerns regarding copyrighted sprites included in the project, specifically characters from Cardcaptor Sakura and the BSD Daemon. Following previous advice to drop the artwork, Cristian confirmed that the issue has been flagged to the upstream developers and that the problematic sprites will be removed via a downstream patch if necessary.

Decisions

  • The copyrighted sprites (Cardcaptor Sakura and BSD Daemon) in koneko must be removed, either by upstream or via a downstream patch. (Source)

Learn more about the Legal team.

Magazine

Magazine

This week, the Magazine group’s activity centered around a comprehensive guide on Complete FIDO2 Integration with Fedora Luks2, Unlock, GUI Login, and Sudo Auth. Administrative actions were taken to split three posts from this discussion into a new topic dedicated to revising the guide for Fedora Linux 44.

Contribution opportunities

  • Community feedback is welcome to improve the FIDO2 integration living document.
  • Contributors are encouraged to explore, test, and share improvements regarding FIDO2 integration for Polkit GUI prompts, as the original author left this partially incomplete.

Learn more about the Magazine team.

Mindshare

Mindshare

This week, Mindshare began early planning for the Virtual F46 Release Party, aiming for May 2027, to ensure a smooth event by crowd-sourcing ideas and recruiting role leads well in advance. Additionally, a community member reached out to organize an informal meetup for Fedora, CentOS, AlmaLinux, and RockyLinux contributors attending SFSCON 2026 in Bolzano, Italy.

Contribution opportunities

  • Help organize the Virtual F46 Release Party by volunteering for event team roles including Wrangler, Speakers, Design, Promotion & Content, and Production & Video. To get involved, join the #commops:fedoraproject.org Matrix room and reply to the ticket.
  • Connect with other community members at SFSCON 2026 in Bolzano, Italy, by joining the organizational thread.

Learn more about the Mindshare team.

Perl

Perl

This week, the Perl group focused heavily on package maintenance, dependency management, and security enhancements. Maintainers implemented source signature verification using openpgpverify for packages like perl-Net-DNS and mod_perl. Several packages received routine version bumps, including perl-Mozilla-CA, perl-CGI, and perl-Tk-Text-SuperText. Additionally, contributors collaborated on adjusting dependencies for downstream distributions, such as adding build conditionals for Lexical::Var in perl-Exporter-Tiny and disabling optional dependencies in RHEL builds for perl-File-ShareDir.

Decisions

Learn more about the Perl team.

Python

Python

The Python group discussed reversing the deprecation of python-dateutil following a new upstream 4.0.0 release. Contributors agreed to undeprecate the package and patch out its new tzdata dependency to rely on the system’s time zone data instead. Additionally, a proposal was made to automatically set LD_LIBRARY_PATH in %py3_test_envvars to streamline testing, and feedback is currently being sought on potential breakages.

Decisions

  • Undeprecate the python-dateutil package following the new upstream 4.0.0 release.
  • Patch out the tzdata dependency in python-dateutil 4.0.0 to rely on system timezone data instead.

Contribution opportunities

Learn more about the Python team.

Quality

Quality

The Quality team successfully verified and tested the release candidates for Fedora 45, officially declaring it “GO” for release, alongside publishing and updating the Common Issues. The team also hosted a Test Week for Linux Kernel 7.3, encouraging users to test the kernel rebase on Fedora 44 and 45.

In other activities, the team concluded the F45 test days planning and GRUB EFI for Confidential Computing test days, while scheduling an upcoming KDE Plasma 6.8 test week for November 9-15. Infrastructure and CI improvements continued, including fixes for ELN Koji repositories and successful Fedora 45 installations on Beaker hardware. The team also finalized their requirements for the Bugzilla to Forgejo migration.

Decisions

  • Fedora 45 is officially approved (“GO”) for release after successful release candidate testing.
  • The Bugzilla to Forgejo migration requirements have been formally gathered and submitted, closing the investigation.
  • The Cockpit test day has been postponed to the Fedora 46 release cycle.

Contribution opportunities

Learn more about the Quality team.

Release Engineering

Release Engineering

Fedora 45 has been officially released, with the team handling final release candidate composes, signing the IoT compose, and managing post-release cleanup and synchronization. During the rollout, a minor synchronization issue with the Labs images was manually resolved, and discussions were held to better align fedora_distro_aliases and releases.json updates in future cycles.

In addition to the release, the team resolved several infrastructure and build issues. This included fixing broken RHEL 9 repositories for EPEL 9 builds, addressing a bug where Rawhide .treeinfo files were missing kernel image information, and removing several underpowered x86_64 hosts from the heavybuilder channel to prevent Out-Of-Memory errors during large builds like Chromium.

Decisions

  • Fedora 45 has been officially released.
  • Several underpowered x86_64 build hosts were removed from the heavybuilder channel to prevent OOM errors during large package builds. (URL)
  • A fix was implemented and backported in Pungi to ensure .treeinfo files contain kernel image information, restoring virt-install functionality for Rawhide. (URL)
  • The EPEL 7 meson tagging order issue will not be fixed because EPEL 7 is End of Life. (URL)

Contribution opportunities

Learn more about the Release Engineering team.

RISC-V

RISC-V

The Fedora RISC-V team successfully finalized and announced the Fedora 45 RISC-V GA images, including Server, Container, and Cloud variants. A major focus this cycle was clarifying kernel recommendations: the ‘Omni’ kernel is highly recommended for most physical hardware to avoid issues like PCIe/NVMe data corruption on JH7110-based boards (e.g., VisionFive 2), while the ‘Generic’ kernel is primarily targeted at QEMU and a select few boards. Meanwhile, the bootstrap of Fedora ELN (Enterprise Linux Next) for RISC-V is making significant progress, with Koji fully configured for ELN and RVA23 channels, and over 140 packages already built. The team is also actively debugging hardware-specific issues, including GCC build hangs on the SpacemiT K3 and a QEMU KVM guest initialization bug.

Decisions

  • The ‘Omni’ kernel is officially recommended for most physical RISC-V hardware (including VisionFive 2) to prevent potential data corruption with certain PCIe/NVMe storage configurations, while the ‘Generic’ kernel is recommended primarily for QEMU.
  • Koji hub policies and channels have been updated to route RVA23-specific builds appropriately, enabling the ongoing Fedora ELN bootstrap.

Contribution opportunities

  • Help is needed to debug and resolve a hard lockup issue occurring during GCC ELN and Rust builds on SpacemiT K3 hardware (disabling Transparent Huge Pages is currently being tested as a workaround).
  • Contributors can assist with upstreaming vendor patches from the Omni kernel to the Mainline kernel to improve out-of-the-box hardware support.
  • Developers familiar with QEMU and KVM can help investigate a guest initialization failure when using -cpu max on RISC-V KVM hosts.

Learn more about the RISC-V team.

Rust

Rust

The Rust group focused heavily on security updates and package rebuilds this week, addressing multiple RUSTSEC advisories across crates like zstd, zip, ruzstd, rustls, and webpki-roots. Additionally, there was a mailing list discussion regarding a request to package crubit for Fedora and EPEL to support Chromium builds, though it faces significant hurdles due to its reliance on nightly Rust and unstable compiler internals.

Decisions

  • The request to package crubit for Fedora to support Chromium builds is currently blocked, as the required cc_bindings_from_rs tool depends on a nightly compiler and unstable compiler internals, which cannot be shipped in Fedora (Mailing List).
  • The effort to update packages to ruzstd v0.9 to address RUSTSEC-2026-0344 has been completed and the tracking ticket is closed (Issue 42).

Contribution opportunities

  • Assist with rebuilding or updating applications not co-maintained by the Rust SIG that vendor affected versions of zstd, zstd-safe, rustls, and webpki-roots (Issue 48, Issue 43, Issue 46).
  • Help port applications currently depending on older versions of zip (v0.6), rustls (v0.21/v0.22), and webpki-roots (v0.25) to their latest secure releases (Issue 47).

Learn more about the Rust team.

Server

Server

The Server Working Group celebrated the release of Fedora 45 Server and immediately began preparing for Fedora 46 by setting up a new testing project. A significant portion of the week was dedicated to the “Strengthening Server Updates” project, focusing on system resilience using LVM snapshots. Following the F45 release, the group closed numerous tracking tickets for system-wide changes and package updates.

In addition, the group discussed ongoing work on Ansible support, deciding to catch up on outstanding tasks over the next two weeks before reconvening on the topic. New contributors joined the meeting and immediately volunteered to help with testing and documentation efforts.

Decisions

  • The group agreed to continue using the ticket system for release testing (starting with Fedora 46), with optimizations to be discussed in the process. (Meeting Log, Mailing List)
  • For the “Strengthening Server Updates” project, the agreed next steps are testing the snapshot procedures, adding them as a step in post-installation, and preparing a Fedora Magazine article. (Meeting Log, Mailing List)
  • Members will use the coming weeks to catch up on outstanding tasks for the Ansible support project, deferring further discussion for 14 days. (Meeting Log)

Contribution opportunities

  • Testers are highly needed for the “System Resilience Using LVM Snapshots” procedures. Findings should be reported in Ticket #272.
  • Contributors are invited to help write a how-to style article for the post-installation section regarding server update resilience (Ticket #271).
  • There is an open opportunity to help draft a Fedora Magazine article about the “Strengthening Server Updates” project.
  • Assistance is welcome for the ongoing Ansible support project, specifically regarding the creation of an Ansible management CLI and configuring CI/CD runners (Ticket #268).

Learn more about the Server team.

Websites and Apps

Websites and Apps

This week, the Websites and Apps team resolved an issue where the x86_64 folder was missing from the Fedora 45 Labs download page by syncing the content and rebuilding the site. The team also successfully closed the F45 beta release tracker and opened tickets for UI improvements, including fixing dark-mode logos on the CoreOS page and improving contrast in the Fedora Media Writer section. In addition, a community member reported that the captive portal check URL is on an HSTS-preloaded domain, which breaks Wi-Fi login detection; the infrastructure team plans to move it to another domain in the future. Finally, a bug in Fedocal where events with past repeat-end dates fail to appear was identified and resolved for a user.

Decisions

Contribution opportunities

  • Review requested for the Fedora Maubot/Zodbot plugin for cookies: PR #257 and PR #161.
  • Help needed to fix missing dark-mode variant logos on the CoreOS page (Work item #439).
  • Help needed to improve the contrast of download items in the Fedora Media Writer section (Work item #438).

Learn more about the Websites and Apps team.

Workstation / GNOME

Workstation / GNOME

A brief 20-minute meeting was held on November 3rd, following up on the agenda from October 27th. The original agenda included topics such as Fedora 45 blockers and exceptions, appstream-data automation, and DNF updating without wheel.

Learn more about the Workstation / GNOME team.

Other Discussions

Other Discussions

  • From F45 onwards: Fedora-maintained (self-updating) hardening…: Chris announced a new self-updating kernel hardening feature available from Fedora 45 onwards. Designed for both beginners and advanced users on GNOME and KDE, it applies security-first configurations automatically, overriding certain defaults like yama-ptrace-enable. Users discussed its interaction with Atomic variants, Toolbox containers, and potential impacts on specific applications, with Chris noting that a new #hardening tag will be used to consolidate feedback.
  • Btrfs-patrol: snapshots before every dnf transaction…: JC shared updates on btrfs-patrol, a snapshot and rollback tool tailored for Fedora’s default Btrfs layout. It automatically takes read-only snapshots before dnf5 transactions and allows for one-command rollbacks while ensuring the restored snapshot has the necessary kernel modules to boot.
  • GitLab access for inactive accounts: Shaun McCance announced that due to Fedora exceeding its seat limit on GitLab, accounts with no activity in the past 12 months will be downgraded to view-only access. This will free up seats for active teams without deleting any data, and edit access can be restored if needed.
  • Proposal: Optional CJK input method support for Fedora’s kmscon console: Skyter Lin proposed adding optional CJK (Chinese, Japanese, Korean) input method support for Fedora’s new kmscon virtual console, having successfully tested Traditional Chinese using uim-fep and m17n. Jocelyn Falempe confirmed the technical feasibility of using Super+Space for toggling and suggested starting by adding a kmscon-uim man page.
  • Some news about the Audinux activity for october: Yann Collette provided an October update for the Audinux repository, highlighting the addition of 29 new audio-related packages and 155 package updates. Notable additions include several AI-generated standalone applications like bytebeat, ibniz-rust, and mx44-rust, which underwent security and performance audits.
  • New packages in Fedora Linux (October 2026): Miroslav Suchý shared a comprehensive list of newly added packages to Fedora Linux during October 2026, generated using the rawhide-changes.py script.
  • F46 Change Proposal: Usermode2 (self-contained): On the devel-announce mailing list, Aoife Moloney shared a Fedora 46 Change Proposal to replace the C implementation of the usermode package with a memory-safe Rust rewrite of its userhelper and consolehelper tools. The rewrite serves as a drop-in replacement while dropping several obsolete standalone GUI tools, and developers discussed ensuring the Rust standard library safely handles the SUID execution environment.
  • Is packaging a fork permissible?: Łukasz Wojniłowicz asked if packaging a fork under the same name as the upstream project is permissible. Developers clarified that while it is allowed and sometimes necessary for dormant projects, the spec file should clearly explain the relationship between the original repository and the fork to avoid confusion.
  • F46 Change Proposal: Libical4 (system-wide): On the devel-announce mailing list, Aoife Moloney announced a Fedora 46 Change Proposal to update the libical library to its 4.x series, which introduces an API/ABI break from the 3.x series. Milan Crha and Michel Lind coordinated the necessary package rebuilds in a side tag, noting that only a subset of dependent packages required direct updates.
  • Heads-up: %gpgverify -> %openpgpverify PRs are coming: Jakub Jelen notified maintainers about upcoming pull requests to migrate packages from %gpgverify to the new %openpgpverify macro, which uses Sequoia’s sqv for upstream source signature verification. He advised maintainers to check if their upstream keys need refreshing or updating to comply with current cryptographic standards.
  • Other discussions included Orion Poplawski checking on a non-responsive maintainer for cmake, Nick inquiring about src.fedoraproject.org UI issues, Dawid Wrobel raising concerns about Btrfs metadata exhaustion defaults, Gordon Messmer offering review swaps for podman-desktop, Nick seeking to co-maintain c-toxcore, Miro Hrončok noting a license change in python-cffi, Benson Muite unretiring python-hl7, the cancellation of a Fedora Council meeting, and Petr Pisar correcting the createrepo_c-devel license.

Orphaning packages

  • Orphaned packages looking for new maintainers (on devel-announce): Several orphaned packages were adopted, including tunneler and openfortivpn, while Dominik Mierzejewski advised against adopting rubygem-drake due to obsolescence.
  • Orphaned – singularity-ce: David Trudgian orphaned singularity-ce as the upstream project reached EOL, recommending apptainer as a suitable replacement.

Package updates

  • libcdio 2.4.0 update comes with new sonames: Adrian Reber announced an upcoming update to libcdio 2.4.0 in Rawhide, which bumps several SONAMEs and requires rebuilding dependent packages in a side tag.
  • Soname bump: libcamera: Milan Zamazal planned an update to libcamera 0.8.0 in Rawhide, noting ABI changes that require rebuilding pipewire-plugin-libcamera, libcamera-apps, and plasma-camera.
  • openapv SONAME bump: Dominik Mierzejewski announced an update to openapv that includes a SONAME bump and API changes, requiring a rebuild of FFmpeg to fix a high-severity CVE.
  • sonivox SONAME bump: Yaakov Selkowitz noted an upcoming update to sonivox 4.0.2, which will involve a side tag rebuild for its dependents.
  • CRI-O v1.37 and Go: Brad Smith reported that CRI-O v1.37.3 now requires Go 1.27.1 or newer, blocking updates on F43 and F44.
  • Heads-up: croaring 5.4.0 coming to Rawhide: Ben Beasley announced an ABI-breaking update for croaring to version 5.4.0, which will be coordinated with updates to python-pyroaring and groonga.

New contributor introductions

  • Aashish Jha: A software engineer at Microsoft working on Azure Confidential VMs, introduced himself and his work packaging azure-protected-vm-secrets as his first contribution to Fedora.
All contribution opportunities

All contribution opportunities

Quality Assurance and testing offer some of the most accessible entry points for community members outside of specific working groups. Contributors can participate in the Linux Kernel 7.3 Test Week and the upcoming KDE Plasma 6.8 Test Week, or help draft test cases for the Fedora Atomic Desktops Test Week. There are also numerous opportunities to test specific system features and provide feedback, such as evaluating “System Resilience Using LVM Snapshots” (Ticket #272), the btrfs-patrol snapshot tool, and the new self-updating kernel hardening feature. Furthermore, testers are needed to reproduce a memory exhaustion bug in Kinoite 44, verify if KDE processes are still crashing on boot, and validate a workaround for an ext4 /boot corruption issue in CoreOS.

For those with skills in technical writing, design, or event organization, there are several ways to make an immediate impact. The community is seeking volunteers to fill Wrangler, Speaker, Design, and Promotion roles for the Virtual F46 Release Party, as well as attendees to connect at SFSCON 2026. Writers can help draft Fedora Magazine articles covering Server Update Resilience and AI in Fedora, or write a how-to guide for post-installation server updates (Ticket #271). Documentation contributors are encouraged to review F45 Release Notes pull requests, replace legacy includes with Antora syntax (Issue #38), and provide feedback on integrating the Design Suite docs. Additionally, general feedback is requested on the proposed transition to Forgejo and agenda topics for the Bootable Image Unification meetings.

Contributors with system administration and infrastructure experience can assist with vital operational tasks, and mentorship is available for newcomers interested in virtualization and infrastructure. Immediate needs include setting up a self-hosted Vagrant registry for the Cloud SIG, configuring Zabbix monitoring for the staging autosign service and Oraculum, and cleaning up NetApp and host storage. Automation enthusiasts can help the COPR team set up PyPI upload automation for copr-cli tags, or assist the Server SIG with creating an Ansible management CLI and configuring CI/CD runners (Ticket #268). There is also an ongoing investigation into persistent login errors on accounts.fedoraproject.org related to FreeIPA OTP modules.

Developers and packagers can contribute by adopting orphaned packages like cmake and c-toxcore, or by helping identify tools that still depend on the legacy DNF4 stack for its planned removal. The Rust SIG needs help rebuilding applications that vendor affected versions of libraries like zstd and rustls, and porting others to secure releases. Web developers can submit fixes for missing dark-mode logos on the CoreOS page and review Maubot plugin pull requests. Finally, systems programmers can tackle complex hardware issues, such as debugging a hard lockup during GCC and Rust builds on RISC-V SpacemiT K3 hardware, or investigating a guest initialization failure on RISC-V KVM hosts.

The post TWIF: November 02 to 08, 2026 appeared first on Fedora Community Blog.

Copr, explained: the sandbox where Fedora packaging starts

Posted by Justin Staging Fedorable on 2026-11-10 08:00:00 UTC
Copr, explained: the sandbox where Fedora packaging starts

In 2017, I wanted a small tool to change my laptop’s screen brightness. I found one that worked, but Fedora did not have an RPM package for it. So I set out to package it myself. Fedora Copr made that first attempt far less stressful. I wrote up that first package at the time: How I created my first RPM package in Fedora. Copr remains one of the most useful tools in the Fedora contribution ecosystem.

This post is the introduction I wish I had read before I started. It explains what Copr is, why packagers and users rely on it, and why its sandbox-like design matters now.

What Copr is 🔗

Copr, short for Community Projects, is a build service. You give it a source RPM (SRPM), and it builds the package and hosts the results in a DNF or YUM repository. Copr runs on Fedora infrastructure. You can use the public instance at copr.fedorainfracloud.org.

If you use Arch Linux, Copr is the closest parallel to the Arch User Repository (AUR). Both are community spaces where people share packages for others to use. The AUR shares build scripts, and you build the package on your own machine. Copr goes a step further. It builds the RPM for you and hosts the repository, so you enable it and install with DNF.

You need a Fedora Account System (FAS) login to create a project. You do not need special approval. You can build for several Fedora releases, EPEL releases, and other targets in one step. One SRPM can produce packages for many releases and architectures.

Why packagers use Copr 🔗

When I started, my biggest question was whether my package would build on the releases I cared about. Koji is Fedora’s official build system, and I used scratch builds there to test. Copr solved a different problem. It let me host the package, install it on my own machine, and share a repository with others before I submitted anything for review.

Koji scratch builds caught a Fedora 27 failure that I fixed before I submitted my package for review. Copr is not a replacement for that process. It is a place to test first.

Copr as an instant enablement path 🔗

Recently, I used Copr to package something new I was working on. I packaged a set of Markdown files, each one an Agent Skill, from the Fedora Agent Skills Library into a single RPM. I published it in the AI/ML SIG Copr project and started sharing it for testing and use.

My plan is to package agent-skills officially in Fedora. Copr made that first step possible because it gave me the fastest path to get an RPM into users' hands. Users got a semi-official channel to install the package now, and I got real feedback while the official process moves along.

Copr as a sandbox 🔗

Copr works well as a sandbox. Several design choices make that true.

  • Projects are separate. Packages in your Copr project do not enter Fedora’s official repositories. Your experiments stay in your own repository.

  • Packaging rules are relaxed. Copr packages do not have to follow the Fedora Packaging Guidelines. The guidelines are still recommended, but you can test ideas before you meet every rule.

  • Projects can expire. You can set a project to delete itself after a number of days. This suits short tests and one-off experiments.

  • Old builds are removed. By default, Copr keeps one build per package and deletes the others after 14 days. Projects on the newer Pulp backend keep the five most recent successful builds per package instead, so test projects do not grow forever.

A sandbox does not mean anything goes. Copr is Free Software, and its repositories are signed. However, the Copr maintainers do not review every package. Before you install a package from a Copr project, check who maintains it. If you can, look at the SRPM and spec file. Projects distributed in Copr must also follow Fedora’s license rules.

Where Copr fits in the innovation discussion 🔗

Fedora is discussing a Council proposal for an Innovation Lifecycle. The proposal includes a "sandbox stage" for experimental work that is too large for a single change proposal. One of its stated goals is to isolate risk. Experiments should be able to break without affecting the main distribution or the people who depend on it.

The proposal also notes that it does not yet define standard sandbox infrastructure. Copr is not part of that proposal. It already shows what a low-risk space for experiments can look like. Work stays separate from official releases, feedback comes quickly, and strong packages can follow a path into Fedora. I hope we keep that spirit as the larger discussion moves forward.

Packaging as a fallback 🔗

Distribution methods will change over time. Right now, RPM packaging works well. It is tested, proven, and well understood by Fedora contributors and users. When we do not know how to share something new, RPM packaging is a path we can always fall back on. It provides versioning and a distribution mechanism for large varieties of software. Copr makes that RPM packaging fallback fast.

Getting started 🔗

You need a FAS account, a project, and an SRPM or RPM spec. These commands create a project for Fedora Rawhide and submit a build:

copr-cli create --chroot fedora-rawhide-x86_64 my-first-project
copr-cli build my-first-project ./my-package.spec

For more detail, read the Copr user documentation.

Final thoughts 🔗

Copr gave me a low-risk way to learn packaging, and it can do the same for you. If you have a package that is too early for Fedora, build it in Copr, share it, and learn from the results. Thank you to everyone who maintains Copr and helps packagers use it.


Featured image generated by LLM-gen-AI using the OpenAI image API.

Server reboots

Posted by Fedora Infrastructure Status on 2026-11-06 21:00:00 UTC

We will be rebooting our vpn hub / smtp gateway / bastion hosts in order to apply a new kernel to mitigate possible CVEs.

The outage should hopefully only take a few minutes.

forge.fedoraproject.org is down

Posted by Fedora Infrastructure Status on 2026-11-06 11:00:00 UTC

The forge.fedoraproject.org is down because of space issue. We are currently working on fixing it. You can watch the progress in https://matrix.to/#/#forge:fedoraproject.org

What’s New for Fedora Atomic Desktops in Fedora Linux 45

Posted by Fedora Magazine on 2026-11-03 14:28:00 UTC

Fedora 45 is now available! 🎉 So let’s see what this new release for the Fedora Atomic Desktops variants includes for Silverblue, Kinoite, Sway Atomic, Budgie Atomic and COSMIC Atomic.

Changes for all Atomic Desktops

Completed the migration to the new Fedora forge

Everything related to the Atomic Desktops now resides in the atomic-desktops organization.

The only remaining repo on GitLab.com/fedora is the one used to build the unofficial bootable container images (gitlab.com/fedora/ostree/ci-test). The migration of this repo will occur in the future, as well.

Anaconda Web UI

The Atomic Desktops installer ISOs now use the new Anaconda WebUI. This follows the same change that occurred for Fedora Workstation 42 and Fedora 43 Spins.

This also enables remote installation of a system using a Web browser on another machine over HTTPS.

See the Fedora Change pages for the switch to the WebUI and for Web based remote installations.

Installer images (ISO) and disk images built by Image Builder

The installer images (ISO) are now built by Image Builder. While there should not be any immediate visible changes, this will help us move to the bootable container images in the future.

This also enables us to offer pre-installed disk images for Silverblue and Kinoite. Those images are currently in preview and only those variants are covered for now. They are the only ones with a first boot experience from a disk image.

See the Fedora Change page for further information.

General Fedora changes worth noting

The following changes are part of the general set of changes that come with Fedora Linux 45 and are worth noting for Atomic Desktops users:

What’s new in Silverblue

Fedora Silverblue comes with the latest GNOME 51 release.

For more details about the changes alongside GNOME 51, see What’s new in Fedora Workstation 45 on the Fedora Magazine.

What’s new in Kinoite

Fedora Kinoite ships with Plasma 6.7, Frameworks 6.31 and Gear 26.08.

Plasma 6.8 is expected to land right after the release.

See also What’s new in Fedora KDE Plasma Desktop 45 on the Fedora Magazine.

What’s new in Sway Atomic

Fedora Sway Atomic comes with the latest 1.12 Sway release.

What’s new in Budgie Atomic

Fedora Budgie Atomic comes with the brand new version 10.10.3 of Budgie Desktop: New Favorites in Budgie Menu, re-introduced Keyboard applet with Wayland support, massive improvements to our desktop view, primary monitor selection, and more! See the 10.10.3 Budgie release announcement.

What’s new in COSMIC Atomic

Fedora COSMIC Atomic comes with the 1.10.0 release of the COSMIC desktop.

Universal Blue, Bluefin, Bazzite, Aurora and secureblue

Our friends in the Universal Blue project (Bazzite, Bluefin, Aurora) have prepared the update to Fedora 45. Look for upcoming announcements in their Discourse.

As always, I heavily recommend checking them out, especially if you feel like some things are missing from the Fedora Atomic Desktops and you depend on them (NVIDIA drivers, extra media codec, out of tree kernel drivers, etc.).

If you have an interest in more security focused variants, I recommend taking a look at the secureblue project.

What’s next

Roadmap to Bootable Containers and bootc / CoreOS / Atomic unification

A lot of work is happening to make the transition to Bootable Containers as smooth as possible for our existing users. You can look at the roadmap for this transition at atomic-desktops#26.

Most of the progress in this release cycle was (again) focused on getting our bootable container images ready for general consumption in Fedora. A part of this work is being able to build them reliably in the Fedora Infra.

The people involved in the bootc, CoreOS and other Atomic variants are working on this effort as part of the new Atomic SIG. See atomic#137 and the project board.

Making it easier to derive images into Fedora Remix images

Work is in progress to make it easier to create derived container images from the Fedora Atomic Desktops images, notably in order to comply with the logo and branding policy.

Once this is ready, we may start publishing “Fedora Remix” branded container images of the Fedora Atomic Desktops. Those images will not include official Fedora branding and will thus be better suited for projects that want to layer their changes on top.

See atomic-desktops#125 and atomic-desktops#132.

Helping us with a few nasty bugs

If you have an interest in contributing to Fedora Atomic Desktops, here are some bugs that we will have to fix in the short term. We would greatly appreciate help with the following issues from the ticket tracker:

  • Fixing root mount options (atomic-desktops#72): This is a long standing and mostly invisible bug that impacts performance.
  • Moving away from nss-altfiles (atomic-desktops#108): This is another long standing source of issues that new users regularly face.

Where to reach us

We are looking for contributors to help us make the Fedora Atomic Desktops the best experience for Fedora users. The following are Matrix rooms that may be of interest to potential contributors:

How to Rebase to Fedora Linux 45 on Silverblue

Posted by Fedora Magazine on 2026-11-03 14:00:00 UTC

Fedora Silverblue is an operating system for your desktop built on Fedora Linux. It’s excellent for daily use, development, and container-based workflows. It offers numerous advantages such as being able to roll back in case of any problems. If you want to rebase to Fedora Linux 45 on your Fedora Silverblue system, this article tells you how. It not only shows you what to do, but also how to revert things if something unforeseen happens.

Update your existing system

Prior to actually doing the rebase to Fedora Linux 45, you should apply any pending updates. Enter the following in the terminal:

$ rpm-ostree update

or install updates through GNOME Software and reboot.

Note

rpm-ostree is the underlying atomic technology that all the Fedora Atomic Desktops use. The techniques described here for Silverblue will apply to all of them with proper modifications for the appropriate desktop.

Rebasing using GNOME Software

GNOME Software shows you that there is new version of Fedora Linux available on the Updates screen.

First thing to do is download the new image, so select the Download button. This will take some time. When it is done you will see that the update is ready to install.

Select the Restart & Upgrade button. This step will take only a few moments and the computer will restart when the update has completed. After the restart you will end up in a new and shiny release of Fedora Linux 45. Easy, isn’t it?

Rebasing using terminal

If you prefer to do everything in a terminal, then this part of the guide is for you.

Rebasing to Fedora Linux 45 using the terminal is easy. First, check if the 45 branch is available:

$ ostree remote refs fedora

You should see the following in the output:

fedora:fedora/45/x86_64/silverblue

If you want to pin the current deployment (meaning that this deployment will stay as an option in GRUB until you remove it), you can do this by running this command:

# 0 is entry position in rpm-ostree status
$ sudo ostree admin pin 0

To remove the pinned deployment use the following command:

# 2 is entry position in rpm-ostree status 
$ sudo ostree admin pin --unpin 2

Next, rebase your system to the Fedora Linux 45 branch.

$ rpm-ostree rebase fedora:fedora/45/x86_64/silverblue

Finally, the last thing to do is restart your computer and boot to Fedora Linux 45.

How to roll back

If anything bad happens (for instance, if you can’t boot to Fedora Linux 45 at all) it’s easy to go back. At boot time, pick the entry in the GRUB menu for the version prior to Fedora Linux 45 and your system will start in that previous version rather than Fedora Linux 45. If you don’t see the GRUB menu, try to press ESC during boot. To make the change to the previous version permanent, use the following command:

$ rpm-ostree rollback

That’s it. Now you know how to rebase Fedora Silverblue to Fedora Linux 45 and roll back. So why not do it today?

FAQ

Because there are similar questions in comments for each blog about rebasing to newer version of Silverblue I will try to answer them in this section.

Question: Can I skip versions during a rebase of Fedora Linux? For example from Fedora Silverblue 42 to Fedora Silverblue 45?

Answer: Although it could sometimes be possible to skip versions during rebase, it is not recommended. You should always update to one version prior (42->43->44->45 for example) to avoid unnecessary errors.

Question: I have rpm-fusion layered and I get errors during rebase. How should I do the rebase?

Answer: If you have rpm-fusion layered on your Silverblue installation, you should do the following before rebase:

$ rpm-ostree update --uninstall rpmfusion-free-release --uninstall rpmfusion-nonfree-release --install rpmfusion-free-release --install rpmfusion-nonfree-release

After doing this you can follow the guide in this blog post.

Question: Could this guide be used for other ostree editions (Fedora Atomic Desktops) as well like Kinoite, Sericea (Sway Atomic), Onyx (Budgie Atomic),…?

Yes, you can follow the Rebasing using the terminal part of this guide for every Fedora Atomic Desktop. Just use the corresponding branch. For example, for Kinoite use fedora:fedora/45/x86_64/kinoite

Migrating away from unmaintained NetworkManager VPN plugins (vpnc and fortisslvpn)

Posted by Fedora Magazine on 2026-11-03 14:00:00 UTC

Two legacy NetworkManager VPN plugins—NetworkManager-vpnc and NetworkManager-fortisslvpn—are retiring and will be obsolete, starting in Fedora Linux 45. This is part of ongoing system maintenance and security cleanup.

If you use Virtual Private Networks (VPNs) to connect to remote workplace or enterprise networks, take note of this upcoming change in NetworkManager package availability.

This article contains information about what you need to know. It covers why these plugins are being retired, how this affects your current setup, and how to migrate your VPN connections to actively supported alternatives.

Why retire these plugins?

Both NetworkManager-vpnc and NetworkManager-fortisslvpn are unmaintained.  Furthermore, the published issues allow LPE through malicious VPN profiles as well as legacy privilege-handling bugs in older VPN helper scripts, which pose security risks to local systems. Further information is available in this blog post.

To ensure Fedora Linux users remain secure and backed by active upstream maintainers, the Fedora Engineering and Steering Committee (FESCo) and NetworkManager maintainers agreed to retire these unmaintained plugins in favor of modern, secure alternatives already available in Fedora repositories.

Overview of changes and migration paths

Retired PluginProtocol / Network TypeMigration TargetStatus & Recommendation
NetworkManager-fortisslvpnFortinet SSLVPNNetworkManager-openconnectopenconnect supports the older PPP-based Fortinet protocols natively and is actively maintained.
NetworkManager-vpncCisco IPsec (IKEv1)NetworkManager-libreswanlibreswan handles the same IKEv1 protocol family and is directly maintained by the NetworkManager team.

Step-by-Step Migration Guide

1. Fortinet SSLVPN Users (fortisslvpn → openconnect)

If you currently rely on Fortinet SSLVPN tunnels, switch to the NetworkManager-openconnect plugin.

  1. Install the OpenConnect NetworkManager plugin:
    Bash
    sudo dnf install NetworkManager-openconnect

  2. Open Settings → Network (or KDE System Settings → Connections).
  3. Click + to add a new connection and select Multi-protocol VPN client (openconnect).
  4. Set the protocol dropdown to Fortinet SSL VPN, input your gateway address and authentication details, and save the profile.
  5. Once verified, remove the legacy package:
    Bash
    sudo dnf remove NetworkManager-fortisslvpn

2. Cisco IPsec / IKEv1 Users (vpnc → libreswan)

If you use legacy Cisco IPsec VPN tunnels, migrate your connections to NetworkManager-libreswan.

  1. Install the Libreswan NetworkManager plugin:
    Bash
    sudo dnf install NetworkManager-libreswan

  2. You may need to create file /etc/ipsec.d/ikev1.conf with this content:
    config setup
    ikev1-policy=accept

    This enables the deprecated IKEv1 protocol. Then restart ipsec.service. Note that the ipsec.service must be running, or the activation will fail.
  3. In your desktop network settings, add a new IPsec based VPN connection and select Type=IKEv1.
  4. Enter your gateway IP/domain, the group name enclosed in square brackets (e.g ‘[group]’), group password (pre-shared key), and user credentials corresponding to your previous vpnc configuration. You might have to tune IKE/ESP proposals, DH/PFS settings and routing requirements, which can be obtained from the gateway’s configuration and old vpnc logs.
  5. Test the connection, then remove the legacy package:
    Bash
    sudo dnf remove NetworkManager-vpnc

What happens during upgrades?

  • Fedora 43 & 44: Current installations retain their installed plugins so active connections will not abruptly break. However, there will be no further feature or security updates issued for vpnc or fortisslvpn.
  • Fedora 45+: The legacy packages are officially obsoleted by NetworkManager. An upgrade to Fedora 45 automatically removes NetworkManager-vpnc and NetworkManager-fortisslvpn, if they are installed.

We strongly encourage all users relying on these VPN types to test and migrate their connection profiles to openconnect or libreswan as soon as possible!

What's New in Fedora Workstation 45

Posted by Fedora Magazine on 2026-11-03 14:00:00 UTC

Fedora Workstation features the latest six months of meticulous polish, under-the-hood responsiveness, and security hardening for F45, based on GNOME 51. Whether you are multitasking across monitors, managing daily appointments, or organizing large sets of files, GNOME 51 brings thoughtful refinements to your daily workflow on Fedora Workstation.

Silky-Smooth Responsiveness: Reworked Frame Scheduling

One standout improvement in GNOME 51 is a reworked frame scheduling and frame delivery system in Mutter. Animations, window snapping, and desktop transitions now hold a rock-steady frame rate even when the CPU and GPU are under heavy compile or gaming loads.

In tandem with this, GNOME streamlined its graphics pipeline by retiring legacy NVIDIA proprietary interfaces in favor of the standard GBM memory management path. This makes Wayland sessions cleaner, faster, and more uniform across all hardware.

Everyday App Polish

Files (Nautilus) Gets Quality-of-Life Upgrades

Files has picked up several subtle but indispensable touches:

  • Drag-and-Drop Counter Badge: When selecting and dragging multiple files, a small badge now shows the exact count of items you're moving.
  • Non-Blocking Operations: Large or slow directory reloads no longer freeze the interface, resulting in a snappier file management experience.
  • Notification Grouping: Grouping status and operation notifications together now keeps your notification tray tidy.

Calendar Rebuilt for Speed

Calendar feels faster than ever. The entire view-rendering engine was overhauled under the hood. This dramatically cut down the lag when scrolling through dense schedules in Month View. Reorganization within the event editor now presents a cleaner Notes section and native recognition of modern video conference links.

Revamped File Previewer

The quick-look File Previewer received a top-to-bottom redesign built on modern GTK 4 and libadwaita. It now seamlessly matches your desktop theme, respects Dark Style, handles fractional display scaling crisper than before, and properly previews high-resolution images at their actual native size.

Deeper Security: Next-Generation Secret Storage with oo7

Security underpins everything in Fedora Workstation. GNOME 51 introduces oo7, a modern Secret Service provider written from scratch to safely store application passwords, API tokens, and credentials.

Fedora Workstation is replacing legacy keyring daemons with a compartmentalized, sandboxed service. This provides even stronger defense against rogue applications attempting to peek at cached user credentials.

Accessibility and Navigation Upgrades

  • Keyboard-Driven Screenshots: You can now adjust screenshot selection boxes entirely with your arrow keys (
    Alt
    to move the selection,
    Shift
    /
    Ctrl
    for coarse/fine resizing, and
    R
    to reset).
  • Extended Reduced Motion: Toggling the Reduced Motion accessibility option now softens animations across more core widgets and Shell elements than ever before.
  • Reorganized Settings: The About (System Details) panel now includes a direct button to view the release notes for your running GNOME version, alongside a revamped fingerprint enrollment flow.

Upgrade or Try Fedora Workstation

If you’re already running Fedora, upgrading through GNOME Software or via the terminal with

dnf system-upgrade
will bring you right into GNOME 51. For clean installs, check out the Fedora Workstation live media at getfedora.org.

Share your favorite new feature or thoughts on the release over at the Fedora Discussion forum!

Disclaimer: Google Gemini, using the GNOME 51 release notes, assisted in the creation of this article. It was reviewed by humans before publishing. No apparent hallucinations were noted, however ,some content was not included.

Please read the GNOME 51 release notes for even more cool features that you can enjoy on Fedora Workstation as part of the F45 release.

What’s New in Fedora KDE Plasma Desktop 45

Posted by Fedora Magazine on 2026-11-03 14:00:00 UTC

KDE Plasma 6.8 was released on KDE's 30 year anniversary and we are proud to have it be the star of Fedora KDE Plasma Desktop Edition 45.

The Fedora KDE Plasma Desktop Edition is well suited for many needs. It combines the reliable and trusted Fedora Linux base with the KDE Plasma Desktop environment. It provides a selection of KDE applications that are simple by default, but powerful when needed.

KDE Plasma 6.8

KDE developers continue to release new features, fix bugs and fine-tune the desktop experience to improve on the now well-established foundation of Plasma 6. There have been two KDE Plasma releases since our last Fedora KDE Plasma Desktop Edition shipped. Some of the new features and updates include:

New Features

  • Per-screen virtual desktops: After 21 years per-screen virtual desktops have finally arrived!
  • Test your microphone volume: Stop wondering if it’s your microphone or an app that’s misbehaving.
  • Press-and-hold for special characters: With Plasma’s virtual keyboard enabled, press and hold a key to type special characters related to it.
  • Light/dark mode toggle: A quick toggle in the system tray to switch between light and dark Global Themes immediately.
  • “Background Apps” in the System Tray: The system tray now shows apps using the newer “Background Apps” system, which is more common for apps using the Flatpak package format.

Updated Features

  • Better Accessibility: a new “dwell clicker” feature can send a mouse click when the pointer stops moving. Designed especially for users with mobility issues.
  • Remote Desktop: Much better performance and quality, bi-directional clipboard synchronization, exclusive mode and overall polish to the experience.
  • Printing: Now the System Tray icon for printers shows the number of active jobs in a little badge.
  • Faster virtual desktop switching in the Overview: When you press "Meta + W" to open the Overview screen, Plasma now lets you switch virtual desktops simply by scrolling or pressing the "Page Up" or "Page Down" keys.
  • Easier to compare different time zones: The Digital Clock widget lets you add multiple time zones and quickly compare them.

Theming

  • Oxygen: For KDE’s 30th anniversary the Oxygen theme is back and brought up to par.
  • Breeze: The default Breeze theme also continues to evolve, now featuring rounded list and grid view highlights for many applications, and visible click effects for menu items.
  • Union: Plasma’s all-new Union theming system streamlines theming by making it possible to style Plasma, QtQuick apps, and QtWidgets apps all with a single set of easy-to-write CSS.

And More ...

There is so much new stuff since our last Fedora KDE Plasma Desktop Edition was released. Check out the full release announcements for Plasma 6.7 and Plasma 6.8.

Fedora Linux 45 general updates

Some broader changes in Fedora Linux also directly impact Fedora KDE Plasma Desktop Edition, notably:

  • Updated Podman: Podman 6 includes new features, but also significant API and CLI breaking changes. Depending on how you use Podman, this change may significantly affect you. The Podman 6 change proposal has information on what is affected.
  • NetworkManager VPN: NetworkManager-vpnc and NetworkManager-fortisslvpn are not in Fedora 45. If you already have them installed and are updating to Fedora 45, NetworkManager will obsolete and remove them. Users still using them should migrate their connection profiles to openconnect or libreswan.
  • Lazarus with multiple widget sets: The lazarus-ide now comes with a Qt6 option in lazarus-ide-qt6.
  • Updated IBus: IBus now supports the ISO latch and shift states of XKB key-maps in Wayland desktop environments like KDE, Sway, Hyprland, COSMIC.
  • DRM Panic Frontend: The DRM Panic Frontend provides users with a user-friendly interface for understanding kernel panic information and facilitates bug reports.

Wrap-up

The Fedora KDE SIG hopes that you’ll find Fedora KDE Plasma Desktop 45 to be a wonderful experience. When you’re ready to try it, click here for download links and verification instructions. If you would like to learn more, check out the Fedora KDE Plasma Desktop website.

Announcing Fedora Linux 45

Posted by Fedora Magazine on 2026-11-03 14:00:00 UTC

The Fedora Project is pleased to announce the release of Fedora Linux 45!

Whether you use Fedora on your desktop, server, edge device, or cloud instance, Fedora Linux 45 brings polished desktop upgrades, powerful new installer features, and updated toolchains.

Every Fedora release is a major community effort - thank you to everyone in our community who helped build, test, and package this release!

Upgrade

If you are already running Fedora Linux, upgrading to the new release is simple. Our user documentation shows you exactly how to start enjoying F45 easily.

Or, start fresh

Looking for a clean install or setting up a new device? Head over to getfedora.org to grab installation media for our flagship Editions:

  • Fedora Workstation
  • Fedora KDE Plasma Desktop
  • Fedora Server
  • Fedora Cloud
  • Fedora CoreOS & Fedora IoT

You can also explore our Atomic Desktops (including Silverblue, Kinoite, and Sericea) or choose from alternate desktop options via Fedora Spins (such as Cinnamon, Xfce, MATE, or COSMIC).

What’s new in Fedora Linux 45?

We have a lot of excellent content under the hood in this release. Below is only a snapshot of them. Take a spin through our release notes for individual changes, and details on each change. 

One of the biggest highlights in Fedora Linux 45 is integrated support for Stratis storage right inside the Anaconda installer.

Stratis brings modern enterprise storage features to local storage while wrapping device-mapper, XFS, and LUKS in an easy-to-use interface. These features include thin provisioning (over-provisioning), storage pooling, dynamic filesystem sizing, snapshots, and encryption.

  • GUI Installs (Web UI & Cockpit Storage): When performing custom partitioning during installation, you can launch the Cockpit storage module directly from Anaconda. From there, you can build Stratis pools across one or more physical drives and create dynamic / and /home filesystems on demand.
  • Automated Installs (Kickstart): For system administrators and automated deployments, Anaconda now supports --type=stratis with autopart, alongside dedicated stratispool and stratisfs kickstart commands.

Read more details about this really cool change in this article.

Desktop Highlights & Ecosystem Updates

  • Latest Desktop Environments: Updated desktop stacks across GNOME, KDE Plasma, and community spins bring improved performance, refined Wayland support, and better fractional scaling. 
  • Developer Toolchains: Updated development tools and runtime libraries ensure you have access to the latest language features, compiler optimizations, and core system utilities.
  • System & Kernel Enhancements: Powered by recent Linux kernel releases, Fedora 45 includes broad hardware support, improved power management for laptops, and enhanced container performance.

If you encounter any bugs or unexpected behavior after upgrading or installing, help is close at hand:

  • Visit the Ask Fedora discussion forum to ask questions and find answers.
  • Check the Common Issues section on Ask Fedora to see known issues and workarounds tracked during the release cycle.

Important: Two legacy NetworkManager VPN plugins—NetworkManager-vpnc and NetworkManager-fortisslvpn—are retiring and will be obsolete, starting in Fedora Linux 45. Please read this article for information on what you need to do to migrate your VPN connections to supported alternatives.

Let's keep the conversation going

We’d love to hear how Fedora Linux 45 works for you! Share your thoughts, post your desktop setups, or say hi to fellow community members over on Fedora Discussion.

Enjoy Fedora Linux 45!

Fedora Copr outage - updating servers

Posted by Fedora Infrastructure Status on 2026-11-03 09:00:00 UTC

There will be a Fedora Copr outage while we upgrade infrastructure machines to the latest Copr packages.

The build queue processing will be stopped during the outage, and the Frontend/Web-UI will be down most of the time (no new tasks accepted). The DNF packages and repositories (hosted on copr-backend …

Fedora Asahi Remix 45 is now available

Posted by Fedora Magazine on 2026-11-02 14:00:08 UTC

We are happy to announce the general availability of Fedora Asahi Remix 45. This release brings Fedora Linux 45 to Apple Silicon Macs.

What's included

Fedora Asahi Remix is developed in close collaboration with the Fedora Asahi SIG and the Asahi Linux project. This release incorporates all of the exciting improvements brought by Fedora Linux 45. Like previous releases, Fedora Asahi Remix 45 supports Apple M1 and M2 systems. In addition, this release includes out of the box initial support for Apple M3, M3 Pro and M3 Max. Asahi Linux upstream now officially supports these new systems. The GPU drivers enabling performant 3D acceleration on the M3 systems are not included at this point. They will be available via a Mesa update in the future.

Fedora Asahi Remix offers KDE Plasma 6.8 as our flagship desktop experience. All of the new and exciting features brought by Fedora KDE Plasma Desktop 45 are included.

A GNOME variant is also available, featuring GNOME 51, with both desktop variants matching what Fedora Linux offers. Fedora Asahi Remix also provides a Fedora Server variant for server workloads and other types of headless deployments. Finally, we offer a Minimal image for users that wish to build their own experience from the ground up.

Installation

You can install Fedora Asahi Remix today by following our installation guide. Follow the usual Fedora Linux upgrade process for existing systems running Fedora Asahi Remix 43 or 44. Upgrades via GNOME’s Software application are unfortunately unavailable. Either KDE’s Plasma Discover or DNF’s System Upgrade command must be used.

Contacts

Please report any Remix-specific issues in our tracker, or reach out in our Discourse forum or our Matrix room for user support.

New badge: Let's have a party (Fedora 45) !

Posted by Fedora Badges on 2026-10-27 17:31:42 UTC
LetYou attended the F45 Virtual Release Party!

DevConf US 2026: Lessons Learned About Reaching Students in Open Source & Linux

Posted by Justin Staging Fedorable on 2026-10-27 08:00:00 UTC
DevConf US 2026: Lessons Learned About Reaching Students in Open Source & Linux

Walking up to the Fedora & CentOS booth on the first day of DevConf US in Boston, I was not quite sure what to expect. Although I have attended the Czech Republic variant of DevConf several times, this was my first time attending the US event. I was there as part of Red Hat’s joint Fedora and CentOS community presence. What I found over those two days was not just a chance to hand out stickers and talk to Fedora Linux users. It was a useful reminder in what the Fedora event strategy needs to become.

The setting: Red Hat tech on a university campus 🔗

DevConf US is a community conference focused on developers and Red Hat technologies. Being held on the Boston University campus during the academic semester meant we knew we would see students. What I did not fully anticipate was how the increased student presence here would reshape what I thought our booth should accomplish.

Alongside my colleagues Shaun McCance, Matthew Miller, Amy Marrich, and To Hung Sze, we staffed a joint Fedora and CentOS table. We kept the booth table light, compared to other events. We did not have any laptop demos, elaborate staging, or any fancy technical displays. We brought ourselves and our trusty Pelican event box full of stickers, lanyards, pins, and swag.

Meeting the "Ubuntu is Linux" generation 🔗

Most people who stopped by the table already knew Fedora, or at least recognized the logo. Most were students, but not all. We also met faculty members, industry professionals, and contributors to other open source projects. However, there was an unmistakable pattern among the students who approached us. For nearly all of them, their first real exposure to Linux happened in university computer science labs. And in university labs, Ubuntu is almost universally the default.

For these students, Ubuntu was not simply a distribution preference. For them, Ubuntu was Linux.

What surprised me most was that they were not defensive about it. They were genuinely curious. They wanted to understand what else was out there, how different systems fit together, and why alternative distributions mattered. The subsequent conversations with those students are some of the most interesting, fun conversations to have at a Fedora booth.

Upstream at the mouth of the river 🔗

That curiosity opened the door to talk about Fedora’s foundational place in the broader Linux ecosystem. When you use Fedora, you are standing directly at the upstream source of enterprise Linux everywhere.

For the curious, the pitch goes something like this. Every three years, Fedora branches to become the foundation for CentOS Stream, which in turn feeds directly into Red Hat Enterprise Linux (RHEL). However, the reach does not stop with Red Hat products, which is often unknown to most students. Downstream enterprise rebuilds like AlmaLinux and Rocky Linux trace their lineage back through CentOS Stream to Fedora. Furthermore, hyperscalers stand out as interesting downstream operating systems too. For example, Amazon Linux is derived from Fedora Linux. And this year, Microsoft announced that Azure Linux, their custom hypervisor container OS, will base its future architecture on Fedora.

So, when you study and use Fedora, you are not just learning another distribution. You are standing at the mouth of the river. You see the innovations before they flow into every major cloud provider and enterprise datacenter in the world.

The missing on-ramp 🔗

The students understood that value proposition immediately. They grasped the architectural power of being upstream. However, the conversations that truly resonated were not about packaging flags or kernel versions. They were about careers.

Students were asking how to build practical skills, how to level up beyond coursework, and what industry engineering teams actually look for. A handful asked specifically about how to contribute to open source and get involved with Fedora.

That is where I realized what our booth was missing. We had no clear call to action.

We could explain the architecture, and we could illustrate the ecosystem on a whiteboard, but we could not smoothly shepherd someone from curiosity to contribution. We lacked a concrete on-ramp. We had no printed guide explaining the first three steps to take after leaving the venue. We had no five-minute interactive exercise someone could complete right at the table to earn something tangible. Instead, we offered a sprawling overview of "everything you can do in Fedora," which is paralyzing when you are just getting started.

What hackathons taught me about student engagement 🔗

Years ago, as a student at RIT and a Fedora Ambassador, I staffed more than a few Fedora booths at collegiate hackathons like HackMIT and Bitcamp. Back then, I learned a vital lesson about engaging students: they need hands-on, achievable activities.

Students need something doable, self-contained, and repeatable. Most importantly, they need something they can earn. A unique reward, like an event badge or a milestone achievement, creates an enduring memory. A standard sticker gets lost in a backpack; a challenge you solved at a booth creates a personal reason to stay connected to the community.

Modernizing our student event strategy 🔗

Executing a commercial trade-show booth strategy at a student-heavy venue does not work. Commercial attendees often browse passively for vendor solutions; students are actively planning their futures and want to understand how distributed engineering collaboration functions in the real world. Free Software and open source are precisely that, but we have to frame them to meet their goals.

If we want to translate curiosity into long-term community contributors, our playbook needs three tangible upgrades:

  • Tailored on-ramp materials: Brief, well-structured guides that explain what our sub-projects do and provide clear first tasks for beginners.

  • Audience-specific talking points: Equipping booth ambassadors with prompts geared toward early-career engineers, highlighting the practical career value of public upstream contributions.

  • Interactive booth challenges: Short, five-minute exercises that allow attendees to make a small contribution, file a test ticket, or solve a puzzle right at the table.

So, should Fedora & CentOS return to DevConf US? Absolutely. DevConf US is a fantastic venue, but next time we must arrive prepared for the audience in the room. The curiosity is already there. We just need to build the bridge that lets them cross over into upstream work.

scraper attack

Posted by Fedora Infrastructure Status on 2026-10-26 08:00:00 UTC

Scrapers are DDOsing version fedoraproject applications.

We are working to mitigate things. Some endpoints may be unavailable as we work to mitigate the attack.

Modernizing the console with kmscon

Posted by Fedora Magazine on 2026-10-19 08:00:00 UTC

For decades, the Linux virtual console has relied on the kernel fbcon driver, to draw the framebuffer, to manage fonts, and to handle keyboard layout. Starting with Fedora 45, we’re switching to a userspace utility called kmscon. Depending on your usage of virtual console, this may impact your workflow.

If you’re not a developer or a system administrator, chances you probably never heard about fbcon or virtual terminal (VT), in this case you’re probably not impacted.

You can still read the rest if you’re curious about minimal text interfaces, and maybe you’ll start using it.

How to use the virtual console

Most of the graphic sessions runs in tty1 or tty2. So press Ctrl+Alt+F3 to switch to tty3, and you will get a login prompt. This is the virtual console we’re talking about. To go back to your graphic session, press Ctrl+Alt+F1 (or F2 or F7 depending on your desktop environment).

Why is kmscon replacing fbcon ?

The legacy fbcon driver runs directly in the kernel space, and has significant drawbacks:

  • Security: Each bug in fbcon can be exploited in the kernel directly, and each crash is a kernel panic.
  • Keyboard layout: The keyboard layouts supported by the kernel are different from what userspace is using. So when you choose the keyboard layout in the anaconda installer, it tries to find the kernel layout that is as close as possible to the chosen layout.
  • Fonts: fbcon only uses bitmap fonts, which look small on a High DPI display, and you can’t resize them at runtime. They have limited unicode support. Kmscon can use freetype, and render all monospace fonts.
  • Scrolling: fbcon does not support scrolling anymore, due to a CVE.
  • Mouse: fbcon does not have mouse support, it can be added with gpm, but is a bit clumsy. Kmscon uses a transparent hardware cursor when available, and has basic mouse support.
  • Fbdev: fbcon relies on the old fbdev interface, but all GPU drivers are now using drm. Switching to kmscon allows dropping the fbdev emulation layer in the kernel.

What this will change for users and administrators ?

  • Kmscon uses pseudo-tty (pts) devices. So when you run tty it returns /dev/pts/0 instead of /dev/tty1, like when you use a graphic terminal. So you will need to update all scripts or configuration that use this information.
  • Kmscon uses the exclusive drm interface to the GPU to draw the terminal. If you want to run a graphic session or a program that wants to use the GPU, it won’t work like it used to with fbcon. The reason is that fbcon runs in the kernel and can let any userspace application take the GPU. Kmscon can’t do that, so you have to tell it to release the GPU. This is done with a script called kmscon-launch-gui. For example, to start a graphic session you can run
    kmscon-launch-gui kmscube -c 100
    or
    kmscon-launch-gui startx
  • Kernel messages: By default the kernel error/warning messages are visible in tty1. It can be annoying when it mixes with what you are typing. You can read the messages with dmesg -w, or have a dedicated tty that runs
    kmscon --vt=%I --no-switchvt --oneshot --login -- dmesg -w
  • Kernel fonts: The setfont command has no effect on kmscon. Kmscon uses the built-in unifont or freetype if it’s available. You can read below how to configure it. kmscon can also use psf fonts, if you want the exact same looking as fbcon.
  • Keyboard layout: The loadkeys command has no effect on kmscon. Instead, kmscon listens to localectl dbus, and updates the keyboard layout accordingly. So, to change layout, run
    localectl set-keymap us
  • Kmscon replaces the default console in F45, for tty1-6. If you want to keep a tty using fbcon, just in case, you can run
    sudo systemctl mask kmsconvt@tty5 && sudo systemctl enable --now getty@tty5
    Then pressing Ctrl+Alt+F5 switches to your good old fbcon console.

Default kmscon shortcuts

  • Zoom in: Ctrl++, Ctrl+WheelUp
  • Zoom out: Ctr+-, Ctl+WheelDown
  • Rotate the terminal: Super++, Super+-
  • Scroll up: Shift+UpArrow, Shift+PageUp, Mouse Wheel Up
  • Scroll down: Shift+DownArrow, Shift+PageDown, Mouse Wheel Down
  • Copy/paste: select with the mouse, or select a word with double click, and MiddleClick to paste
  • Switch to ttyX: Ctrl+Alt+FX
  • Restart kmscon on ttyX: sudo systemctl restart kmsconvt@ttyX
  • To know on which VT you are using, echo $XDG_VTNR

How does it look ?

Previous experience, Fedora 45 with fbcon:

Fedora 45 with kmscon (unifont)

Fedora 45 with kmscon (freetype) and some customization (fish, Hack Nerd Font)

How to configure kmscon the way you like

Plugins

kmscon is split into multiple subpackages, so you have a minimal installation without graphic/font dependencies for servers, and optional packages for more features.

  • kmscon: main package, contains the unifont font, for good unicode support without additional dependencies.
  • kmscon-freetype: Use the freetype library to render the fonts.
  • kmscon-pango: Uses the pango library to render the fonts, it is deprecated in favor of kmscon-freetype.
  • kmscon-gl: This is an opengl renderer. This might be faster but also a bit blurry. You need to add hwaccel to your configuration file to actually use it.

Configuration file

The configuration file for kmscon is /etc/kmscon/kmscon.conf
you can copy the example with this command:
sudo cp /etc/kmscon/kmscon.conf.example /etc/kmscon/kmscon.conf

Here are the most common options to change:

verbose: enable more logs, if you have issues with kmscon. To get the logs, use
journalctl -u kmsconvt*

font-engine: defaults to freetype (if available) or unifont (fallback). You can also use pango, or psf (the format used by the kernel fonts)

font-name: The name of the font (for pango, freetype, and psf). As kmscon runs as root, the font must be installed in /usr/share/fonts, not in your home directory. You can find the exact name to use with fc-list. You can install Cascadia fonts, that are good for non-latin languages with
sudo dnf install cascadia-fonts-all
If you want fancy icons, Nerd fonts are good, but not available in the default Fedora repository. For psf font, font-name is the path to the font file.

font-size: The font height in pixels. By default kmscon tries to scale the font to have about 120×40 characters.

multi-monitor: multi-monitor configuration, the terminal is the same on all monitor. The default is scaled which will scale the font to avoid too much black border. Other options are clone, which will center the terminal on each monitor, and largest which will only use the largest monitor.

dpms-timeout: The timeout (in second) after which the monitor will be turned off. default to 600 (10 minutes). 0 means disabled.

no-mouse: This disable the mouse support. It can be useful to disable touchpad on some laptops.

palette: Change the default color palette for your terminal. You can define each color if none of the provided default palette suits you.

Conclusion

We hope you will enjoy using kmscon in Fedora 45. You may use it occasionally, or use it as your main session for some specific usage, like Veronica Explains for a writerdeck https://www.youtube.com/watch?v=E7vFdy4BEAY.

If you encounter any bugs, have feature ideas, or want to contribute to development, the upstream repository is at https://github.com/kmscon/kmscon.

Join us for the Fedora Linux 45 Release Party!

Posted by Fedora Magazine on 2026-10-16 16:06:49 UTC

Fedora Linux 45 is almost here! Developers, packagers, and quality assurance engineers are hard at work putting the remaining polish on Fedora 45, which means it’s time for our Global Virtual Release Party! It is almost time to celebrate! If all goes according to plan, we will celebrate Fedora 45 just after its actual final release.

To mark the occasion, we are hosting the Fedora Linux 45 Virtual Release Party on Friday, October 30, 2026.

Regardless of the final calendar date of any Fedora Linux release, every release represents months of hard work, testing, and collaboration from our global community. Whether you are a long-time package maintainer, a dedicated documentation writer, a creative graphic artist, or a brand-new user, this release belongs to you.

Join us for a half-day of live sessions, recorded deep-dives, and community socialization. We’re busy filling the upcoming schedule with updates from the Fedora Project Leader and behind-the-scenes looks at new features.

How to Attend

The event is 100% free and open to everyone, but registration is required to access the virtual venue. We will continue using Element, our chat communication platform, as the virtual venue for the Global Virtual Release Parties. Thanks Element & Matrix.org for providing us the great tools to bring our global community together!

👉 Register for the Fedora Linux 45 Release Party live event on Matrix! 👈

See you there!

Don’t miss out on the chance to connect with the people who build Fedora. Grab your ticket, share the link with your friends, and get ready to celebrate Fedora Linux 45.

Managing multiple Git repos with AI: How I keep up with Fedora's sprawl

Posted by Justin Staging Fedorable on 2026-10-13 08:00:00 UTC
Managing multiple Git repos with AI: How I keep up with Fedora's sprawl

No single person can know everything happening in Fedora at any given time. I say this often in our community, half as a warning and half for comfort. For a while, I did not really believe it applied to me. I wanted to know everything. I joined new teams, participated in tickets, and either participated or led meetings across the project. Surprisingly, as a young university student, I held a vast amount of it in my head.

But Fedora does not stand still long enough for that to last. Eventually, I was spread thin across more teams than I could realistically track. As my academic load increased or I began an internship, promises I made quietly fell off my radar. It was not because I did not care. It was because the systems I used to track them could not keep up with the sprawl, when my available time to contribute changed.

However, as I reentered the Fedora community as a Red Hat employee, the same systems I used as a student were challenged. As I get going with my new role, I am rethinking how I can rebalance my bandwidth sustainably. So, this post is about how I started managing multiple Git repos with AI agents to claw back some of that bandwidth. It is not really a story about a remarkable tool. It is an argument that in a project this sprawling, protecting your attention is the real win. I will cover two moments when things fell through the cracks, the workflow I built to catch them, a real example of it working, and an honest take on trusting AI when it sometimes gets things wrong.

Why managing multiple Git repos gets hard at Fedora’s scale 🔗

Fedora is sprawling. Fedora’s distribution Git (dist-git), the home for package sources, holds something like 20,000 packages. Add the team and SIG repositories that coordinate the people behind those packages on Fedora Forge, and the number of places where decisions get made is enormous. Yet, most contributors only touch a handful of them. However, even a handful is often scattered across different platforms, with no single view of all of it.

Where things fell through the cracks 🔗

Before this workflow, it felt like pure chaos, and I have the scars to prove it. Fedora runs on mailing lists, Fedora Discussion topics, Matrix chat rooms, and Fedora Forge issues/tickets. Furthermore, all of these are spread across dozens of teams, Working Groups (WGs), and Special Interest Groups (SIGs). In short, there are a lot of different places to follow a lot of different things.

For a long stretch, the Fedora Marketing Team had a backlog of tickets. In a few cases, contributors asked for talks and presentations to be uploaded to the Fedora YouTube channel. I had the access to do it and other YouTube maintainers were no longer active, so therefore, it was quietly mine to own. I saw the tickets at least once, but I was overworked and busy with higher-priority work. The YouTube videos slid off my list. A new volunteer eventually picked them up months or even a year later.

Additionally, Fedora also runs meetings well… on paper. Fedora holds virtual text meetings in Matrix chat rooms with a bot that logs everything. Each meeting has a clear start, a clear end, and annotated topics. But a faithful log is not the same as follow-through. For example, in AI/ML SIG meetings, we discuss a decision or someone takes an action item, and it gets logged. But it does not always make it back into the relevant ticket or discussion post. The record exists, but it does not connect itself to the places that need updating.

Patterns like this repeat themselves. The examples above are merely specific examples of where things fall through the cracks. However, there are things like this that happen everyday in different corners of the community too.

The AI multi-repo workflow 🔗

So, here is the workflow I use now. It does not get rid of all the chaos, but it helps me manage it much better. First, I point an LLM-gen-AI agent at a directory holding several cloned Git repositories. For example, the AI/ML SIG docs repository, AI/ML SIG tickets repository, and Agent Skills library. Then I ask it to analyze across all of them.

I also feed it meeting logs or summaries. I ask it to cross-check them against open tickets and Fedora Discussion topics:

  • Did we document the decisions?

  • Did we track the action items?

  • Is anyone still waiting on a reply?

Critically, I do not want it reading only files from my local git clones. I want it to query the remotes too: the Fedora Forge API, issues, discussions, and more. The underlying Forgejo API is enormous. It lets the agent track the actual cadence a team works at, not just a snapshot.

A word on trust and hallucination 🔗

I have to be honest here: the agent sometimes gets things wrong. It will occasionally misread a thread or hallucinate a detail. However, I do not think that disqualifies it. Humans get things wrong too. I would rather have slightly imperfect visibility into tens, hundreds, or even thousands of repositories than none at all. Ultimately, the question is not whether the agent is ever wrong. The question is what level of risk you are willing to accept for the visibility you gain.

A real example: Reviewer guidelines across three repos 🔗

Our Fedora Agent Skills Library needed reviewer guidelines. Laura Barcziová (@lbarczio), on our reviewer team, wrote a solid REVIEWING.md in the ai-ml/skills-library repo. But our separate ai-ml/docs repository only had a page on creating a skill, and nothing on reviewing one.

I used an agent in OpenCode to pull discussion context from Fedora Forge issues about our reviewer process. It helped me reconcile that context with Laura’s draft. Then I orchestrated multiple Pull Requests across the repositories at once. This brought the AI/ML SIG docs site in line with what the team had actually decided.

The real payoff is not the tool 🔗

In conclusion, the payoff is that it hands me back the capacity to zoom out. In a project where nobody can hold it all in their head, something should watch dozens of repositories. It surfaces what changed and what needs to catch up. That means I can engage with people’s feedback instead of just surviving the volume of it. When someone takes the time to review my Pull Request, I want the bandwidth to genuinely consider what they said. I do not want to just clear my queue.

I hope this overview of my flow and process is insightful. As of yet, I do not have a commenting feature on my blog, although I am looking into this. Tag me in a LinkedIn post and we can continue the conversation there.


Original photo by DM David on Unsplash. Modified by Justin Wheeler. Modified cover photo exclusively distributed under CC BY-SA 4.0.

Podman Test Week: Help test the Rust-based conmon v3

Posted by Fedora Magazine on 2026-10-07 16:25:50 UTC

The Podman and Fedora Quality teams are organizing a test week from Monday, October 12, through Sunday, October 18, 2026. We want your help testing conmon v3, the Rust-based container monitor used with Podman. If you use Podman, try the same containers and commands with conmon v3 and report any differences.

Why we’re testing conmon v3

Conmon is the small process that keeps watching a container after the Podman command that started it has finished. Podman uses an OCI runtime such as crun or runc to start the container; conmon attaches to its input and output, provides the connection for podman attach, collects logs, and records its exit status.

Conmon v3 replaces the C implementation with a Rust version. This helps prevent common memory errors in safe code. It also gives the logging backends a shared interface, making them easier to extend and test.

We already run Podman’s system tests against conmon v3. Now we’d like help checking development containers, interactive sessions, and Quadlet services on other people’s setups.

Getting started

We’ve prepared a test week wiki page with setup instructions, links to the test cases, and information on reporting results. Start there to check the Fedora and package requirements, then use a test machine or VM with no important data.

Install the new monitor with this command:

sudo dnf install conmon-v3

To select it system-wide, create /etc/containers/containers.conf.d/99-conmon-v3.conf with the following content:

 [engine]
conmon_path = ["/usr/bin/conmon-v3"]

Run podman info and check that the conmon path is /usr/bin/conmon-v3 and its version starts with 3. If you use both rootless and rootful Podman, check sudo podman info as well. User configuration can override the system setting.

Start new test containers after making this change. Containers that are already running retain their existing monitor.

To switch back after testing, remove the drop-in. New containers will then use your previous configuration.

What to test

Here are the areas we’d particularly like you to check:

  • Open an interactive shell, resize the terminal, and detach and attach again.
  • Run podman exec, including interactive commands, and check the output and exit status.
  • Check file and journald logs with large output and lines without a final newline.
  • Start, stop, and restart containers, including services managed by Quadlet or systemd.
  • Try rootless or rootful Podman, and crun or runc where available.

Watch for hangs, missing output, incorrect exit statuses, unexpected CPU usage, or behaviour that differs from conmon v2. The wiki links to the test cases, which include the conmon-specific checks.

Results and help

Record your results in the test day application. Please record successful tests too. They tell us which setups have been checked.

Report conmon problems in the conmon v3 issue tracker. For other Podman issues, follow the bug-reporting instructions on the wiki page. Include your Fedora version, relevant package versions, reproduction steps, relevant logs, and the output of this command:

podman info --debug

Link the bug report when submitting your test result.

For help with testing or reporting a problem, join us on Matrix in #podman:fedoraproject.org.


This article was co-written by Petr Sklenar and Jan Kaluza.

Note about AI usage: : The core technical content and claims are completely our own. Claude (Anthropic) was used only as an editing tool to enhance grammar and readability.

Fedora Forge outage

Posted by Fedora Infrastructure Status on 2026-10-04 08:00:00 UTC

forge.fedoraproject.org is currently down. We are investigating and hope to restore service soon.

Update 2026-10-04 16:15UTC: service has been restored.

Fedora Forge outage

Posted by Fedora Infrastructure Status on 2026-10-04 08:00:00 UTC

forge.fedoraproject.org is currently down. We are investigating and hope to restore service soon.

Update 2026-10-04 16:15UTC: service has been restored.

Updates and reboots on Fedora infrastructure

Posted by Fedora Infrastructure Status on 2026-10-01 20:00:00 UTC

Fedora Infrastructure team will be applying updates to servers and rebooting them.

Many services will be affected, most should only be down for a short time as their particular resources are rebooted HOWEVER some may be down for a non-trivial amount of time due to firmware upgrades.

Fedora Copr outage - updating servers

Posted by Fedora Infrastructure Status on 2026-10-01 06:00:00 UTC

There will be a Fedora Copr outage while we upgrade infrastructure machines to the latest Copr packages.

The build queue processing will be stopped during the outage, and the Frontend/Web-UI will be down most of the time (no new tasks accepted). The DNF packages and repositories (hosted on copr-backend …

Anaconda F45 features Test Week

Posted by Fedora Community Blog on 2026-09-29 14:08:36 UTC

The Fedora QA team invites you to participate in the Anaconda F45 features Test Week, which is running now through October 2, 2026. There is still time to jump in this week and help us shape the Fedora 45 installer before it ships.

What’s New in the Anaconda F45 Installer

Fedora 45 brings three significant changes to how you install the system. Each one is ready for real-world testing – and better testing means a better installer.

  • WebUI for Atomic Desktops – The modern web-based installer now covers the Atomic Desktops (Silverblue, Kinoite, and the Cosmic/Sway/Budgie Atomic variants). See the Change page.
  • Remote WebUI – You can now drive an installation from another device entirely, straight from a browser. See the Change page.
  • Stratis support – The WebUI can now configure Stratis storage. See the Change page and the introduction on Fedora Magazine.

How to Participate

Requirements

  • A virtual machine or a spare bare-metal box – not a production machine and not one with data you care about.
  • The latest Fedora 45 nightly image (nightly images or the development mirror).
  • A little time between now and October 2.

Start here

The Anaconda Test Week is running now through October 2, 2026. We have prepared easy-to-follow steps for you here: https://fedoraproject.org/wiki/Test_Day:2026-09-28_Anaconda_F45_features

If you need any help, community contacts are listed on that page too.

Learn more:

The post Anaconda F45 features Test Week appeared first on Fedora Community Blog.

Fedora Shines Blue at Software Freedom Day Bukidnon 2026

Posted by Fedora Community Blog on 2026-09-29 12:00:00 UTC

On September 19, 2026, the Fedora Project supported the conduct of Software Freedom Day Bukidnon 2026. The event took place at the Northern Bukidnon State College, Manolo Fortich, Philippines.

Now in its second run, Software Freedom Day Bukidnon gathered students, professionals, educators, and community members to explore how Free and Open Source Software can empower innovation, digital inclusion, and impact their daily lives, primarily in the province of Bukidnon, Philippines. Despite the challenges like power outage, the event was a massive success, demonstrating the local community’s resilience and passion for open technology.

Event Highlights

The event features an impressive speaker lineup, with presentations spanning foundational Open Source principles and cutting-edge technology trends.

  • Paul Harriet Asiñero while presenting Hello Fedora
  • Walt Miner while presenting Introduction to Automotive Grade Linux
  • Arjay Sitoy while presenting Local LLMs: My 8GB VRAM vs the World
  • Romar Mayer Micabalo while presenting Harnessing Krita For Fun and Profit
  • Rafael Tibudan while presenting Building a Second Brain: Turning Information into Leverage
  • Wei Lee while presenting Orchestration Still Matters: Apache Airflow in the Age of AI
  • Jay Ginete while presenting 5 Cool Open Source Tools to Pimp Out Your Windows CLI
  • Roger Madjos while presenting Practical Agentic Coding with OpenCode

Linux and Open Systems

Hello Fedora by Paul Harriet Asiñero – This session introduced attendees to Fedora Linux, highlighting its pivotal role in driving Open Source innovation. Participants explored the power, robust security, and exceptional flexibility that make it one of the world’s premier Open Source operating systems.

Introduction to Automotive Grade Linux by Walt Miner – Attendees received an exciting look at how Open Source technology has moved beyond PCs and servers, driving the software systems that power modern smart vehicles.

Art and the Developer Workflow

Harnessing Krita For Fun and Profit by Romar Mayer Micabalo – Proving that Open Source is just as crucial for creatives as it is for developers, this talk walked attendees through building a career or hobby using Krita, a premier Open Source digital painting tool.

5 Cool Open Source Tools to Pimp Out Your Windows CLI by Jay Ginete – A practical guide for developers stuck on proprietary systems, showing how to upgrade a boring terminal into an Open Source-powered developer powerhouse.

The AI and Data Pipeline

Local LLMs: My 8GB VRAM vs the World by Arjay Sitoy – In a highly relevant, budget-conscious session, this talk demonstrated how developers can break free from corporate API reliance by running powerful Large Language Models locally on standard consumer hardware.

Practical Agentic Coding with OpenCode by Roger Madjos – Shifting from consumption to creation, this session showed developers how to leverage Open Source AI agents to actively write and debug code. Attendees walked away with a practical blueprint for turning agentic coding into a reliable, secure, and repeatable development workflow that delivers value faster without compromising quality.

Building a Second Brain: Turning Information into Leverage by Rafael Tibudan – Explored how to use knowledge management, AI, and automation to build a digital “second brain.” The session shared simple, scalable strategies to transform past code bugs, research notes, and AI conversations into a personal knowledge base.

Orchestration Still Matters: Apache Airflow in the Age of AI by Wei Lee – Attendees got a deep dive into the backend infrastructure powering modern technology. The talk drove home a crucial point: even as artificial intelligence dominates the headlines, leveraging Apache Airflow to control and orchestrate the data pipelines and workflows powering AI applications remains absolutely vital to AI success.

Page Follow Bingo Game and Raffle Draw

In addition to the engaging sessions, the event featured a Page Follow Bingo Game and an exciting raffle for all attendees. The Bingo game was designed to boost engagement for our event sponsors and partners by encouraging participants to follow their official pages, with the first five to complete the task being crowned winners. The event wrapped up with a raffle draw featuring an array of prizes generously contributed by our sponsors. The raffle was conducted using pyraffle, an Open Source raffle draw software executed within a notebook environment.

Final Thoughts

Despite the challenges, Software Freedom Day Bukidnon 2026 was a resounding success! An impactful movement like this cannot happen in isolation. As we look back on the success of this year’s event, our deepest gratitude goes out to the incredible individuals and organizations who helped bring this vision to life.

Event Sponsors and Partners

Software Freedom Day Bukidnon 2026 Partners and Sponsors
Software Freedom Day Bukidnon 2026 Event Partners and Sponsors

This event was made possible through the generous support of our partners and sponsors. In addition to the Fedora Project, we would like to extend our sincere gratitude to the following organizations:

Aside from the participating organizations, we would like to express our gratitude to an anonymous donor for providing financial support for the event.

Speakers

Awarding of tokens for the Speakers
Awarding of tokens for the Speakers

Thank you for sharing your time, passion, and unparalleled expertise. You gave our community tangible frameworks to work with, sparking ideas that will undoubtedly fuel local tech innovation for months to come.

Event Volunteers

Volunteers are the backbone of Software Freedom Day Bukidnon 2026, driving everything from pre-event preparations to post-event operations. We are proud to recognize the dedicated individuals who made this success possible:

Participants

Thank you for taking the time out of your weekend to show up, engage, and learn. Your energy, thoughtful questions, and collaborative spirit are what give life to the FOSS movement in Bukidnon. You are the future of our digital landscape, a thriving ecosystem where the veterans lift up the rookies, passing the torch to ensure the next generation keeps pushing boundaries.

The event has wrapped up, but our mission continues. The Free and Open Source Software movement in Bukidnon thrives because of community advocates and supporters like you. As we look ahead to the return of Software Freedom Day next September, we invite you to join us as a participant, volunteer, sponsor, or partner. Together, we can empower local tech ecosystems and drive collaborative innovation.

The post Fedora Shines Blue at Software Freedom Day Bukidnon 2026 appeared first on Fedora Community Blog.

Installing Navidrome on Fedora Linux using Podman

Posted by Fedora Magazine on 2026-09-25 08:00:00 UTC

Navidrome is an open-source music server that lets you stream your personal audio collection anywhere. It gives you freedom to listen to your music collection from any browser or mobile device. It’s like your personal Spotify!

In this guide, we will explore how to get Navidrome up and running securely using Podman on Fedora Linux. Best of all, because Navidrome builds official multi-architecture container images including, linux/amd64, linux/arm64, and linux/arm/v6/v7, this setup is highly portable. Whether your hardware is a standard x86 PC server or a low-powered ARM-based Raspberry Pi, this walk-through has you covered.

For the official image for Navidrome Music Server go to:

deluan/navidrome – Docker Image

Using the official container images with Podman and Podman Compose

Container images are available for the linux/amd64, linux/arm/v6, linux/arm/v7 and linux/arm64 platforms. They include everything needed to run Navidrome

[nico@stamfordbridge navidrome\]$ podman pull deluan/navidrome
✔ docker.io/deluan/navidrome:latest
Trying to pull docker.io/deluan/navidrome:latest…
Getting image source signatures
Copying blob 75c0824146ea done |
Copying blob 4f4fb700ef54 done |
Copying blob 4f4fb700ef54 done |
Copying blob e1dbf20ea67c done |
Copying blob 1cc3d825d8b2 done |
Copying config 0c9bad3bd7 done |
Writing manifest to image destination
0c9bad3bd7305815d56fe588a64f9172a8bb6aa2bfef3ad77e764c8694e7e860

If you have SELinux enabled on your Fedora Linux server, then add the container_file_t SELinux context to the Data and Music directories and its contents.

[nico@stamfordbridge navidrome]$ sudo semanage fcontext -a -t container_file_t  '/home/nico/navidrome/Data(/.\*)?'

[nico@stamfordbridge navidrome]$ sudo semanage fcontext -a -t container_file_t  '/home/nico/navidrome/Music(/.\*)?'

Apply the SELinux policy to the Data and Music directories.

[nico@stamfordbridge navidrome]$  sudo restorecon -R /home/nico/navidrome/Data

[nico@stamfordbridge navidrome]$  sudo restorecon -R /home/nico/navidrome/Music

Change the owner of the /home/nico/navidrome/Data and /home/nico/navidrome/Music to 1000.

[nico@stamfordbridge navidrome]$ podman unshare chown 1000:1000 /home/nico/navidrome/Data

[nico@stamfordbridge navidrome]$ podman unshare chown 1000:1000 /home/nico/navidrome/Music

Using podman-compose :

Create a podman-compose.yml file with the following content (or add the navidrome service below to your existing file):

[nico@stamfordbridge navidrome]$ cat podman-compose.yml
version: "3"
services:
  navidrome:
    image: deluan/navidrome:latest
    user: 1000:1000 # should be owner of volumes
    ports:
      - "4533:4533"
    restart: unless-stopped
    environment:
      # Optional: put your config options customization here. Examples:
      ND_SCANSCHEDULE: 1h
      ND_LOGLEVEL: info  
      ND_SESSIONTIMEOUT: 24h
      ND_BASEURL: ""
    volumes:
      - "/home/nico/navidrome/Data:/data"
      - "/home/nico/navidrome/Music:/music:ro"

Start the navidrome container with podman-compose up -d.

[nico@stamfordbridge navidrome]$ podman-compose up -d

Note that the environment variables above are just an example and are not required. The values in the example are already the defaults

Using podman command line tool:

[nico@stamfordbridge navidrome]$ podman run -d - name navidrome - restart=unless-stopped - user $(id -u):$(id -g) -v /home/ec2-user/navidrome/Music:/music -v /home/ec2-user/navidrome/Data:/data -p 4533:4533 -e ND_LOGLEVEL=info deluan/navidrome:latest
c00c31d49ec5e0f0a0141aef9e2b69abf6a1b5f0604515bc7111f3e0ef398237

[nico@stamfordbridge navidrome]$ podman ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
c00c31d49ec5 docker.io/deluan/navidrome:latest 9 seconds ago Up 9 seconds 0.0.0.0:4533->4533/tcp navidrome

Customization

  • The user argument should ideally reflect the UID:GID of the owner of the music library to avoid permission issues. For testing purposes you could omit this directive, but as a rule of thumb you should not run a production container as root.
  • Remember to change the volumes paths to point to your local paths. /data is where Navidrome will store its DB and cache, /music is where your music files are stored.
  • Configuration options can be customized with environment variables as needed. For podman-compose just add them to the environment section or the yml file. For podman CLI use the -e parameter. e.g.: -e ND_SESSIONTIMEOUT=24h.
  • If you want to use a configuration file with Navidrome running in Podman, you can create a navidrome.toml config file in the /data folder and set the option ND_CONFIGFILE=/data/navidrome.toml.

New badge: ESC member !

Posted by Fedora Badges on 2026-09-24 19:26:43 UTC
ESC memberYou have been a member of the EPEL Steering Committee

Installing Fedora 45 on Stratis storage

Posted by Fedora Magazine on 2026-09-23 08:00:00 UTC

The Anaconda installer in Fedora 45 will introduce a new option for storage configuration: Stratis, a modern solution for local storage management.

Stratis isn’t a completely new technology, it uses existing tools and technologies like device mapper, LUKS, and XFS and integrates them into an easy to use package. The idea is to provide modern storage features while hiding the often complex logic behind them. Adding support to the installer brings these features even closer to Fedora users.

There are only two basic structures or layers you need to know when working with Stratis: pools and filesystems. Pools represent an abstract layer on top of existing block devices (disks, partitions, RAID arrays etc.). A pool can consist of one or more devices (for systems with multiple disks, for example). Features like encryption or over-provisioning are also configured on the pool level. Multiple filesystems can be created on the pool. These are devices that will serve as your root or home volumes. Some additional features supported by Stratis include snapshots, caching, and for encrypted pools, multiple unlocking methods like TPM or Clevis/Tang. Caching and encryption without a passphrase are not currently supported by Anaconda, but these can be easily enabled after the installation.

Management of Stratis devices can be done using the stratis command. For more information, check our older, but still valid, article Getting started with Stratis or the Stratis project how-to.

Installation using Web UI

The new web-based user interface for the Anaconda installer currently doesn’t allow selecting which type of storage technology will be used for the automated and guided partitioning options. The storage layout you will get depends on the Fedora variant you choose to install. But if you want to use Stratis, you still have an option in the graphical installation. Any storage layout can be created manually using the Cockpit storage module, which is integrated into the installer. To enter it, simply select the If none of the options above apply… option on the Installation Destination step.

Installation method page in the Anaconda installer

The Cockpit storage module supports a wide variety of storage configurations and Stratis is one of the supported technologies. Do not forget that with manual partitioning, you need to create all required partitions so first create partitions required for booting (/boot and /boot/efi or biosboot, based on your system configuration). After that, simply create a new Stratis pool from the menu.

Local storage menu in the manual partitioning editor

Creating stratis pool

After selecting a name for the pool and the disk (or disks) it will be placed on, you can decide whether to enable encryption and over-provisioning for the pool. Over-provisioning allows allocation of more space for the filesystems created on the pool. Similarly to how LVM thin provisioning and Btrfs work. With over-provisioning enabled, there is no need to worry about running out of space in root with still plenty of free space in /home. It also allows greater flexibility when using snapshots. On the other hand, you actually need to be aware that you don’t really have terabytes of space and you need to make sure you won’t actually run out of space on your disk. Both encryption and over-provisioning can also be enabled or disabled after the installation.

Creating Stratis pool in the manual partitioning

Creating stratis filesystems

With the new pool created, you now need to add some filesystems to it. You’ll most likely want the standard two separate filesystems for your / and /home. But you can also create a separate filesystem for your /var, for example.

If you enable over-provisioning on your pool, you can also decide to not specify sizes for the filesystems and use the 1 TiB default size with over-provisioning or set a size limit for the filesystem to prevent it from automatically growing if you ever run out of space.

Creating Stratis filesystem in the manual partitioning

Using the configured layout

With all the filesystems created, you can Return to installation. Anaconda will check the created devices to make sure all requirements are met and return you to the Installation destination page where a new Use configured storage option will be preselected with the devices that were just created.

Confirmation dialog with validated storage layout in the manual partitioning
Using configured storage in the Anaconda installer

That is the storage part of the installation done. You can double-check on the Review and install page that everything is correctly set and start the installation.

Summary of the installer configuration before starting the installation

Installation using kickstart

For advanced users who wish to use automated installations, full kickstart support for Stratis is also available. Both automatic and manual partitioning are available via kickstart.

Automatic partitioning is simple: the existing autopart command can be used with –type=stratis to create the default Stratis storage layout fully automatically. A storage section in kickstart, for setting up an encrypted Stratis layout, could look like this:

zerombr
clearpart --all --initlabel
autopart --type=stratis --encrypted --passphrase="passphrase"

Manual partitioning requires building the entire storage layout manually from bottom up. Two new Stratis kickstart commands were added: stratispool for creating and managing Stratis pools and stratisfs for creating and managing Stratis filesystems. Usage of these commands and most of the options are similar to how kickstart partitioning works with LVM. An example of a more advanced Stratis layout can be found below.

reqpart
part /boot --fstype=ext4 --size=500
part stratis.01 --size=1 --grow --ondisk=vda
part stratis.02 --size=1 --grow --ondisk=vdb
stratispool fedora stratis.01 stratis.02
stratisfs / --name=root --poolname=fedora --size=5000 --grow
stratisfs /home --name=home --poolname=fedora --size=1 --grow

Here we are creating a pool called fedora on top of two disks, vda and vdb, with two filesystems. One called root for / and a second called home for /home. The –grow tells the installer to use all available free space when creating the devices. For more details about the commands see the kickstart documentation.

Conlusion

The newly introduced Stratis support in Anaconda offers an easy way to take advantage of the modern storage features offered by Stratis. With the Web UI support available through Cockpit storage, you can now easily use Stratis on your system. We plan to simplify the process even more in future releases and enable even more advanced Stratis features. 

If you run into any issues or have feedback, both the Anaconda and Stratis teams would love to hear from you.

Fedora Copr outage - updating servers

Posted by Fedora Infrastructure Status on 2026-09-23 06:00:00 UTC

There will be a Fedora Copr outage while we upgrade infrastructure machines to the latest Copr packages.

The build queue processing will be stopped during the outage, and the Frontend/Web-UI will be down most of the time (no new tasks accepted). The DNF packages and repositories (hosted on copr-backend …

Fedora at Data Con LA 2026: Open Source & Local AI

Posted by Fedora Community Blog on 2026-09-17 12:00:00 UTC

On Saturday, August 22, 2026, the Fedora Project joined forces with openSUSE at Data Con LA 2026, hosted on the campus of California State University, Long Beach (CSULB).

Now in its 14th year, Data Con LA is Southern California’s largest gathering of data professionals, students, and practitioners covering data science, AI/ML, and data engineering. While Data Con LA is not a traditional Linux-centric conference, our presence offered a unique, hands-on opportunity to engage a fresh audience of prospective contributors, test our event planning workflows, and showcase Fedora Workstation in action.

As part of our ongoing work to standardize the Fedora Ambassador event pipeline, this report reflects on our operational outcomes, what worked well, and key lessons learned for future event organizers.

1. A Standout Win: “A House with Many Rooms” (Co-Hosting with openSUSE)

Our standout operational victory at Data Con LA was co-locating and sharing table space side-by-side with openSUSE advocates (coordinated with Patrick Finie / mir and Drew Adams).

Rather than maintaining isolated tables, we embraced the philosophy of “A House with Many Rooms.” This cross-community collaboration was an immediate force multiplier:

  • Shared Energy & Presence: Combining our presence effectively doubled our footprint and visual appeal, turning our shared booth area into a high-energy focal point in the expo area.
  • Seamless Staffing & Rotations: Having four volunteers across both distributions allowed for seamless shift rotations during peak traffic and lunch breaks, completely preventing booth fatigue.
  • Cross-Promotion: When attendees visited our table, we engaged them collaboratively by directing people to open source solutions across distros based on their specific technical needs and interests.

For future community organizers planning small-to-medium booths, establishing a shared booth with allied open source projects is an operational model we strongly recommend.

2. Demographics & Lead Engagement

Over the course of the day, our booth engaged approximately 100 visitors (110% of our initial goal), with peak traffic occurring during the post-keynote morning rush (9:30 AM – 11:00 AM) and lunch transitions (12:30 PM – 2:00 PM).

The attendee demographic offered valuable insights into the broader tech ecosystem:

  • Student & Alumni Presence: The majority of visitors were CSU Long Beach undergraduate and graduate students, alumni, and local data practitioners.
  • First Encounters with Linux: Roughly 10% of attendees were active Linux users; for the remaining 90%, Data Con LA was their first direct introduction to Linux and Fedora.
  • Lead Qualification Breakdown:
    • Hot Leads (30): Inquired specifically about Fedora, visited the website, and expressed interest in installing Fedora Workstation or exploring the Join SIG.
    • Warm Leads (20): Asked for links to documentation, Fedora Discussion forums, Matrix channels, or local user groups (such as SGV LUG in Pasadena and SFV LUG in Northridge).
    • General Engagements (10+): Discussed general data industry trends, tech careers, or university studies.

3. The Technical Showcase: Local AI on Fedora Asahi Remix

To connect directly with the conference’s AI/ML focus, we showcased a fully offline, containerized local AI demonstration running on an Apple Silicon laptop.

The Setup

  • Hardware: 2020 Apple M1 MacBook Air (8 GB RAM) dual-booting macOS.
  • Operating System: Fedora Asahi Remix (Fedora 44 release) running GNOME on Wayland.
  • Software Stack: Fedora-native Podman containers running Ollama alongside Open WebUI, exposing a private, ChatGPT-style web interface at localhost.
  • Model: llama3.2:1b (sized appropriately for the laptop’s 8 GB memory ceiling).

Why It Resonated

This demonstration served as a major crowd-pleaser across two distinct attendee groups:

  1. Data Professionals & Privacy: Attendees expressed fatigue with commercial operating systems that enforce invasive telemetry and proprietary cloud AI features. Highlighting how Fedora enables private, offline LLM inference with zero data leakage resonated powerfully.
  2. Students on a Budget: CSULB students loved seeing how Linux can revive older, restricted hardware to deliver a capable, subscription-free AI workspace without requiring expensive cloud API tokens.

4. Advice & Lessons for Future Event Owners

If you are planning to organize a small event (under $150) or booth presence in the next six months, here are four practical takeaways from our experience:

  1. Design 100% Offline Demos: Campus and conference Wi-Fi networks are notoriously unreliable, firewalled, or slow. Designing our demo to run entirely inside local Podman containers without requiring an internet connection kept our booth fully functional all day without friction.
  2. Account for Outdoor Environmental Factors: Our booth was located in an outdoor expo space. During the afternoon peak heat, direct sunlight caused our demo laptop to heat up, requiring us to tuck it under banners in the shade. Recommendation: Always confirm booth coverage in advance, and pack brimmed hats, pop-up shade, or cooling accessories if outdoor placement is unavoidable.
  3. The Power of the Daily User Perspective: You do not need to be a kernel developer or upstream maintainer to staff a Fedora booth. Sharing how you use Fedora day-to-day for work, study, or home projects alleviates “imposter syndrome” and provides relatable, authentic guidance that newcomers appreciate.
  4. Keep Swag Requests Lean on Short Timelines: Because our event planning window was short, we kept our Forgejo Mindshare swag request focused strictly on high-impact essentials: stickers, case badges, and pens. Podman and Fedora logo stickers drew in decision-makers and students alike.

5. Next Steps & Wrap-Up

We would like to thank Patrick Finie, Drew Adams, and the openSUSE community for partnering with us, as well as the CSULB organizers for putting together a fantastic event.

Following Data Con LA, our team of Ambassadors Perry Rivera and Rob McBryde are incorporating these lessons directly into the new Small Events Standard Operating Procedure (SOP) and preparing for upcoming community participation at SCaLE. Our intention is to share and publish this information in the Fedora Docs website so that other event owners in the Fedora community may benefit from common wisdom from others who have done this work before.

  • Want to get involved? Connect with us on Fedora Discussion or drop by the #ambassadors:fedoraproject.org Matrix channel!

The post Fedora at Data Con LA 2026: Open Source & Local AI appeared first on Fedora Community Blog.

New badge: TXLF 2026 !

Posted by Fedora Badges on 2026-09-17 11:50:57 UTC
TXLF 2026You visited the Fedora booth at TXLF 2026!

CoreOS 45 Test Week

Posted by Fedora Magazine on 2026-09-16 08:00:00 UTC

The Fedora CoreOS and QA teams are gearing up for Fedora 45, and we need your help! We are organizing a Fedora CoreOS Test Week starting on September 21, 2026.

This event is a great opportunity for the community to test Fedora CoreOS (FCOS) based on Fedora 45 content before it officially reaches the testing and stable streams. By participating, you help us ensure a smooth and reliable experience for all users.

How does a Test Week work?

A Test Week is an event where anyone can help verify that the upcoming release works as expected. If you’ve been looking for a way to get started with Fedora contribution, this is the perfect entry point.

To participate, you simply need to:

  • Download the Fedora CoreOS test images.
  • Follow the step-by-step test cases provided.
  • Report whether the tests passed or failed on your hardware or VM.

The Wiki Page is your primary source of information for this event. It contains information on what to download (and from where), what and how to test, who you can contact if necessary, and where to report any bugs you may find. Once you have completed your tests, please log your results there!

Your contribution, big or small, makes a huge difference. Let’s work together to make Fedora CoreOS 45 a great release. Happy testing!

Announcing Fedora Linux Asahi Remix 45 Beta

Posted by Fedora Magazine on 2026-09-15 14:05:00 UTC

We are happy to announce the availability of Fedora Linux Asahi Remix 45 Beta. This pre-release will bring the freshly announced Fedora Linux 45 Beta to Apple Silicon Macs. We expect to announce general availability of Fedora Linux Asahi Remix 45 in about a month. This will coincide with the overall Fedora Linux 45 release.

Fedora Linux Asahi Remix is developed in close collaboration with the Fedora Asahi SIG and the Asahi Linux project. Fedora Asahi Remix 45 Beta includes all of the Changes from Fedora Linux 45. Notably, this is the first Fedora Asahi Remix release to include out of the box initial support for Apple M3, M3 Pro and M3 Max systems, which are now officially supported by Asahi Linux upstream. The GPU drivers to enable performant 3D acceleration on these M3 systems are not included at this point and will be available via a Mesa update in the future. This release also includes support for hardware accelerated H.264 and VP9 video decoding for all Apple Silicon systems; additionally, Apple M3 systems include support for AV1 decoding.

You can try out Fedora Asahi Remix 45 Beta today by following our installation guide. Existing systems, running Fedora Asahi Remix 43 or 44, can be updated following the usual Fedora upgrade process. Upgrades via Fedora Workstation’s Software application are unfortunately not supported and DNF’s System Upgrade plugin has to be used.

Since this is a beta release, we expect that you may encounter bugs or missing features. Please report any Remix-specific issues in our tracker. You may also reach out in our Discourse forum or our Matrix room for user support.