Bug 19474

Summary:	plasma5 desktop launchers that use 'open in terminal' do nothing even if created and working in Mga5
Product:	Mageia	Reporter:	Barry Jackson <zen25000>
Component:	RPM Packages	Assignee:	KDE maintainers <kde>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	critical
Priority:	Normal	CC:	fri, geiger.david68210
Version:	Cauldron	Keywords:	NEEDINFO
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	plasma5...	CVE:
Status comment:
Bug Depends on:
Bug Blocks:	17523

Description Barry Jackson 2016-09-27 22:53:29 CEST

Description of problem:
As summary.
This breaks all my script shortcuts on the desktop that I have used for years in KDE.

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


How reproducible:
Always

Steps to Reproduce:
1. On Cauldron plasma5 desktop in folder view
2. Right click -> Create New -> Link to Application
3. Under application tab name it "Link to ls"
4. and enter "ls -l" in command field
5. Click advanced options button and in dialog check "Run in terminal" and
6. "Do not close when command exits"
7. OK both dialogs
8. Left click new icon on desktop.
9. This should open konsole with a listing of the user's home folder. It fails.
10. This works perfectly in Mageia 5 KDE

David Walser 2016-09-27 23:28:34 CEST

Blocks: (none) => 17523
Assignee: bugsquad => kde

Barry Jackson 2016-10-09 18:25:38 CEST

Severity: major => critical

Comment 1 David GEIGER 2016-10-09 19:24:06 CEST

Is there a bug reported upstream?

CC: (none) => geiger.david68210

Comment 2 Barry Jackson 2016-10-10 00:26:58 CEST

I found this:

https://bbs.archlinux.org/viewtopic.php?id=217487

...but there is no reference to the 'Known upstream bug' it mentions.

The workaround suggested does not work for me, assuming I understood it correctly.

Putting the command in quotes literally as "ls-l" in step 4 of comment 0 above did not work.

Keywords: (none) => NEEDINFO

Comment 3 Barry Jackson 2016-10-10 00:29:14 CEST

Ignore typo, I meant "ls -l"

Comment 4 Morgan Leijström 2016-10-10 19:19:20 CEST

Seem to be same as my 19332

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

Status: NEW => RESOLVED
CC: (none) => fri
Resolution: (none) => DUPLICATE