DMS fauling to start - Start-limit-hit

### Compositor

Hyprland

### If Other, please specify

_No response_

### Distribution

CachyOS

### If Other, please specify

_No response_

### Select your Installation Method

DankInstaller

### 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: CachyOS
- ID: cachyos, Version: rolling, Arch: amd64
- [ok] Architecture: amd64
- [ok] Display Server: Wayland
- WAYLAND_DISPLAY=wayland-1

**Versions**
- [ok] DMS CLI: dms v1.6.1
- /usr/bin/dms
- [ok] Quickshell: Quickshell 0.3.1 (revision , distributed by Arch Linux)
- /usr/bin/qs
- [ok] DMS Shell: v1.6.1
- /run/user/1000/danklinux-shell/d83248ba9119b48a

**Installation**
- [ok] DMS Configuration: Found
- /run/user/1000/danklinux-shell/d83248ba9119b48a
- [ok] shell.qml: Present
- /run/user/1000/danklinux-shell/d83248ba9119b48a/shell.qml
- [info] Install Type: Unknown
- /run/user/1000/danklinux-shell/d83248ba9119b48a

**Compositor**
- [ok] Hyprland: 0.56.2
- /usr/bin/hyprland
- [ok] niri: 26.04
- /usr/bin/niri
- [info] Active: Hyprland
- [ok] Background Blur: Supported
- Compositor supports 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 (5 formats)
- Formats: WebP, TIFF, GIF, JP2, ICNS (/usr/lib/qt6/plugins/imageformats:/usr/lib/qt/plugins/imageformats:/usr/lib64/qt6/plugins/imageformats)
- [ok] kimageformats: Installed (4 formats)
- Formats: AVIF, HEIF, JXL, EXR (/usr/lib/qt6/plugins/imageformats:/usr/lib64/qt6/plugins/imageformats)
- [ok] Terminal: kitty, alacritty
- [ok] Network: NetworkManager
- NetworkManager present. Using NM API.
- [ok] matugen: Installed
- Dynamic theming
- [ok] cava: Installed
- Audio visualizer
- [info] khal: Not installed
- Calendar events
- [ok] danksearch: Installed
- File search
- [ok] dankcalendar: Installed
- Calendar app
- [info] fprintd: Not installed
- Fingerprint auth
- [info] adw-gtk3: Not installed
- GTK3 dynamic theming; without it the global CSS override applies

**Config Files**
- [ok] settings.json: Present
- /home/siobhanrfm/.config/DankMaterialShell/settings.json
- [info] clsettings.json: Not yet created
- /home/siobhanrfm/.config/DankMaterialShell/clsettings.json
- [info] plugin_settings.json: Not yet created
- /home/siobhanrfm/.config/DankMaterialShell/plugin_settings.json
- [ok] session.json: Present
- /home/siobhanrfm/.local/state/DankMaterialShell/session.json
- [ok] dms-colors.json: Present
- /home/siobhanrfm/.cache/DankMaterialShell/dms-colors.json

**Services**
- [error] dms.service: enabled, failed
- [info] greetd: disabled

**Environment**
- [info] QT_QPA_PLATFORMTHEME: Not set
- [info] QT_QPA_PLATFORMTHEME_QT6: Not set
- [info] QS_ICON_THEME: Not set
- [warn] XDG_MENU_PREFIX: Not set
- Dolphin file associations and 'Open with…' dialog may be empty. Set XDG_MENU_PREFIX=plasma- in your compositor's environment block.

**Fonts**
- [ok] Normal Font: Inter Variable
- /run/user/1000/danklinux-shell/d83248ba9119b48a/DankCommon/assets/fonts/inter/InterVariable.ttf
- [ok] Monospace Font: Fira Code
- /run/user/1000/danklinux-shell/d83248ba9119b48a/DankCommon/assets/fonts/nerd-fonts/FiraCodeNerdFont-Regular.ttf

---
**Summary:** 1 error(s), 1 warning(s), 33 ok

### Description

DMS is failing to start on login, and if I start it manually it will fail to see any audio devices.

Here's the output of journalctl --user -xeu dms.service for additional context.

Click to expand
❯ journalctl --user -xeu dms.service
░░ This usually indicates a programming error in the crashing program and
░░ should be reported to its vendor as a bug.
Sep 11 19:40:07 STARDREAM dms[8546]: ERROR go: UI exited: exit status 255
Sep 11 19:40:07 STARDREAM systemd[1128]: dms.service: Main process exited, code=exited, status=255/EXCEPTION
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ An ExecStart= process belonging to unit UNIT has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 255.
Sep 11 19:40:07 STARDREAM systemd[1128]: dms.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit UNIT has entered the 'failed' state with result 'exit-code'.
Sep 11 19:40:07 STARDREAM systemd[1128]: Failed to start Dank Material Shell (DMS).
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit UNIT has finished with a failure.
░░
░░ The job identifier is 808 and the job result is failed.
Sep 11 19:40:08 STARDREAM systemd[1128]: dms.service: Scheduled restart job, restart counter is at 6.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ Automatic restarting of the unit UNIT has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Sep 11 19:40:08 STARDREAM systemd[1128]: dms.service: Start request repeated too quickly.
░░ This usually indicates a programming error in the crashing program and
░░ should be reported to its vendor as a bug.
Sep 11 19:40:07 STARDREAM dms[8546]: ERROR go: UI exited: exit status 255
Sep 11 19:40:07 STARDREAM systemd[1128]: dms.service: Main process exited, code=exited, status=255/EXCEPTION
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ An ExecStart= process belonging to unit UNIT has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 255.
Sep 11 19:40:07 STARDREAM systemd[1128]: dms.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit UNIT has entered the 'failed' state with result 'exit-code'.
Sep 11 19:40:07 STARDREAM systemd[1128]: Failed to start Dank Material Shell (DMS).
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit UNIT has finished with a failure.
░░
░░ The job identifier is 808 and the job result is failed.
Sep 11 19:40:08 STARDREAM systemd[1128]: dms.service: Scheduled restart job, restart counter is at 6.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ Automatic restarting of the unit UNIT has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Sep 11 19:40:08 STARDREAM systemd[1128]: dms.service: Start request repeated too quickly.
Sep 11 19:40:08 STARDREAM systemd[1128]: dms.service: Failed with result 'start-limit-hit'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit UNIT has entered the 'failed' state with result 'start-limit-hit'.
Sep 11 19:40:08 STARDREAM systemd[1128]: Failed to start Dank Material Shell (DMS).
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit UNIT has finished with a failure.
░░
░░ The job identifier is 853 and the job result is failed.
Sep 11 19:40:10 STARDREAM systemd[1128]: dms.service: Start request repeated too quickly.
Sep 11 19:40:10 STARDREAM systemd[1128]: dms.service: Failed with result 'start-limit-hit'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit UNIT has entered the 'failed' state with result 'start-limit-hit'.
Sep 11 19:40:10 STARDREAM systemd[1128]: Failed to start Dank Material Shell (DMS).
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit UNIT has finished with a failure.
░░
░░ The job identifier is 920 and the job result is failed.

As it is now, logging into hyprland just creates a grey screen.

### Solutions Tried

_No response_

### Configuration Details

_No response_

### Screenshots/Recordings

_No response_

Start with the dms.service failure in journalctl --user -xeu dms.service, then inspect the reported DMS CLI, shell.qml, and login startup context. Compare service startup with manual startup and verify that the service no longer exits with status 255 or start-limit-hit and that audio devices are detected.

Written by the indexing model from the issue text.