Bug 484223 - "TypeError" warning whenever I launch System Setting's sound configuration
Summary: "TypeError" warning whenever I launch System Setting's sound configuration
Status: RESOLVED FIXED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_pulseaudio (other bugs)
Version First Reported In: 6.0.2
Platform: Arch Linux Linux
: NOR minor
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-03-22 09:06 UTC by Guilherme Silva
Modified: 2025-12-22 20:15 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In: 6.6.0 or earlier
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Guilherme Silva 2024-03-22 09:06:21 UTC 
SUMMARY
Whenever I open System Setting's sound configuration, the following warning message pops up in the system journal three times:

qrc:/kcm/kcm_pulseaudio/DeviceListItem.qml:66: TypeError: Cannot read property 'description' of undefined

STEPS TO REPRODUCE
1. Right-click on the "volume" icon in the system tray
2. Click on "Configure Audio Devices..." 
3. Open journalctl -b

OBSERVED RESULT
On my machine, this warning pops up three times:

qrc:/kcm/kcm_pulseaudio/DeviceListItem.qml:66: TypeError: Cannot read property 'description' of undefined

EXPECTED RESULT
No warnings.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.8.1-arch1-1 (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-3570K CPU @ 3.40GHz
Memory: 7,7 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 660/PCIe/SSE2

ADDITIONAL INFORMATION
These warning do not seem to affect the main functionality of the applet in any way.
Comment 1 ratijas 2024-03-23 12:46:31 UTC 
I can confirm, it happens with at least two online audio devices (outputs). That delegate's implementation is a hot mess tbh, it could use a refactor or two.
Comment 2 Nate Graham 2025-12-22 20:15:33 UTC 
This appears to be fixed now.