Bug 353454 - "KDEInit could not launch..." error when calling kwrite from a shell script
Summary: "KDEInit could not launch..." error when calling kwrite from a shell script
Status: RESOLVED UNMAINTAINED
Alias: None
Product: plasma4
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-10-02 15:06 UTC by Tristan Miller
Modified: 2018-06-09 05:02 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tristan Miller 2015-10-02 15:06:08 UTC
KWrite produces annoying console output (see Bug 173760) so I wrap it in a shell script as follows:

#!/bin/bash
/usr/bin/kwrite "$@" >&/dev/null &

This shell script works fine when I launch it from a terminal. However, if I use Plasma to run it with Alt+F2, the kwrite launches but I also get the following error dialog:

Sorry - Run Command Interface
KDEInit could not launch '/home/miller/bin/kwrite'

Possibly this is related to Bug 343673, which was supposedly fixed in KDE 5 and backported to KDE 4.  Note, however, that my problem is slightly different: I get the error only when I use Alt+F2 to run a shell script which invokes kwrite.  (And even then, the problem occurs only when I let KDE find the script on my PATH; if I instead type ~/bin/kwrite, the error doesn't occur.)

I am using KDE 4.14.3.

Reproducible: Always

Steps to Reproduce:
1. Create a shell script ~/bin/kwrite which launches kwrite.  Make sure ~/bin is on the PATH.
2. Press Alt+F2, type "kwrite", and press enter.


Actual Results:  
3. Error dialog appears which says, "KDEInit could not launch '/home/miller/bin/kwrite'"
4. KWrite is launched.

Expected Results:  
Step 3 above should not happen.
Comment 1 Tristan Miller 2016-08-13 18:47:25 UTC
Problem still exists in KDE 4.14.18.
Comment 2 Nate Graham 2018-06-08 18:20:30 UTC
Hello!

This bug report was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this bug has already been resolved in Plasma 5.

Accordingly, we hope you understand why we must close this bug report. If the issue described  here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting

If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging

Thanks for your understanding!

Nate Graham
Comment 3 Tristan Miller 2018-06-09 05:02:52 UTC
I tested this in Plasma 5 and the problem is not reproducible there.