No Notification sound (Level 0%) - KDE

Hello together!
Since yesterday, I have a problem with notifications sound.
When a notification pops up, there is no sound.
I already learned how to solve it temporarily:
The sound of Notifications is set to the Level 0% (not muted)
I can turn it back to ~50% and then it works again.
But, when I reboot, then it is at 0% again => No Sound again.

How can I create a autostart application or something like that to fix it for me?

  Kernel: 5.16.8-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 11.1.0
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen root=UUID=bbd31a1a-5acd-4143-b97f-a940c8bb5b82
    rw [email protected] quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
  Desktop: KDE Plasma 5.24.0 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11 vt: 1 dm: SDDM
    Distro: Garuda Linux base: Arch Linux
  Type: Laptop System: Medion product: S4216 v: 1.0 serial: <superuser required>
  Mobo: Medion model: S4216 v: 1.0 serial: <superuser required> UEFI: American Megatrends v: 505
    date: 09/28/2012
  ID-1: BAT0 charge: 31.0 Wh (97.2%) condition: 31.9/36.4 Wh (87.6%) volts: 16.5 min: 14.4
    model: B34 type: Li-ion serial: N/A status: Not charging
  Info: model: Intel Core i5-3317U bits: 64 type: MT MCP arch: Ivy Bridge family: 6
    model-id: 0x3A (58) stepping: 9 microcode: 0x21
  Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache: L1: 128 KiB
    desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB L3: 3 MiB desc: 1x3 MiB
  Speed (MHz): avg: 2348 high: 2369 min/max: 800/2600 scaling: driver: intel_cpufreq
    governor: schedutil cores: 1: 2369 2: 2333 3: 2333 4: 2359 bogomips: 13568
  Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2
    mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling
  Type: srbds status: Vulnerable: No microcode
  Type: tsx_async_abort status: Not affected
  Device-1: Intel 3rd Gen Core processor Graphics vendor: Pegatron driver: i915 v: kernel
    bus-ID: 00:02.0 chip-ID: 8086:0166 class-ID: 0300
  Device-2: Microdia USB 2.0 Camera type: USB driver: uvcvideo bus-ID: 1-1.1:3
    chip-ID: 0c45:6457 class-ID: 0e02
  Display: x11 server: X.Org compositor: kwin_x11 driver: loaded: intel
    unloaded: modesetting alternate: fbdev,vesa display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 507x285mm (20.0x11.2") s-diag: 582mm (22.9")
  Monitor-1: VGA1 res: 1920x1080 hz: 60 dpi: 92 size: 530x300mm (20.9x11.8") diag: 609mm (24")
  OpenGL: renderer: Mesa DRI Intel HD Graphics 4000 (IVB GT2) v: 4.2 Mesa 21.3.5 compat-v: 3.0
    direct render: Yes
  Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: Pegatron
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:1e20 class-ID: 0403
  Sound Server-1: ALSA v: k5.16.8-zen1-1-zen running: yes
  Sound Server-2: PulseAudio v: 15.0 running: no
  Sound Server-3: PipeWire v: 0.3.45 running: yes
  Device-1: Intel Centrino Wireless-N 2230 driver: iwlwifi v: kernel bus-ID: 02:00.0
    chip-ID: 8086:0887 class-ID: 0280
  IF: wlp2s0 state: up mac: <filter>
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Pegatron
    driver: r8169 v: kernel port: e000 bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp3s0 state: down mac: <filter>
  IF-ID-1: docker0 state: down mac: <filter>
  Device-1: Intel Centrino Bluetooth Wireless Transceiver type: USB driver: btusb v: 0.8
    bus-ID: 1-1.4:5 chip-ID: 8087:07da class-ID: e001
  Report: bt-adapter ID: hci0 rfk-id: 1 state: up address: <filter>
  Local Storage: total: 223.57 GiB used: 37.78 GiB (16.9%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: GOODRAM model: SSDPR-CL100-240-G2 size: 223.57 GiB
    block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: V4.7
    scheme: GPT
  ID-1: / raw-size: 104.87 GiB size: 104.87 GiB (100.00%) used: 37.75 GiB (36.0%) fs: btrfs
    dev: /dev/sda5 maj-min: 8:5
  ID-2: /boot/efi raw-size: 99 MiB size: 95 MiB (95.96%) used: 29.9 MiB (31.4%) fs: vfat
    dev: /dev/sda2 maj-min: 8:2
  ID-3: /home raw-size: 104.87 GiB size: 104.87 GiB (100.00%) used: 37.75 GiB (36.0%) fs: btrfs
    dev: /dev/sda5 maj-min: 8:5
  ID-4: /var/log raw-size: 104.87 GiB size: 104.87 GiB (100.00%) used: 37.75 GiB (36.0%)
    fs: btrfs dev: /dev/sda5 maj-min: 8:5
  ID-5: /var/tmp raw-size: 104.87 GiB size: 104.87 GiB (100.00%) used: 37.75 GiB (36.0%)
    fs: btrfs dev: /dev/sda5 maj-min: 8:5
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: zram size: 7.65 GiB used: 23 MiB (0.3%) priority: 100 dev: /dev/zram0
  System Temperatures: cpu: 59.0 C mobo: N/A
  Fan Speeds (RPM): N/A
  Processes: 273 Uptime: 32m wakeups: 1 Memory: 7.65 GiB used: 3.31 GiB (43.3%) Init: systemd
  v: 250 tool: systemctl Compilers: gcc: 11.1.0 clang: 13.0.1 Packages: 1834 pacman: 1829 lib: 392
  flatpak: 5 Client: shell wrapper v: 5.1.16-release inxi: 3.3.12
Garuda (2.5.4-2):
  System install date:     2022-01-22
  Last full system update: 2022-02-14
  Is partially upgraded:   No
  Relevant software:       NetworkManager
  Windows dual boot:       Probably (Run as root to verify)
  Snapshots:               Snapper
  Failed units:            

It looks like a bunch of bugs related to notification sounds in KDE 5.24 were identified here: 449828 – Login notification doesn't play the sound queue on login since the system was updated to KDE Plasma 5.24

I'm wondering if the issue you've noticed might be related. :thinking:


Yeah could be. What should I do now?

Since it has already been reported, there isn't much you can do except keep an eye on the reported bug for updates, and wait for the bug fix to come down. I know the KDE team has been working really hard recently to prioritize squashing bugs, but unfortunately it is just impossible to say how long it might take.

1 Like

Okay, Thanks.
I think I'll close this issue and start watching.

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.