| Summary: | Unhelpful error message shown when attempting to run malformed shell script with space before shebang | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] frameworks-kio | Reporter: | cotasamnemano53253 |
| Component: | general | Assignee: | KIO Bugs <kio-bugs-null> |
| Status: | CONFIRMED --- | ||
| Severity: | normal | CC: | a.samirh78, kdelibs-bugs, nate, rakuco |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Manjaro | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | This is the problematic bash file | ||
|
Description
cotasamnemano53253
2021-11-30 13:20:08 UTC
"buildsystem" isn't the right product here, moving to "frameworks-kio". The problem's in the space character before the shebang in the first line. While kio detects that this is an executable shell script, I think this goes all the way down to QProcess via KProcessRunner and possibly to Linux's detection of scripts (which verifies that the first two characters are "#!"). I agree the error message is very cryptic though. That's a pretty bad error message, yeah. We can do better. I couldn't reproduce this issue with e.g.: #! /usr/bin/bash /usr/bin/kfind & works OK, and kfind is opened. Do you still see this issue? Is there a space *before* the shebang in your test script? Viewing plain text is misleading in web browsers, looking at the attachment again it's " #! /usr/bin/bash". Retesting, now I see the issue. IIRC this is the error message we get from the system/kernel, not sure how it can be improved... |