Bug 450573 - KIO::CommandLauncherJob doesn't emit error when command is empty
Summary: KIO::CommandLauncherJob doesn't emit error when command is empty
Status: REPORTED
Alias: None
Product: frameworks-kio
Classification: Frameworks and Libraries
Component: general (other bugs)
Version First Reported In: 5.91.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KIO Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-02-19 14:44 UTC by Nicolas Fella
Modified: 2022-02-21 23:01 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Nicolas Fella 2022-02-19 14:44:55 UTC 
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