Problem Solving & Issue Reporting
This page includes general information on how to investigate and report issues with Fedora Workstation.
Workstation includes a set of graphical and command line tools which can be used to investigate and diagnose issues, if they happen.
Graphical tools include:
System Monitor: can be used to see if system resources are being exceeded, and which processes are using the most resources.
Logs: a graphical viewer app for system and application logs.
Problem Reporting: automatically detects crashes, and allows reporting of crash data. In some cases the Problem Reporting tool will link to existing issue reports for a crash.
Command line diagnostic tools which are preinstalled in Fedora Workstation include:
top: command line system monitor.
journalctl: command line interface for viewing systemd logs. Learn how to get started with journalctl.
coredumpctl: command line interface for analyzing software crashes. Fedora Magazine has a good article on getting started with coredumpctl.
Issues that need to be tracked as part of the Fedora release process, such as potential release blockers, should be reported against the correct component in Red Hat Bugzilla.
For other issues, it is recommended to create reports directly with the relevant upstream project. The GNOME Project is the upstream for much of the software that makes up Fedora Workstation. Issues with GNOME components can be reported using GNOME’s Gitlab instance.
When the system is running out of memory, Fedora Workstation automatically forces processes to quit, in order to ensure that the system can continue to function.
If applications or processes suddenly close, it could be due to memory pressure. Check the logs to see if a OOM event was recorded, and check system resources to see if your system is approaching its memory limits.
Want to help? Learn how to contribute to Fedora Docs ›