| Summary: | KIO::CommandLauncherJob doesn't emit error when command is empty | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] frameworks-kio | Reporter: | Nicolas Fella <nicolas.fella> |
| Component: | general | Assignee: | KIO Bugs <kio-bugs-null> |
| Status: | REPORTED --- | ||
| Severity: | normal | CC: | kdelibs-bugs-null, nate |
| Priority: | NOR | ||
| Version First Reported In: | 5.91.0 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
auto *job = new KIO::CommandLauncherJob("", {}, this); job->start() will finish without error()/errorMessage()/errorString() indicating any issue, although in 99% of cases that would be a bug in the calling code This appears in the logs: kf.kio.gui: Failed to register new cgroup: "app--43ef161fd300419da0628a3fc7446b39.scope" "org.freedesktop.DBus.Error.UnixProcessIdUnknown" "Process with ID 21340 does not exist." kf.kio.gui: "" exitCode= 0 exitStatus= QProcess::NormalExit