Bug 373775

Summary:	Run command fails whenever the command includes any special character
Product:	[Applications] kdeconnect	Reporter:	kde
Component:	common	Assignee:	Albert Vaca Cintora <albertvaka>
Status:	RESOLVED FIXED
Severity:	normal
Priority:	NOR
Version First Reported In:	0.8
Target Milestone:	---
Platform:	Kubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description kde 2016-12-17 16:55:08 UTC

Hey there,

I have a few commands that I want to be able to trigger through Kdeconnects "Run command" plugin. I've noticed that any that include special characters (eg '";&) just flat out don't run.

To give an example:
kill -s TERM `pgrep thunderbird`

never does anything through run command, but works perfectly on the local commandline of the host machine.

I've also found that where I want to run two separate commands, each of which works by themselves, if I separate them with & or ; then the first runs but the second doesn't.

I'm running Ubuntu Yakkety which seems to have Kdeconnect 0.8 along with the FDroid version of the Android app (1.4.4).

I'm not sure, but this bug seems to be related to special characters not being escaped, possibly also causing bug #52452 and bug #211735.

Comment 1 kde 2016-12-17 17:02:27 UTC

Gah. I just noticed that those two bugs I mentioned, which were suggested by this bug tracker (Bugzilla?), are actually in different products and thus are irrelevant. The pattern of seeing commands with special characters fail though is consistent and relevant.

Comment 2 Albert Vaca Cintora 2016-12-17 17:24:35 UTC

The Run Command plugin was never included in KDE Connect 0.8. The first version with this plugin is 1.0.

During development, we found that these kind of commands didn't work, but for the final 1.0 release that was fixed. 

It might be that Ubuntu packagers are trying to release a development version instead of using the oficial releases... they do that sometimes to have the "cool stuff" before other distros, and then this kind of problems happen. Could you ask Ubuntu to just update to 1.0.2? That way it will fix the problem for you and every other Ubuntu user.

Comment 3 kde 2016-12-18 20:27:27 UTC

*sigh* Understood and will do.