Bug 339123 - kioexec spawns endless instances of itself
Summary: kioexec spawns endless instances of itself
Status: CONFIRMED
Alias: None
Product: frameworks-kio
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Maarten De Meyer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-16 15:52 UTC by Elias Probst
Modified: 2021-03-09 05:53 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Elias Probst 2014-09-16 15:52:48 UTC 
Using KF5-based ksnapshot (fa3226be) built using Qt 5.4.0 alpha.
All KF5 components are up-to-date from git.

Send to → GIMP shows the dialog box "The URL\n is malformed" and after dismissing this message, it spawns infinite numbers of kioexec instances:
/usr/lib64/libexec/kf5/kioexec gimp-2.8 /home/elias/snapshot_J26426.png

The error message is (according to xprop) shown by kioexec.

I had 75 kioexec instances within 25 seconds.
By closing ksnapshot, all of them were terminated.
Comment 1 Elias Probst 2014-09-16 15:56:50 UTC 
Hmm, looks like this is more a kioexec issue than ksnapshot.
Running manually
/usr/lib64/libexec/kf5/kioexec gimp-2.8 /home/elias/snapshot_J26426.png
results in the same situation as described above.

The output of kioexec doesn't tell really much about what's going on, just repeating endlessly these lines:
command= "gimp-2.8"
kuiserver found
Icon theme "oxygen" not found.
Icon theme "oxygen" not found.
All files downloaded, will call slotRunApp shortly
Trying to open ksycoca from "/home/elias/.cache/ksycoca5"
EXEC  "/usr/lib64/libexec/kf5/kioexec gimp-2.8 /home/elias/snapshot_J26426.png"

Re-assigning to frameworks-kio…
Comment 2 Maarten De Meyer 2014-09-18 16:34:05 UTC 
https://git.reviewboard.kde.org/r/120267/
Comment 3 Elias Probst 2014-10-03 11:32:51 UTC 
The provided RR fixes the issue for me, but I need someone with more domain specific knowledge to give the patch a "ship it" or "improve it".
Comment 4 Justin Zobel 2021-03-09 05:53:56 UTC 
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.