Bug 307752

Summary:	krunner does not interpret environmental variables
Product:	[Plasma] krunner	Reporter:	ti.yarosh
Component:	general	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	wishlist	Keywords:	triaged
Priority:	NOR
Version First Reported In:	4.8.4
Target Milestone:	---
Platform:	Debian testing
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description ti.yarosh 2012-10-02 21:23:38 UTC

As for KDE SC version 4.8.4 krunner does not interpret environmental variables.
Alt+F2, `kwrite test` opens new text files with `test` name, but either `kwrite $HOSTNAME` or `kwrite "$HOSTNAME"` opens noname text file.

Reproducible: Always

Steps to Reproduce:
1. Open «Run command» dialog (e.g. alt+f2)
2. typing `kwrite $HOSTNAME`
Actual Results:  
Opens noname text file with kwrite.

Expected Results:  
kwrite should be opened with the file name, taken from the $HOSTNAME?

Comment 1 Jekyll Wu 2012-10-03 01:05:45 UTC

It works fine for me, like this :

    $ kquitapp krunner
    $ export $HOSTANME=Gentoo-Linux
    $ krunner (then typing "kwrite $HOSTNAME" will open Gentoo-Linux for me)

The real problem is probably that $HOSTNAME env is not set for your krunner although you assume it has been. To check, run the following command : 

    cat  /proc/`pidof krunner`/environ | tr '\000' '\012'   | grep HOSTNAME

Comment 2 Andrew Crouthamel 2018-09-23 02:42:05 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 3 Andrew Crouthamel 2018-10-27 02:26:11 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!