Bug 494515 - Nothing is shown in audio section when opening systemsettings and go to audio first, shown when switch settings then back to audio
Summary: Nothing is shown in audio section when opening systemsettings and go to audio...
Status: RESOLVED DUPLICATE of bug 493266
Alias: None
Product: systemsettings
Classification: Applications
Component: general (show other bugs)
Version: 6.2.0
Platform: Arch Linux Linux
: NOR minor
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-10-11 09:50 UTC by noreporter
Modified: 2024-10-11 10:57 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Audio configuration not shown when open systemsettings and go to audio first (64.81 KB, image/png)
2024-10-11 10:04 UTC, noreporter 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description noreporter 2024-10-11 09:50:54 UTC 
SUMMARY


STEPS TO REPRODUCE
1. Open systemsettings
2. Go to audio section, nothing is shown
3. switch to other settings then back to audio and it is shown
4. Open systemsettings in the terminal and you will get an error saying :org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo.monitor"(this can be different depending on the audio device you are using as shown in this brief bug report on archlinux forums: https://bbs.archlinux.org/viewtopic.php?id=300060)


OBSERVED RESULT
Nothing in audio setting is shown when you open systemsettings and go to audio settings first

EXPECTED RESULT
There would be options to configure audio shown in the audio section when opening systemsettings and go to audio first

SOFTWARE/OS VERSIONS
Linux: Arch Linux
KDE Plasma Version: 6.2
KDE Frameworks Version: 6.6.0
Qt Version: 6.7.3
Comment 1 noreporter 2024-10-11 10:04:35 UTC 
Created attachment 174680 [details]
Audio configuration not shown when open systemsettings and go to audio first
Comment 2 Antonio Rojas 2024-10-11 10:57:51 UTC 

*** This bug has been marked as a duplicate of bug 493266 ***