How to View and Filter System Logs in Ubuntu Using the Logs App

When an application unexpectedly crashes, a USB peripheral fails to connect, or your system experiences an unprompted slowdown, Linux system logs hold the exact forensic details needed to diagnose the problem. While advanced administrators frequently query system logs via terminal utilities like journalctl, Ubuntu includes a powerful, graphical log viewer called GNOME Logs. This built-in application provides an intuitive window into system events, allowing everyday users to inspect errors, security events, and hardware alerts without memorising terminal commands.

Understanding Log Categories in Ubuntu

The Ubuntu Logs application parses systemd journal streams and classifies events into easily digestible categories accessible from the left-hand sidebar:

• Important: Displays high-priority warnings, critical system failures, kernel panics, and unexpected application terminations. This should be your first stop when investigating a crash.
• All: A chronological timeline of every informational notice, service start, and system event recorded by your current system session.
• Applications: Log entries produced directly by desktop software, web browsers, media players, and GNOME extensions.
• System: Background daemon messages, scheduled cron tasks, power state changes, and package manager operations.
• Security: Authentication attempts, sudo privileges executed, SSH handshakes, and screen lock events.
• Hardware: Kernel driver notifications, USB device connections, graphics driver messages, and disk controller events.

How to Open the Logs Application in Ubuntu

Accessing the graphical log viewer is straightforward on any standard Ubuntu desktop:

1. Press the Super (Windows) key on your keyboard or click the Show Applications grid icon on your dock.
2. Type Logs into the top search bar.
3. Click on the Logs icon (depicting a notepad with lines of text).
4. The main GNOME Logs interface will launch, automatically populating with recent log events.

How to Search and Filter Specific Error Events

Modern Linux systems generate thousands of routine informational log lines each hour. Finding the specific failure you are troubleshooting requires applying targeted filters:

1. Select the relevant category from the left sidebar, such as Important for crashes or Hardware for peripheral issues.
2. Click the Magnifying Glass icon in the top header bar (or press Ctrl + F).
3. Type keywords related to the issue, such as the application name (e.g., firefox, pulseaudio, or nvidia), or generic failure terms like failed, denied, or timed out.
4. The list instantly filters to show only log lines matching your search query.

Inspecting Detailed Log Messages and Metadata

Clicking on any log entry in the main list expands a detailed technical summary panel:

• Timestamp: The exact date, hour, minute, second, and microsecond when the event occurred.
• Message Body: The complete unedited error string output by the application or system daemon.
• Audit & Process ID: The specific PID (Process Identifier) and system service unit responsible for generating the log line.
• Exporting Details: To share an error trace on Ubuntu forums or technical bug trackers, click the export or copy button in the top corner to copy the full traceback to your clipboard.