https://bugs.kde.org/show_bug.cgi?id=522520
Bug ID: 522520
Summary: krunner run shell command plugin use wrong PATH
Classification: Plasma
Product: krunner
Version First 6.7.1
Reported In:
Platform: Bazzite
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected], [email protected]
Target Milestone: ---
I _guess_ this is a bug since the behavior is radically different from previous
KDE version, and it was not advertised as a being changed. It is also not
intuitive to have a different behavior in PATH between krunner and konsole
DESCRIPTION
When using the "run shell command" plugin in krunner, binaries that are present
in /.local/bin or any other PATH location, are not filtered and can't be
executed.
I used "printenv PATH" in both krunner and a terminal to confirm that, and
krunner only looks for /usr/bin/, ignoring the PATH set in bashrc for example
This is definitely not the same behavior as before I updated to bazzite 44,
which jump from kde 6.6 to 6.7.1
STEPS TO REPRODUCE
1. put binaries into /.local/bin/
2. there are not to be found
alternatively :
1. execute ```printenv PATH > log.txt``` in krunner
2. and compare to the same thing within konsole
EXPECTED RESULT
krunner should behave the same as konsole,
SOFTWARE/OS VERSIONS
Operating System (available in the Info Center app, or by running `kinfo` in a
terminal window): Bazzite 44
KDE Plasma Version: 6.7.1
KDE Frameworks Version: 6.27.0
Qt Version: 6.11.1
ADDITIONAL INFORMATION
As a workaround, I found that you can still export PATH within krunner with
/home/bazzite/.config/plasma-workspace/env/pathexport.sh
but this is not very intuitive
--
You are receiving this mail because:
You are watching all bug changes.
