Skip to content

Conversation

@omc8db
Copy link
Contributor

@omc8db omc8db commented Oct 12, 2025

The GNOME command listed in the documentation was subtly wrong - it would list a shortened output name like "HDMI-1" instead of "HDMI-A-1", which gamescope would fail to recognize.

The new command in this PR works across all desktop environments and uses the same source of truth for output names that gamescope reads from. It also has a shorter, easier to read output format:

$ grep -r '^connected' /sys/class/drm/*/status | grep -Po 'card.-\K.*'
DP-2/status:connected
eDP-1/status:connected

The GNOME command listed in the documentation was subtly wrong - it would list a shortened output name like "HDMI-1" instead of "HDMI-A-1", which gamescope would fail to recognize.

The new command in this PR works across all desktop environments and uses the same source of truth for output names that gamescope reads from. It also has a shorter, easier to read output format:

```
$ grep -r '^connected' /sys/class/drm/*/status | grep -Po 'card.-\K.*'
DP-2/status:connected
eDP-1/status:connected
```
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @omc8db, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request resolves a critical issue in the HTPC mode boot documentation where the recommended GNOME command for identifying display outputs generated incorrect monitor names, causing gamescope to fail. The change introduces a more robust and universal command that accurately retrieves display output names, ensuring proper functionality across all desktop environments and simplifying the configuration process for users.

Highlights

  • Fixes Incorrect Monitor Names: The previous GNOME command (gnome-randr) for identifying display outputs produced shortened names (e.g., "HDMI-1") that gamescope failed to recognize for HTPC mode boot.
  • Introduces Universal Command: A new grep command is now used, which provides full and correct output names (e.g., "HDMI-A-1") and works consistently across all desktop environments.
  • Improved Output Format: The new command also offers a shorter and easier-to-read output format for display names.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request aims to improve the documentation by providing a more reliable, universal command to find display output names for HTPC setups. This is a good improvement over the previous desktop-environment-specific commands. However, the new command provided is incorrect and will not produce the desired output. I have provided a review comment with a corrected, more user-friendly command.


```
gnome-randr
grep -r '^connected' /sys/class/drm/*/status | grep -Po 'card.-\K.*'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The provided command has an incorrect grep pattern that will likely produce no output. Additionally, even if the pattern were corrected to match the intended logic, the output would include extra text (like /status:connected) that the user would need to manually remove.

This suggested command is more robust and user-friendly. It uses grep -l to get the file paths of connected monitors and then awk to cleanly extract just the connector names, which is exactly what the user needs to copy.

Suggested change
grep -r '^connected' /sys/class/drm/*/status | grep -Po 'card.-\K.*'
grep -l '^connected' /sys/class/drm/*/status | awk -F'[-/]' '{print $(NF-1)}'

@Zeglius Zeglius merged commit 28e2b95 into bazzite-org:main Nov 27, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants