Network & Audio Volume tray icons give errors

Support KDE Plasma
1

Network & Audio Volume tray icons give these errors:

qrc:/qt/qml/plasma/applet/org/kde/plasma/networkmanagement/main.qml:60:25: Type PopupDialog unavailable

qrc:/qt/qml/plasma/applet/org/kde/plasma/networkmanagement/PopupDialog.qml:110:22: Type ConnectionListPage unavailable

qrc:/qt/qml/plasma/applet/org/kde/plasma/networkmanagement/ConnectionListPage.qml:26:5: Type Kirigami.InlineMessage unavailable

file:///usr/lib/qt6/qml/org/kde/kirigami/controls/InlineMessage.qml:14:1: Type KT.InlineMessage unavailable

qrc:/qt/qml/org/kde/kirigami/templates/InlineMessage.qml:187:51: Cannot assign object of type "Primitives.IconPropertiesGroup" to property of type "IconPropertiesGroup_QMLTYPE_512\*" as the former is neither the same as the latter nor a sub-class of it.

qrc:/qt/qml/plasma/applet/org/kde/plasma/volume/main.qml:528:13: Type MicrophoneTestView unavailable

qrc:/qt/qml/plasma/applet/org/kde/plasma/volume/MicrophoneTestView.qml:60:9: Type Kirigami.InlineMessage unavailable

file:///usr/lib/qt6/qml/org/kde/kirigami/controls/InlineMessage.qml:14:1: Type KT.InlineMessage unavailable

qrc:/qt/qml/org/kde/kirigami/templates/InlineMessage.qml:187:51: Cannot assign object of type "Primitives.IconPropertiesGroup" to property of type "IconPropertiesGroup_QMLTYPE_512\*" as the former is neither the same as the latter nor a sub-class of it.

…And no icons at all appear on desktop.

2

Your post has been moved to a dedicated topic.

Please provide your system information according to forum guidelines. Any additional information provided may also prove useful.

Regards.

[Mini-HowTo] Provide System Information

Basic details provided by *-fetch type apps might give enough information for someone wishing to buy a computer, however, for Support purposes it’s best to ask your system directly.

Output of the inxi command will generate more useful and detailed information for those who may wish to help:

Suggested inxi command (use either):
inxi -zv8 (short-form)
inxi --filter --verbosity=8 (long-form)

Command output should be presented as pre-formatted text in accordance with forum guidelines. :eyes:

Running inxi within a chroot environment

  • Add --color=0 to the long-form command, or…
  • Change the short-form command to inxi -zv8c0

Your privacy is respected

[Mini-HowTo] Present code or command output

Note: Grave accent (or, backtick) characters are used. :eyes:

For inline code or to show a single command:

  • please follow this simple example: code here.

For multi-line command output:

  • place text beween two rows of three (```) backtick characters to form a scrollable text box, or …
  • use the </> button in the Compose window to achieve the same result.

The empty row between these rows of backtick characters is where to paste any multi-line command output (such as inxi).

An example of a pre-formatted text enclosure:

What is a Quark?

A. In Physics, an elementary particle and fundamental constituent of matter. 
B. A character from the Star Trek: "Deep Space Nine" television series.
C. A soft, creamy, usually unsalted cheese traditional to central Europe.
4

This error is a known QML type mismatch bug affecting KDE Plasma 6.7.4 and Frameworks 6.29.0 when used with Qt 6.11.2. It occurs because the InlineMessage component in Kirigami fails to correctly assign the IconPropertiesGroup type, causing components like the volume applet, network widget, and various System Settings KCMs to crash or fail to load.

Key Details and Workarounds:

  • Affected Components: The error frequently triggers in plasmashell applets (Volume, Network, Folder View) and systemsettings modules (Mouse, Keyboard, Colors & Themes).

  • Root Cause: The issue stems from a regression in how Qt 6.11.2 handles QML type registration for Kirigami templates, specifically regarding the Primitives.IconPropertiesGroup versus the internal IconPropertiesGroup_QMLTYPE_* variants.

  • Troubleshooting Steps:

    • Clear Caches: Users have reported success by moving or deleting the QML cache folders: ~/.cache/plasmashell/qmlcache/ and ~/.cache/systemsettings/qmlconfig/.

    • Environment Variable: Setting QML_DISABLE_DISK_CACHE=1 via ~/.config/environment.d/envvars.conf can bypass the issue for some users.

    • Configuration Fix: In some cases, removing the activityId line from ~/.config/plasma-org.kde.plasma.desktop-appletsrc resolves panel-specific crashes.

    • Downgrades: The issue persists even when downgrading Kirigami to version 6.28.0 on some systems, suggesting the root cause lies deeper within the Qt 6.11.2 or Plasma 6.7.4 integration.

This bug is tracked in KDE bug reports such as Bug 524608 and Bug 525110, with ongoing investigation into whether it requires a fix in Kirigami’s property type relaxation or a Qt-side adjustment.

[info from LLM]

The expected fix is in Qt 6.11.3, which Qt has targeted for September 2026 — i.e., this month. It will also be the last release in the 6.11 series, and Qt 6.11’s open-source support window closes on September 22, 2026 (9 days from now).

[info from LLM]

5

:robot:

You’re supposed to be honest about it when posting something compiled by an LLM. :grin:

6

source: https://bugs.kde.org/show_bug.cgi?id=524608

Mod edit:- General tidy of presentation. No charge.

9

This seems to indicate a CachyOS system.

11

@RiCK-Man-jaro

Could you please provide the output of:

inxi -zv8

… from the system you are currently running? … Also please remember to use proper formatting. :wink:

14

Of the person reporting the bug to KDE, not my system.

My specs were already given.

Also this was not a post asking for help. I did not even make this its own post, one of the mods did. It started out as a reply to another post, from the stable update page, which had requested to post about errors from the update, and I have no idea why one of the mods took it here as its own post. I can only guess it was a misunderstanding.

15

In future, please take steps to make it clear that information is quoted from elsewhere, and always provide a direct link so that others can verify any quoted text. Use either bbcode markup or other techniques supported by a Discourse forum to achieve this; for example:

[quote]
Quoted content here.
[/quote]

which renders as:

Specs were requested as inxi output; the de facto standard for providing System Information on the Manjaro forum – as a Manjaro forum member for some years, you should already have been aware of this. The request for this inxi output and details on how to provide it have been made (twice) and subsequently ignored or dismissed (twice).

Well, I didn’t move this one, however it’s a common practice when posts in the Announcement threads might not be related to an issue with the respective Update, and might be better addressed in a dedicated topic.

This was likely the case with yours, being that the issue was already known and actioned; evidenced by notes in the KDE Bug tracker #508377 (the report you indicated was marked a duplicate of this one);

This comment led me quickly to the apparent solution:

See: Qt Code Review #768697

Thus the importance of making sure intentions are understood. Forums can be a difficult medium; emoji don’t quite help in most cases; accuracy in communication is the best resolve to be understood by others as we wish to be.

Sometimes that’s not easy.

In which case, I’ll simply close the thread, as Support topics are strictly for those requesting help.