AvengeMedia / AvengeMedia/DankMaterialShell
Confusion about saving to Display Profiles
- Dominant language
- QML
- Stars
- 8.1k
- Forks
- 515
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 102
Description
### Compositor
Hyprland
### If Other, please specify
_No response_
### Distribution
Arch Linux
### If Other, please specify
_No response_
### Select your Installation Method
Distro Packaging
### Was your original Installation method different?
Yes
### If no, specify
_No response_
### dms doctor -vC
Click to expand
## DMS Doctor Report
**System**
- [ok] Operating System: Arch Linux
- ID: arch, Version: rolling, Arch: amd64
- [ok] Architecture: amd64
- [ok] Display Server: Wayland
- WAYLAND_DISPLAY=wayland-1
**Versions**
- [ok] DMS CLI: dms v1.4.6
- /usr/bin/dms
- [ok] Quickshell: Quickshell 0.3.0 (revision , distributed by Arch Linux)
- /usr/bin/qs
- [ok] DMS Shell: v1.4.6
- /usr/share/quickshell/dms
**Installation**
- [ok] DMS Configuration: Found
- /usr/share/quickshell/dms
- [ok] shell.qml: Present
- /usr/share/quickshell/dms/shell.qml
- [info] Install Type: System package
- /usr/share/quickshell/dms
**Compositor**
- [ok] Hyprland: 0.55.4
- /usr/bin/hyprland
- [ok] niri: 26.04
- /usr/bin/niri
- [info] Active: Hyprland
- [warn] Background Blur: Unsupported
- Compositor does not support ext-background-effect-v1
**Quickshell Features**
- [ok] Polkit: Available
- Authentication prompts
- [ok] IdleMonitor: Available
- Idle detection
- [ok] IdleInhibitor: Available
- Prevent idle/sleep
- [ok] ShortcutInhibitor: Available
- Allow shortcut management (niri)
- [ok] BackgroundBlur: Available
- Background blur API support in Quickshell
**Optional Features**
- [ok] accountsservice: Available
- User accounts
- [ok] power-profiles-daemon: Available
- Power profile management
- [ok] logind: Available
- Session management
- [ok] cups-pk-helper: Available
- Printer management
- [info] I2C/DDC: No monitors detected
- External monitor brightness control
- [ok] qt6-imageformats: Installed (1 formats)
- Formats: GIF (/usr/lib/qt6/plugins/imageformats:/usr/lib64/qt6/plugins/imageformats)
- [warn] kimageformats: Not installed
- AVIF, HEIF, JXL support
- [ok] Terminal: kitty, alacritty
- [ok] Network: NetworkManager
- NetworkManager present. Using NM API.
- [warn] matugen: Missing
- Dynamic theming
- [ok] dgop: Installed
- System monitoring
- [ok] cava: Installed
- Audio visualizer
- [info] khal: Not installed
- Calendar events
- [ok] danksearch: Installed
- File search
- [ok] fprintd: Installed
- Fingerprint auth
**Config Files**
- [ok] settings.json: Present
- /home/ak/.config/DankMaterialShell/settings.json
- [ok] clsettings.json: Present
- /home/ak/.config/DankMaterialShell/clsettings.json
- [ok] plugin_settings.json: Present
- /home/ak/.config/DankMaterialShell/plugin_settings.json
- [ok] session.json: Present
- /home/ak/.local/state/DankMaterialShell/session.json
- [info] dms-colors.json: Not yet created
- /home/ak/.cache/DankMaterialShell/dms-colors.json
**Services**
- [warn] dms.service: Disabled
- [info] greetd: Not installed
- Optional greeter service
**Environment**
- [info] QT_QPA_PLATFORMTHEME: Not set
- [info] QS_ICON_THEME: Not set
---
**Summary:** 0 error(s), 4 warning(s), 30 ok
### Description
_TL:DR: I find the `Display Profiles` UX not intuitive and I'm never sure how to save/not save changes._
I'm slightly confused how `Display Profiles` work.
Every time I use it, multiple question arise.
Mostly its unclear for me: When is my profile used/changed
Scenario 1:
I have a profile selected. Now I change something in the `Monitor Configuration` and press `Apply Changes`. Does this also overwrite my profile implicitly? How to explicitly save my profile?
Scenario 2:
I have a profile loaded with my laptop using a docking station with displays. Now I move to a different docking station. For this station I don't have an existing profile and don't want to create one. How to change the display configuration without overwriting my existing profile (if my profile is saved implicitly)?
### Solutions Tried
N/A
### Configuration Details
N/A
### Screenshots/Recordings
Contributor guide
Research direction
Start by reproducing the Display Profiles and Monitor Configuration flows described in the issue on the reported Arch Linux setup, checking what Apply Changes does to a selected profile and how a new docking-station configuration is handled. Document the observed save, overwrite, and discard behavior, including how to preserve an existing profile without creating one.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- desktop
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100