About the Proposed Common Issues category

If you know of a problem in a Fedora Linux release which affects a lot of people in a serious way, you’ve come to the right place! This category is where we collect and organize suggested Common Issues. When they’re in good shape, we publish them to the main Common Issues category.


Because Fedora integrates so much rapidly-changing open source software so quickly, if we waited for everything to be perfect, we’d never release. We try to be as close to ideal as we can, but this list helps our users when we fall short! Making it as useful as possible is a great deal of effort, so we appreciate your help.


Posts that Common Issues Bot makes in this category will be marked as “wiki”, which means anyone with at least the Basic site trust level can edit and improve them. That’s the level it takes to create new posts here, too. To do that, just fill out the template that comes up when you start a new topic in this category. The parts between <!-- and --> characters are comments — they’re instructions that won’t show in the final result. (You can remove them as you write, if you want.)

Keep in mind that we’re targeting a general audience, so don’t assume too much technical knowledge. Also, people coming here probably just want to get working again, so keep to the point. In-depth discussion can go in a linked topic in another category.

You can also nominate a Bugzilla bug to be linked to an issue here by adding the “CommonBugs” keyword. When you do that, I, Issuebot, will come along and create a topic for you, linking back to that bug. It’ll follow the same template as a human-created bug, but won’t be very well filled out, because, let’s face it, I have a tiny bug brain and don’t understand computers. (Actually, I’m just a Python script.)

Once Issues are filed here in this category, everyone can discuss. I will try to help out by providing updates from any linked Bugzilla entries. Once the @common-issues-triage team decides that the issue meets the criteria and the text is ready, Issuebot will move the topic to the Accepted Common Issues category. If, on the other hand, they decide that it’s a false alarm, or better handled a different way, they’ll close the topic, and if it stays that way for a week, I’ll automatically clean it up.


The Common Issues Triage Team is a group of Fedora contributors who work on this effort. If you’re an old hand around the Fedora Project, your expertise would be very welcome. And, if you’re brand new, this is a great place to get started — we’ll appreciate your enthusiasm and help you learn anything you need to know.

For now, if you’re interested in joining, post over in Site Feedback. We’ll probably have a Fedora Discussion space soon, but let’s get started here.

Note that this category is muted (hidden) by default. To follow along, go to the category page and change 160503cfaffd1819b7798ac8a6c51f6ece67b0fc.png.

1 Like

Detailed Triage Instructions

Hi @common-issues-triage team! Issuebot has found some bugs marked with the CommonBugs keyword in Bugzilla, and made entries for them here.

Anyone can tag a bug with CommonBugs, so that doesn’t mean anything official — it’s just a candidate. Also, Issuebot doesn’t try to do anything more than extract the title and provide a link, because the bug report isn’t necessarily — or even likely to be — in the style we want for Common Issues topics.

So, a human is needed.

For F35: wiki page to new style entry

For this experimental time after the Fedora Linux 35 release up until the F36 Beta, this is running in parallel with the traditional F35 Common Bugs wiki page, so, at least for the current batch, what we need to do is look at the bugs here, look at the entry there, and translate formats — both from MediaWiki to Markdown, but also a little bit in format, because the template I’ve made here is a little different from the layout there (to fit a forum topic vs. a single wiki page).

Since these topics are marked as “wiki”, you don’t have to be a moderator or member of the Common Issues Triage Team to help with this!

Titles and Tags

Remember to fix the title. Remove the New proposed Common Issue found prefix, and reword the rest to reflect the issue a user might encounter — which may be very different from the subject of the bug report. For F35, “borrowing” titles from the wiki page is probably right.

Add tags corresponding to that page’s sections. (If you don’t have permissions to add tags, flag the post and a moderator will do it.) Feel free to add additional tags that seem to fit.

Issuebot comments

After the initial topic is created, Issuebot will scan for possible fixes in any Bugzilla links in the topic. Again, it’s not smart — if you put multiple Bugzilla links in the topic post, Issuebot will look in all of them just in case. Right now, it’s just echoing the Fedora Updates System comments. I intend to make these messages a little more helpful in the next couple of weeks, so normally they should not require human improvement — but, they should be checked, and edited if need be. You may also want to put some of the information Issuebot discovers into the “Workarounds?” section of the topic post.

Marking an issue solved

If an update noted by Issuebot — or another reply — explains how to solve the problem, mark that reply as the solution (which will make the entire topic display as Solved :white_check_mark: in the topic list).

Other replies and discussion

Otherwise, replies should be kept to the topic of “should this be listed as a Common Issue?” or discussion about the text. Discussion about the underlying bug should go in Bugzilla. And workarounds or more information about the problem a user might encounter should be edited into the topic text.

1 Like

20 posts were merged into an existing topic: We are testing a “New Common Issues” category and process