Bug 393091 - "zsh: kdevelop!: command not found" in Konsole tool view with CentOS AppImage
Summary: "zsh: kdevelop!: command not found" in Konsole tool view with CentOS AppImage
Status: RESOLVED WORKSFORME
Alias: None
Product: kdevelop
Classification: Applications
Component: general (show other bugs)
Version: git master
Platform: Appimage Linux
: NOR normal
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-04-13 07:52 UTC by Jeremy W. Murphy
Modified: 2022-12-31 05:23 UTC (History)
2 users (show)

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 Jeremy W. Murphy 2018-04-13 07:52:40 UTC
When I use the Konsole view in KDevelop, I get this error message:

[jmurphy@ad.4dx.com@dev100]~%  kdevelop! -s "{0fea6bbb-ed85-41c8-a479-d5cef6f9ec33}"
zsh: command not found: kdevelop!

I get the equivalent error with bash too.
Only in the CentOS AppImage, not with a native build.
Comment 1 Kevin Funk 2018-09-20 08:48:10 UTC
I can reproduce this. The 'kdevelop!' script is part of the AppImage, though.

The problem is that the shell started in the Konsole view in KDevelop does not have the AppImage's PATH in its very own PATH env var. No idea how to work-around this fact.

Maybe Sven has an idea?
Comment 2 Sven Brauch 2018-09-20 09:04:18 UTC
It would probably in general make sense if KDevelop would just prepend this path to the shell environment's path before starting it ... then we could also remove the kdevelop! executable from our bin/ path, it imo doesn't belong there (it belongs into libexec).
Comment 3 Francis Herne 2018-09-20 09:06:52 UTC
I think kdevelop! does belong in $PATH, it's equally useful to control KDevelop from other terminal windows.

I'm looking at prepending the path for this case.
Comment 4 Sven Brauch 2018-09-20 09:11:09 UTC
Ok, fair enough.
Comment 5 Kevin Funk 2018-09-24 13:43:34 UTC
Bug 393091 seems to have a work-around for this issue?
Comment 6 Kevin Funk 2018-09-24 13:44:06 UTC
Sorry, I've meant https://bugs.kde.org/show_bug.cgi?id=398907
Comment 7 Justin Zobel 2022-12-01 04:34:33 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 8 Bug Janitor Service 2022-12-16 05:13:29 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
mark the bug 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 9 Bug Janitor Service 2022-12-31 05:23:37 UTC
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!