Bug 427082

Summary:	slideshow remote: "pointer" crashes ability to remote control
Product:	[Applications] kdeconnect	Reporter:	Michał Pomorski <misieck>
Component:	common	Assignee:	Albert Vaca Cintora <albertvaka>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	nicolas.fella
Priority:	NOR
Version:	1.4
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:

Description Michał Pomorski 2020-09-28 16:52:19 UTC

SUMMARY

Slideshow remote's "pointer" function caucrashes somethingses disconnection of slideshow remote, remote input and media control.

STEPS TO REPRODUCE
1. Open slideshow remote on the phone.
2. Press "Pointer" multiple times.
3. 

OBSERVED RESULT
The whole PC screen flashes each time "pointer" is pressed. After 3-8 times the remote control is no longer functional. "Remote input" stops working, "Multimedia control" cant control sound levels anymore.
Other functions such as "ring" or "send file" continue to work.

EXPECTED RESULT
Whatever "pointer" was supposed to do (i dont know).

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: PopOs 20.04 with Gnome 3.36.3

KDE Plasma Version: 
KDE Frameworks Version: 5.68.0-ubuntu1
Qt Version: 5.12.8 (?)

ADDITIONAL INFORMATION
Killing kdeconnectd on PC seem to restore the remote control, but the effect is not immediate, so im not sure if that's the cause.

Comment 1 Nicolas Fella 2020-10-04 19:43:08 UTC

Can you verify that qml-module-qtquick-particles2 is installed?

Comment 2 Michał Pomorski 2020-10-05 13:09:17 UTC

Ideed, qml-module-qtquick-particles2 was not installed. It is in the repos and installing it resolves the problem.
So the bug looks like a package dependency problem. But also indicates to some error handling problems in the desktop app.

Btw, the pointer is a great feature when it works, wow!

Comment 3 Nicolas Fella 2020-10-08 22:12:52 UTC

Then it's a known issue. Ultimatley it's something that needs to be fixed in distro packaging. the good news is that my fix for Debian jsut got merged so it will find its way to Ubuntu eventually

*** This bug has been marked as a duplicate of bug 414913 ***