Search results

...and the [[QA:Update_feedback_guidelines|update feedback guidelines]]. This page specifically covers the update submission process. ...single multi-package update, such that no user will face problems if they install all the packages in the update together.

...eir time, and may even result in the bug being ignored or forgotten. This page describes how to file quality bug reports and suggest enhancements in a con {{Admon/tip |Commonly Reported Bugs|The [[Bugs/Common| Fedora common bugs]] page is useful for finding fixes to already known installation, upgrading or HW/

...modify the configuration, users that require special configuration should create and use custom authselect profile. ...Fedora 35 as a [[Changes/RemoveAuthselectCompatPackage|system wide change page]]. It is now well accepted by the community as well as the package maintain

<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps ...hat it will do. This information is used for the overall changeset summary page for each release.

| name = '''Kernel 6.7 Test Week''' | image = [[File:test-days-banner.svg|300px|link=QA/Test Days]]

...keyword to the bug report, and place the anchor link to the entry on this page in the Whiteboard field on the bug report if it is not being used for anyth ....org/updates/(name)-EVR report to Bodhi] whether it solves the problem. To test the update, run this command:

<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps ...hat it will do. This information is used for the overall changeset summary page for each release. Note that motivation for the change should be in the Bene

<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps <!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps

<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps ...at it will do. This information is used for the overall change set summary page for each release.

This is a page that is going to be edited. Feel free to leave comments and suggestions. Fedora moves very quickly and has lots of users. As a result we see our fair share of bugs.

<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps <!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps

<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps ...hat it will do. This information is used for the overall changeset summary page for each release. Note that motivation for the change should be in the Bene

...accepted by FESCo, tracking bug is created in Bugzilla and linked to this page ...an be installed for a given package. Even on a multi-lib system you cannot install the 64-bit and 32-bit versions of a debuginfo package in parallel (technica

<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps ...hat it will do. This information is used for the overall changeset summary page for each release. Note that motivation for the change should be in the Bene

...fixes or workarounds for these problems. If you find your problem in this page, ''do not file a bug for it, unless otherwise instructed.'' Where appropri ...dhat.com Bugzilla] should be a comprehensive database of known bugs. This page is a sampling of the bugs most commonly discussed on our mailing lists and

This page provides information about '''JDK''' installations on Fedora. (See also [ht ...ge will discuss mainly about Open JDK and Oracle JDK, how to install them, test and configure them on Fedora.

<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps ...hat it will do. This information is used for the overall changeset summary page for each release.

...e exciting features of Fedora 21's products in a form that anyone can help test. This testing, guided by the [[QA|Fedora QA team]], helps us target *http://download.fedoraproject.org/pub/fedora/linux/releases/test/21-Beta/Images/armhfp/

* Improve compatibility with other Unixes/linux, no confusion about tools install locations, no $PATH fiddling, all possible paths to a binary will always wo == How To Test ==

...read it, choose the "view source" link.<br/> '''Copy the source to a ''new page'' before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSA <!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps