Ubuntu Support Template: A Brief Explanation

Support and Help Start Here
1

In this guide, users will be able to copy the raw version of the template.

It was created with Markdown and if you want to use it all you have to do is copy and paste into a new topic.

Note that the example in the next post uses backticks to allow users to copy/paste the template into a plaintext editor of your choice.

This should retain the Markdown formatting and when you copy/paste back into a new post, the correct Markdown format should still be visible in your post.

Please use the copy code function in Discourse to retain the correct formatting

copy code
copy code1175×336 58.8 KB

The second part will offer brief explanations of each field as well as commands to use to gather the required information.

Bear in mind that while we definitely encourage the use of the template it is not an obligation.

Remember:

whichever fields you are not using should be removed/cleared BEFORE posting. This helps keep things clean and organized for everyone.

Very Important:

please use code tags to wrap terminal or script output. We cannot stress enough the importance for readability and analysis. A wall of terminal output is hard to read and follow and makes offering help that much harder for the volunteers who power this site.

To add code tags use one of the following methods:

  1. Highlight the text and click on </> in the composer

  2. Highlight the text and use Ctrl + E on the keyboard

  3. Add 3 backticks before and after where you intend pasting, then paste the output between the sets of backticks

If you have questions or comments, please open a new topic in Site Feedback

Thanks

4 Likes
2 
Ubuntu Support Template

**Ubuntu Version**:
Example: 22.04 LTS, 24.04, 25.10

**Desktop Environment (if applicable)**:
Example: GNOME, KDE Plasma, XFCE, Budgie, etc.

**Problem Description**:
Describe what you’re trying to do and what happens instead.
If you can easily reproduce the problem, include the steps so others can try.

Example:

Open Settings → Displays
Try to change resolution
Screen goes black

**Relevant System Information**:
Include any details that might help (e.g., hardware, drivers, or special configurations).

**Screenshots or Error Messages**:
If applicable, paste error messages or screenshots.
We prefer copy-pasted text and screenshots instead of photos of screens.

For multi-line text or logs, wrap them in triple backticks like this or highlight the text and use </> in the composer:

`sudo dmesg | tail -20`

**What I’ve Tried**:
List the solutions or workarounds you’ve already attempted.

**Before Posting**:
:mag: Please check if similar issues have already been reported and resolved.
3 Likes
3

The following section assumes you are running commands from the terminal.

On Ubuntu or flavours, use the keyboard shortcut Ctrl + Alt + T or search the Applications menu.

This is the easiest and usually most accurate way to gather the information that the volunteer helpers need to assist other users.

Below is a concise explanation for each section of the Ubuntu Support Template with commands that should work on all Ubuntu versions and flavours (including Ubuntu, Kubuntu, Xubuntu, Lubuntu, Ubuntu Budgie, Ubuntu MATE, etc.).

1. Ubuntu Version

What to provide:
The exact Ubuntu release number (e.g., 22.04 LTS, 24.04, 25.10).

Command:

lsb_release -a

Alternative:

cat /etc/os-release

2. Desktop Environment (if applicable)

What to provide:
Your graphical desktop (e.g., GNOME, KDE Plasma, XFCE, LXQt, MATE, Budgie).

Command:

echo $XDG_CURRENT_DESKTOP

If that’s empty:

echo $DESKTOP_SESSION

3. Problem Description

What to provide:

  • What you’re trying to do
  • What happens instead
  • Clear reproduction steps

No command required — this should be written clearly and step-by-step.

Example format:

1. Open Settings → Displays
2. Change resolution
3. Screen goes black

4. Relevant System Information

What to provide:
Hardware, drivers, kernel version, GPU info, special configurations.

Commands:

uname -r

lspci

lsusb

For full hardware summary:

sudo lshw -short

5. Screenshots or Error Messages

What to provide:

  • Copy-paste error messages (preferred over photos)
  • Terminal output inside triple backticks

Example:

sudo dmesg | tail -20

To capture recent journal logs:

journalctl -xe

6. What I’ve Tried

What to provide:
List troubleshooting steps already attempted (reinstalls, driver changes, config edits, etc.).

No command required — written summary only.

7. Before Posting

What to do:
Search for similar issues first using the powerful Discourse search options.

Bear in mind that this is not supposed to be a comprehensive guide, merely a tool to try and help point users in the right direction.

We hope to keep this as fresh and updated as possible as a reference point.

2 Likes