From Fedora Project Wiki

Page title matches

  • ...ed kernel and not from the context of the crashed kernel. Kdump uses kexec to boot into a second kernel whenever system crashes. This second kernel, ofte The first kernel reserves a section of memory that the capture kernel uses to boot. Kexec enables booting the capture kernel without going through the BI
    6 KB (1,022 words) - 22:42, 7 January 2022
  • Before doing anything else, please try to figure out if you're testing the latest version of anaconda - this goes for To check which version of anaconda you're running, you need only watch the scr
    15 KB (2,730 words) - 00:34, 8 August 2018
  • ...the bug and providing the right information in the bug report allows a bug to be resolved quickly. Filing a bug report with little useful information can ...eneric information on filing bugs. This page contains information specific to virtualization bugs.
    19 KB (3,076 words) - 07:58, 20 May 2018
  • Bluetooth is a short range wireless protocol that is used to connect to various low bandwidth I/O devices (like keyboards, mice, headsets). Newer ...gement port in the kernel to the hardware drivers. Applications that want to communicate with the bluetoothd daemon do so over a d-bus api. This includ
    4 KB (547 words) - 13:07, 23 December 2023
  • Safe mode can be used to start Firefox in basic safe configuration. Open terminal and: ...the problem, and if so, copy your data (bookmarks, saved passwords, etc.) to the new profile.
    15 KB (2,275 words) - 06:26, 23 May 2024
  • ...be with IPP Anywhere -- I haven't played with that as much as I would like to have).
    894 bytes (155 words) - 18:47, 31 January 2019
  • ...seem to help, please consider [[#Filing_a_bug_report|filing a bug report]] to help us make Fedora run better on your hardware. ...please have a patience and try to narrow the problem as much you are able to for maintainers.
    61 KB (9,757 words) - 15:59, 8 August 2022
  • ...here or none of the workarounds seem to help, please consider filing a bug to help us make Fedora run better on your hardware. Be prepared to include some information (logs) about your system as well. These should be
    9 KB (1,446 words) - 18:47, 26 March 2017
  • ...page explains information that should be included when filing bugs related to PulseAudio. Problems involving PulseAudio should be filed against [https:// ...etermining whether a sound problem involves PulseAudio, and what component to file a report against if it does not.
    5 KB (783 words) - 16:50, 24 October 2020
  • ...page explains information that should be included when filing bugs related to sound. General sound problems - where the problem is observed across multip ...tailed information on your sound hardware when filing a sound-related bug. To produce this information, run this command:
    4 KB (716 words) - 14:41, 5 October 2015
  • ...here or none of the workarounds seem to help, please consider filing a bug to help us make Fedora run better on your hardware. {{admon/note|Follow the upstream wiki guide|To debug systemd problems please follow the helpful upstream wiki page on the topic:
    4 KB (613 words) - 17:13, 14 June 2015
  • ...gear button to determine type of session you're logging into. If you want to start your session in a different way, read [https://wiki.gnome.org/Initiat ...th [https://community.kde.org/KWin/Wayland this howto]. There doesn't seem to be out-of-the-box support for running a full Wayland session at the moment.
    20 KB (3,199 words) - 12:53, 23 December 2023
  • To find out what kernel version you are currently running, and what machine ar Of course, you should also make sure to file the bug using the appropriate version of Fedora. [[Releases/Rawhide|Ra
    19 KB (3,123 words) - 13:03, 24 April 2016
  • There are several ways and levels to debug MariaDB or MySQL server. ...mmon and easy ways anyone can do, to the styles for which you first need a debug build of the server.
    16 KB (2,400 words) - 09:27, 19 March 2021
  • {{lang|en|fr|page=How to debug Virtualization problems}}
    56 bytes (9 words) - 12:37, 24 April 2016

Page text matches

  • {{lang|en|fr|page=How to debug Virtualization problems}}
    56 bytes (9 words) - 12:37, 24 April 2016
  • Use this guide to determine to which category your proposed change belongs to. * changes to isolated/leaf package without the impact on other packages/rest of the dist
    6 KB (843 words) - 12:00, 25 August 2021
  • This is the starting page for the Fedora port to the MIPS64 architecture. Currently we have chosen to support Loongson 3A and 3B.
    1 KB (192 words) - 10:30, 2 July 2021
  • ...Search Expression HOWTO to have at least some examples how it is supposed to work * [[How_to_debug_Firefox_problems|How to debug Firefox problems]]
    1 KB (175 words) - 18:11, 30 December 2018
  • ...control to the kernel. The bootloader doesn't seem to be used - it seems to be all zero on the factory boot partitions. I don't know what the fedora k Where dummy.boot is 4k of zeros to match google kernel. This is a similar size
    5 KB (529 words) - 21:02, 15 March 2017
  • ...ay images bring additional benefits - a welcome screen with an easy access to test day channels (web, chat), smaller size and customizability. How to build a Test Day Live image:
    7 KB (1,132 words) - 09:21, 14 November 2023
  • ...longer running and no longer being developed. You can use these wiki pages to learn about its history, but please be aware that the information is no lon = Where to see the results of the task?=
    5 KB (758 words) - 14:46, 7 May 2020
  • ...ial-Eclipse (cloned from mercurial repo), then create the spec file to see how fedora packager on eclipse works. Use eclipse-mylyn package as a reference :: Add Internal help content to the wizard - beside the URL
    1 KB (181 words) - 16:51, 7 October 2021
  • ...s are available to chat and help debug issues. This is a great opportunity to meet people who create said software and discuss any issues you might have ...fore or after the official Test Day is also useful and we encourage people to add their results and file bugs even if they cannot make the date. (Note th
    3 KB (570 words) - 12:43, 18 January 2024
  • ...<code>*.debug</code> files in it is unexpectedly small (typically <code>*.debug</code> are larger than the corresponding binary it was stripped from), it's === Useless or incomplete debuginfo packages due to packaging issues ===
    6 KB (890 words) - 19:56, 21 December 2018
  • Please feel free to add more points to the list. If you need to discuss something with the forum moderators, find us at {{fpchat|#fedora-as ...e correct topic categories:''' You should use the correct topic categories to post your questions.
    5 KB (755 words) - 13:22, 17 July 2021
  • Please feel free to add more points to the list. If you need to discuss something with the forum moderators, find us at {{fpchat|#fedora-as ...e correct topic categories:''' You should use the correct topic categories to post your questions.
    5 KB (757 words) - 08:38, 20 March 2019
  • This change proposes to ship debugging information in static libraries. * Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]]
    5 KB (666 words) - 05:39, 17 March 2017
  • ...gs you find at [http://bugzilla.redhat.com Bugzilla], and add your results to the results section. If this page is more than a month old when you arrive == What to test? ==
    5 KB (752 words) - 00:27, 15 November 2016
  • Here is some information about how printing works in Fedora, how to diagnose problems with it, and related topics. ...blems|How to debug printing problems]] page for some information about how to diagnose printing problems and what information is needed when filing bug r
    3 KB (461 words) - 01:03, 4 July 2016
  • The following page will cover how we deal with the kernel in Rawhide. It's a mix of history, policy, and pro ...fore they make it into a stable Fedora release. Of course, we are limited to the usage of rawhide itself, but we have nothing better at the moment.
    7 KB (1,253 words) - 15:53, 4 April 2018
  • |description=Install Fedora CoreOS and debug kernel crashes using kdump as described in [https://docs.fedoraproject.org/ ...can do it via rpm-ostree as described in this documentation, you also need to make sure the kdump.service will be enabled, you can do same via ignition o
    2 KB (268 words) - 16:50, 6 April 2022
  • ...make it easier to trace, profile and observe what programs are doing or to debug when they have crashed. That way debugging, tracing or profiling programs c * Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]]
    14 KB (2,305 words) - 16:44, 12 October 2017
  • ...file. Some tracing and profiling tools don't need the actual source files to provide stack traces or insert probes. So installing the debugsources shoul * Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]]
    11 KB (1,787 words) - 16:45, 12 October 2017
  • * Last updated: <!-- this is an automatic macro — you don't need to change this line --> {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}} ...r, it is still a possibly to upgrade older releases as long as we continue to provide a repository. This will leave those users with an old possibly vuln
    3 KB (481 words) - 19:45, 19 August 2019
View (previous 20 | ) (20 | 50 | 100 | 250 | 500)