SUMMARY KDE connect indicatior crashes when using, the phone as a pointer on the slide remote plugin STEPS TO REPRODUCE 1. for the kdeconnect android app select the sideshow remote 2. Now hold on the pointer button to use it as a pointer 3. use it to show a pointer on the desktop OBSERVED RESULT the kdeconnect-indicator crashes EXPECTED RESULT a round circle acting as a pointer shows up on the desktop SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon Unstable Edition (available in About System) KDE Plasma Version: 5.20.80 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION i ran the application under gdb it says that the dbus interace is not valid ( maybe a typo in calling dbus ) here is the full log `Starting program: /usr/bin/kdeconnect-indicator [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7ffff12d3700 (LWP 51887)] [New Thread 0x7fffebfff700 (LWP 51889)] kdeconnect.interfaces: dbus interface not valid kdeconnect.interfaces: dbus interface not valid uint DBusMenuExporterDBus::GetLayout(int, int, const QStringList&, DBusMenuLayoutItem&): Condition failed: menu uint DBusMenuExporterDBus::GetLayout(int, int, const QStringList&, DBusMenuLayoutItem&): Condition failed: menu kdeconnect.interfaces: dbus interface not valid kdeconnect.interfaces: dbus interface not valid uint DBusMenuExporterDBus::GetLayout(int, int, const QStringList&, DBusMenuLayoutItem&): Condition failed: menu uint DBusMenuExporterDBus::GetLayout(int, int, const QStringList&, DBusMenuLayoutItem&): Condition failed: menu` kdeconnect indicator does not have a version no so here are the version no of the others kdeconnect-cli - 1.4.0 kdeconnect-app - 1.0 kdeconnect-settings 1.4.0 kdeconnect-handler - 1.4.0
Try installing the qml-module-qtquick-particles2 package. If that fixes it then it's a known distro issue and being worked on
Yeah that fixes it thanks
Thanks for confirming, it should be fixed in KDE Neon by now. *** This bug has been marked as a duplicate of bug 418076 ***