KDE Plasma 5.18.5 crashing & restarts when i click on Audio volume

I'm using Manjaro unstable and when i left click on Audio Volume Plasma Desktop crashing & restarts.
Here's my "journal -xe " output:

Blockquote
[panos@phobos ~]$ journalctl -xe
#3 0x00007ff4a18c3422 start_thread (libpthread.so.0 + 0x9422)
#4 0x00007ff4a20dcb83 __clone (libc.so.6 + 0xffb83)
-- Subject: Process 2177 (plasmashell) dumped core
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/technical-issues-and-assistance
-- Documentation: man:core(5)
--
-- Process 2177 (plasmashell) crashed and dumped core.
--
-- This usually indicates a programming error in the crashing program and
-- should be reported to its vendor as a bug.
Μαΐ 16 03:22:01 phobos.daemons.gr systemd[1]: systemd-coredump@2-12228-0.service: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/technical-issues-and-assistance
--
-- The unit systemd-coredump@2-12228-0.service has successfully entered the 'dead' state.
Μαΐ 16 03:22:01 phobos.daemons.gr kernel: audit: type=1131 audit(1589588521.247:114): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-coredump@2-12228-0 comm=">
Μαΐ 16 03:22:01 phobos.daemons.gr audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-coredump@2-12228-0 comm="systemd" exe="/usr/lib/system>
Μαΐ 16 03:22:01 phobos.daemons.gr plasmashell[12227]: file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:482:13: QML Label: Binding loop detected fo>
Μαΐ 16 03:22:01 phobos.daemons.gr plasmashell[12227]: file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:523:9: QML Label: Binding loop detected for>
Μαΐ 16 03:22:01 phobos.daemons.gr plasmashell[12227]: file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:543:5: QML Label: Binding loop detected for>
Μαΐ 16 03:22:01 phobos.daemons.gr audit: AUDIT1334 prog-id=20 op=UNLOAD
Μαΐ 16 03:22:01 phobos.daemons.gr audit: AUDIT1334 prog-id=19 op=UNLOAD
Μαΐ 16 03:22:01 phobos.daemons.gr kernel: audit: type=1334 audit(1589588521.380:115): prog-id=20 op=UNLOAD
Μαΐ 16 03:22:01 phobos.daemons.gr kernel: audit: type=1334 audit(1589588521.380:116): prog-id=19 op=UNLOAD
Μαΐ 16 03:22:01 phobos.daemons.gr kded5[1521]: org.kde.knotifications: warning: failed to connect to ActionInvoked dbus signal
Μαΐ 16 03:22:01 phobos.daemons.gr kded5[1521]: org.kde.knotifications: warning: failed to connect to NotificationClosed dbus signal
Μαΐ 16 03:22:01 phobos.daemons.gr plasmashell[12227]: libkcups: CUPS-Get-Printers last error: 1030 No destinations added.
Μαΐ 16 03:22:01 phobos.daemons.gr plasmashell[12227]: libkcups: Get-Jobs last error: 0 successful-ok
Μαΐ 16 03:22:01 phobos.daemons.gr plasmashell[12227]: libkcups: Get-Jobs last error: 0 successful-ok
Μαΐ 16 03:22:01 phobos.daemons.gr plasmashell[12227]: libkcups: Create-Printer-Subscriptions last error: 0 successful-ok
Μαΐ 16 03:22:01 phobos.daemons.gr plasmashell[12227]: QQuickItem::stackAfter: Cannot stack StatusNotifierItem_QMLTYPE_425(0x55cb7d4c3490, parent=0x55cb7d1a0140, geometry=0,0 0x0) after Stat>
Μαΐ 16 03:22:01 phobos.daemons.gr plasmashell[12227]: QQuickItem::stackAfter: Cannot stack StatusNotifierItem_QMLTYPE_425(0x55cb7d4cdd10, parent=0x55cb7d1a0140, geometry=0,0 0x0) after Stat>
Μαΐ 16 03:22:01 phobos.daemons.gr plasmashell[12227]: libkcups: 0
Μαΐ 16 03:22:01 phobos.daemons.gr plasmashell[12227]: libkcups: 0
Μαΐ 16 03:22:01 phobos.daemons.gr plasmashell[12227]: Both point size and pixel size set. Using pixel size.
Μαΐ 16 03:22:01 phobos.daemons.gr plasmashell[12227]: file:///usr/share/plasma/plasmoids/org.kde.plasma.battery/contents/ui/CompactRepresentation.qml:53:17: Unable to assign [undefined] to >
Μαΐ 16 03:22:01 phobos.daemons.gr plasmashell[12227]: trying to show an empty dialog
Μαΐ 16 03:22:01 phobos.daemons.gr plasmashell[12227]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:146:19: QML Loader: Binding loop detected for propert>
Μαΐ 16 03:22:01 phobos.daemons.gr plasmashell[12227]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:146:19: QML Loader: Binding loop detected for propert>
Μαΐ 16 03:22:01 phobos.daemons.gr kdeconnectd[1622]: org.kde.knotifications: warning: failed to connect to ActionInvoked dbus signal
Μαΐ 16 03:22:01 phobos.daemons.gr kdeconnectd[1622]: org.kde.knotifications: warning: failed to connect to NotificationClosed dbus signal
Μαΐ 16 03:22:01 phobos.daemons.gr kdeinit5[12299]: Qt: Session management error: networkIdsList argument is NULL
Blockquote

Afaik the standard workaround to avoid a crash is, before clicking the volume widget, stand on one leg [ideally the one opposite your mouse hand, for aesthetic balance], & then simultaneous with the clicking action rub your tummy circularly. The tricky bit is to remember your hemisphere; if northern, rub CCW, if southern, rub CW. Mixing these up usually results in a deleted partition.

Summary

An actual serious person will likely happen along soon to help you; your described sysmptom is entirely too weird for me, as i have never experienced that in countless SSD & VM Manjaro, Arch, KaOS, EndeavourOS, ArchLabs et al Plasma 5.18.5 systems. Good luck.

Oh, my only initial real question: what happens if you create a second user account; does the symptom repeat there?

Hmmm, second question: if you uninstall this widget [& ensure its config directory is also gone], then reinstall it, is the behaviour any better?

3 Likes

Is fine if you can deal with things yourself, but might not be a good idea if you want a working main system.
One error points to glibc but i can't reproduce the issue, and is same version on testing as on unstable. Did you try with a new TEST user? Only left click crashes? If you create a new panel it does the same? I can think to a number of questions to ask, but i won't as i'm not quite

Welcome to the forum! :wink:

2 Likes

ok i created new user account and now it works. thank you! :slight_smile:

Good, but IMO that represents progress, not a solution per se. My logic in making that basic testing suggestion is that it proves the root cause is specific only to your initial user profile, not the entire installation. Thus the next step could/should be to either find the specific root cause & eliminate it, or [often more practical] simply reset your main user account's Plasma configs. However the arguably first step to try is to delete the cache.

Here fyi:
https://wiki.archlinux.org/index.php/KDE#Plasma_desktop_behaves_strangely

1 Like

Happening also here into a new install.

Forum kindly sponsored by