Bug 26680

Summary:	Plasma desktop files created to run in terminal die: "Could not find the program 'konsole'"
Product:	Mageia	Reporter:	Barry Jackson <zen25000>
Component:	RPM Packages	Assignee:	KDE maintainers <kde>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	major
Priority:	Normal	CC:	geiger.david68210
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	plasma-desktop-5.18.5-2.mga8	CVE:
Status comment:

Description Barry Jackson 2020-05-24 18:36:23 CEST

Description of problem:

As summary, since recent updates to Cauldron.


Version-Release number of selected component (if applicable):

plasma-desktop-5.18.5-2.mga8

How reproducible:
Always

Steps to Reproduce:
1. Create a "link to application" on the desktop
2. Enter an exec command something like "ls -l /"
3. Under Advanced set it to run in a terminal and optionally not close the terminal.
4. Try to use it and a dialogue pops up saying that 'konsole' cannot be found.

Comment 1 Lewis Smith 2020-05-24 21:41:08 CEST

Thank you for the detailed "Steps to Reproduce".
All I can add is that it *does* work on Mageia 7!

Assigning to the KDE team.

Assignee: bugsquad => kde

Comment 2 David GEIGER 2020-05-25 14:57:38 CEST

This issue should be reported upstream and perhaps it is already reported by another distro.

CC: (none) => geiger.david68210

Comment 3 David GEIGER 2020-05-26 12:20:56 CEST

As reported here https://bugs.kde.org/show_bug.cgi?id=421374 and fixed upstream, please test next kio-5.70.1-2.mga8 update!

Comment 4 Barry Jackson 2020-05-27 22:27:42 CEST

It's now finding the konsole as in the simple example where I used ls, but now not ssh in this case:

Could not find the program 'ssh -l baz zmhost tail -f cronsync_last.log'

Using full path to ssh makes no difference:

Could not find the program '/usr/bin/ssh -l baz zmhost tail -f cronsync_last.log'

Ah!!

However, removing the quotes around the command fixes it. They were the fix a few years ago when the plain command stopped working, so I guess the original bug has now been fixed which has broken the workaround.

So - yes closing as fixed. :)

Status: NEW => RESOLVED
Resolution: (none) => WORKSFORME