Sometimes when I startup my desktop, the headphones aren't displayed as an option and I can't seem to figure out why it only happens some of the time. Here's what I would normally see:

Here's what I see when it's not working:

Here's some system details that may be useful
I've tried restarting pipewire but that doesn't fix it, any suggestions on what I can try the next time it happens (or if there are any logs that would help in troubleshooting this issue)? The only way I can get it working again is with a reboot, which works every time.
NOTE: There was another post of a user having issues with a beelink device (I'm also using beelink), except their issues were the microphone selection over headphone selection, and that issue was resolved with the upgrade to 23.10 (and not issues reported on 24.04). I wonder if my issue is somehow related to theirs? (just guessing here)

Here's what I see when it's not working:

Here's some system details that may be useful
Code:
loki@valhalla:~$ fastfetch `.:/ossyyyysso/:. loki@valhalla .:oyyyyyyyyyyyyyyyyyyo:` ------------- -oyyyyyyyodMMyyyyyyyysyyyyo- OS: Kubuntu x86_64 -syyyyyyyyyydMMyoyyyydmMMyyyyys- Host: SER oyyysdMysyyyydMMMMMMMMMMMMMyyyyyyyo Kernel: Linux 6.8.0-57-generic `oyyyydMMMMysyysoooooodMMMMyyyyyyyyyo` Uptime: 31 mins oyyyyyydMMMMyyyyyyyyyyyysdMMysssssyyyo Packages: 3182 (dpkg), 11 (snap) -yyyyyyyydMysyyyyyyyyyyyyyysdMMMMMysyyy- Shell: bash 5.2.21 oyyyysoodMyyyyyyyyyyyyyyyyyyydMMMMysyyyo Display (VG27WQ): 2560x1440 @ 144 Hz in 27" [External] * yyysdMMMMMyyyyyyyyyyyyyyyyyyysosyyyyyyyy Display (VG27WQ): 2560x1440 @ 144 Hz in 27" [External] yyysdMMMMMyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy DE: KDE Plasma 5.27.12 oyyyyysosdyyyyyyyyyyyyyyyyyyydMMMMysyyyo WM: KWin (X11) -yyyyyyyydMysyyyyyyyyyyyyyysdMMMMMysyyy- WM Theme: Qogir oyyyyyydMMMysyyyyyyyyyyysdMMyoyyyoyyyo Theme: Breeze (Light) [Qt], Breeze [GTK2/3] `oyyyydMMMysyyyoooooodMMMMyoyyyyyyyyo Icons: breeze [Qt], breeze [GTK2/3/4] oyyysyyoyyyysdMMMMMMMMMMMyyyyyyyyo Font: Noto Sans (10pt) [Qt], Noto Sans (10pt) [GTK2/3/4] -syyyyyyyyydMMMysyyydMMMysyyyys- Cursor: breeze (24px) -oyyyyyyydMMyyyyyyysosyyyyo- Terminal: konsole 23.8.5 ./oyyyyyyyyyyyyyyyyyyo/. CPU: AMD Ryzen 5 5600H (12) @ 4.28 GHz `.:/oosyyyysso/:.` GPU: AMD Radeon Vega Series / Radeon Vega Mobile Series [Integrated] Memory: 2.89 GiB / 28.29 GiB (10%) Swap: 0 B / 1.91 GiB (0%) Disk (/): 181.49 GiB / 455.00 GiB (40%) - ext4 Local IP (enp1s0): 192.168.87.250/24 Locale: en_US.UTF-8 loki@valhalla:~$ lspci -v | grep Audio -a3 Kernel driver in use: amdgpu Kernel modules: amdgpu 04:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Radeon High Definition Audio Controller Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Radeon High Definition Audio Controller Flags: bus master, fast devsel, latency 0, IRQ 73, IOMMU group 5 Memory at fccc8000 (32-bit, non-prefetchable) [size=16K] Capabilities: <access denied> -- Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 04:00.5 Multimedia controller: Advanced Micro Devices, Inc. [AMD] ACP/ACP3X/ACP6x Audio Coprocessor (rev 01) Subsystem: Advanced Micro Devices, Inc. [AMD] ACP/ACP3X/ACP6x Audio Coprocessor Flags: fast devsel, IRQ 70, IOMMU group 5 Memory at fcc80000 (32-bit, non-prefetchable) [size=256K] Capabilities: <access denied> Kernel modules: snd_pci_acp3x, snd_rn_pci_acp3x, snd_pci_acp5x, snd_pci_acp6x, snd_acp_pci, snd_rpl_pci_acp6x, snd_pci_ps, snd_sof_amd_renoir, snd_sof_amd_rembrandt, snd_sof_amd_vangogh, snd_sof_amd_acp63 04:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h/19h HD Audio Controller DeviceName: HD Audio Controller Subsystem: Realtek Semiconductor Co., Ltd. Family 17h/19h HD Audio Controller Flags: bus master, fast devsel, latency 0, IRQ 74, IOMMU group 5 Memory at fccc0000 (32-bit, non-prefetchable) [size=32K] Capabilities: <access denied> loki@valhalla:~$
NOTE: There was another post of a user having issues with a beelink device (I'm also using beelink), except their issues were the microphone selection over headphone selection, and that issue was resolved with the upgrade to 23.10 (and not issues reported on 24.04). I wonder if my issue is somehow related to theirs? (just guessing here)
Comment