AvengeMedia / AvengeMedia/DankMaterialShell

Audio devices not detected in Control Center after updating DankMaterialShell (PipeWire running)

Open
#1,332 11 comments 5 reactions 0 assignees View on GitHub
bug
Dominant language
QML
Stars
8.1k
Forks
515
Avg merge
1d 8h
Merged PRs (30d)
102

Description

### Compositor

- [ ] Niri
- [x] Hyprland
- [ ] MangoWC (dwl)
- [ ] Sway

### Distribution

- [x] Arch Linux
- [ ] CachyOS
- [ ] Fedora
- [ ] NixOS
- [ ] Debian
- [ ] Ubuntu
- [ ] Gentoo
- [ ] OpenSUSE
- [ ] Other (specify below)

### If Other, please specify

_No response_

### dms version

dms v1.0.3

### Description

On startup, the volume/mute controls in DankMaterialShell report "no output device" even though PipeWire shows an active sink. This prevents using the integrated volume control, cycling audio outputs, or muting/unmuting

![Image](https://github.com/user-attachments/assets/f04995c0-5601-439a-b85c-138ffd7dbac9)

### Expected Behavior

Volume and mute controls should reflect the active PipeWire sink.
Cycling audio outputs should work normally.
No “No output device” message if PipeWire nodes are available.

### Steps to Reproduce & Installation Method

Install DankMaterialShell using the official installer on a clean Arch setup Using :
curl -fsSL https://install.danklinux.com | sh

Log into the DMS session (Wayland / Hyprland).
Open the Control Center.
Observe the audio section showing:
No output device
No input device

### Error Messages/Logs

wpctl status

PipeWire 'pipewire-0' [1.4.9, nihvh@archlinux, cookie:1967224397]
└─ Clients:
32. WirePlumber [1.4.9, nihvh@archlinux, pid:997]
33. pipewire [1.4.9, nihvh@archlinux, pid:999]
46. WirePlumber [export] [1.4.9, nihvh@archlinux, pid:997]
62. xdg-desktop-portal [1.4.9, nihvh@archlinux, pid:1975]
63. xdg-desktop-portal-hyprland [1.4.9, nihvh@archlinux, pid:2073]
64. Blueman [1.4.9, nihvh@archlinux, pid:1885]
65. quickshell [1.4.9, nihvh@archlinux, pid:1941]
66. quickshell [1.4.9, nihvh@archlinux, pid:1941]
67. wpctl [1.4.9, nihvh@archlinux, pid:11622]

Audio
├─ Devices:
│ 58. Ryzen HD Audio Controller [alsa]
│ 59. HDA NVidia [alsa]

├─ Sinks:
│ * 47. Ryzen HD Audio Controller Analog Stereo [vol: 0.50 MUTED]

├─ Sources:
│ * 56. Ryzen HD Audio Controller Analog Stereo [vol: 1.00]

├─ Filters:

└─ Streams:

Video
├─ Devices:
│ 52. HP TrueVision HD Camera [v4l2]
│ 53. HP TrueVision HD Camera [v4l2]

├─ Sinks:

├─ Sources:
│ * 60. HP TrueVision HD Camera (V4L2)

├─ Filters:

└─ Streams:

Settings
└─ Default Configured Devices:
~ ❯

dms ipc call audio status
Audio Status:
Output: No sink available
Input: No source available
~ ❯

### Screenshots/Recordings

_No response_

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the problem in the Control Center and compare `wpctl status` with `dms ipc call audio status`; the report shows PipeWire sinks and sources present while DMS reports none. Trace the audio-status entry point used by that IPC command and verify that the Control Center detects the available devices, volume controls, output cycling, and mute state.

Written by the indexing model from the issue text.

Assessment

Tech stack
arch-linux, linux
Domain
audio-video-rtc, desktop
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.