From Fedora Project Wiki

  • * The page doesn't work with Epiphany. Rendering is totally broken and eventually the browser crashes. (epiphany.x86_64 1:2.30.6-1.fc14) ** Í have not tested if it is broken with all WebKit based browsers
    10 KB (1,572 words) - 21:46, 21 November 2011
  • ...if not logged in, the login right sidebar box should be persistent across pages.</strike> ...rpms. if failure, hover menu for build error logs or link out to koji page with build error logs
    18 KB (2,487 words) - 14:09, 20 July 2009
  • ...ticles, separate the words of both the article title and the piped content with spaces; underscores should never be used as, internally to the wiki, they a ...e in the form of a sentence or question. Section titles should not contain links.
    9 KB (1,510 words) - 21:16, 19 July 2011
  • Mailman3 is built in a modular way with several subprojects providing smaller parts of the entire setup. ...the list you are interested in. Please let us know if you find any broken links or are redirected to an incorrect location for a list.
    3 KB (534 words) - 23:19, 18 April 2016
  • | image = [[File:Echo-testing-48px.png|link=QA/Fedora_24_test_days]] ...g is still valuable, and you can use the information on this page to test, file any bugs you find at [http://bugzilla.redhat.com Bugzilla], and add your re
    10 KB (1,431 words) - 21:45, 19 September 2016
  • * Broken deps report ...Obsoletes: to satisfy pre-extras package dependencies?" -> mschwendt will file a bug
    28 KB (3,762 words) - 16:26, 24 May 2008
  • ...nes, and should not conflict with them. In case of conflict the guidelines pages always take precedence. === What is a font file? ===
    23 KB (3,683 words) - 09:36, 23 February 2009
  • File bug reports on this Alpha release for directed feedback. ...normally. If you encounter any broken dependencies, try <code>yum --skip-broken update</code> instead.
    15 KB (2,275 words) - 20:44, 19 September 2016
  • | image = [[File:Echo-testing-48px.png|link=QA/Fedora_38_test_days]] ...g is still valuable, and you can use the information on this page to test, file any bugs you find at [http://bugzilla.redhat.com Bugzilla], and add your re
    17 KB (2,400 words) - 03:45, 24 March 2023
  • ...se of "'fedorabugs' group" in the language. A second draft will be created with changes to the language removing "'fedorabugs' group" and any confusion it ...djustments to the page will be made when required to align with supporting pages.
    52 KB (6,083 words) - 09:51, 18 September 2016
  • ...ommunity on things that worked well and things that could have been better with the testing of Fedora 12. The feedback will be used as a basis for identif * [[User:Johannbg|Viking-Ice]] - Consistency in how to debug <component> pages for better look and feel.
    20 KB (3,260 words) - 13:31, 27 September 2010
  • ...yTestingRound1/UsabilityTester1 | Tester #1]] felt the site was consistent with Fedora branding and recognizable as an official Fedora site. ...yTestingRound1/UsabilityTester2 | Tester #2]] felt the site was consistent with Fedora branding and recognizable as an official Fedora site.
    55 KB (7,431 words) - 23:33, 15 March 2010
  • ...t we'll probably want to look at the template and try writing a few HOWTOs with it before anyone will have input.. ...t-snmp update.. I have no clue how to set up an snmp server, or what to do with it
    30 KB (4,804 words) - 16:31, 24 May 2008
  • ...[[Template:Common_bugs_header_shared]] templates as appropriate, so future pages will contain the same improvements. ...or these problems. If you find your problem in this page, ''please do not file a bug for it, unless otherwise instructed.'' Where appropriate, a referenc
    16 KB (2,470 words) - 00:01, 15 December 2021
  • ...built in stage1) in build order as determined by dependencies in the make file fragments. Stage1 details are [[Architectures/AArch64/Bootstrap/Stage1Note ...can also turn this set of files into a rootfs disk image that can be used with the ARM Foundation model (see ARMv8 using Fedora17 Bootstrap Image and ARM
    18 KB (3,046 words) - 15:33, 6 November 2014
  • | image = [[File:test-days-banner.svg|300px|link=QA/Test Days]] ...g is still valuable, and you can use the information on this page to test, file any bugs you find, and add your results to the results section. If this pag
    16 KB (2,357 words) - 11:43, 17 April 2023
  • ...umber of people think that the Feature Process, as it exists currently, is broken. This page is an attempt to start gathering feedback, information, specifi Here are some handy links to Feature Process-related wiki pages.
    22 KB (3,544 words) - 15:36, 31 October 2012
  • ...others. It also creates an initial <code>~/.rpmmacros</code> customization file for you. This only needs to be done once. Download the <code>kernel-<version>.src.rpm</code> file:
    18 KB (2,946 words) - 14:21, 3 September 2022
  • ...''autoqa/front-ends'' directory to include this and other "Is <component> broken?" front-ends. Liam suggested on coming up with ways to achieve 100% test execution on the test matrix <ref>[[Test_Results:
    84 KB (11,241 words) - 20:09, 19 October 2009
  • * coordinated effort within SIG with limited impact outside SIG functional area, accepted by the SIG ...you maintain the same order of sections so that all of the change proposal pages are uniform.
    12 KB (1,841 words) - 16:23, 9 March 2018
View (previous 20 | ) (20 | 50 | 100 | 250 | 500)