Bug 241580

Summary: kioexec spawns no konsole when opening a file via http:// even if "run in terminal" is enabled
Product: [Unmaintained] kio Reporter: Dennis Schridde <heri+kde>
Component: generalAssignee: David Faure <faure>
Status: RESOLVED FIXED    
Severity: normal CC: adawit
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Dennis Schridde 2010-06-12 20:54:06 UTC 
Version:           unspecified (using Devel) 
OS:                Linux

I am using kde-4.4.4 and I've got a mime-type that is registered with a console application. When I look at the mime-type/command association in the konqueror settings (under advanced options) ~"execute in terminal" is checked. The tooltip claims that I could see the stdout/stderr of the application. However I cannot spot any window, nor is it visible in the opened yakuake, despite that (according to "ps") the console-application is still running...

The file was a .amz file, with clamz being configured to handle it, and konqueror being setup to use kget for downloads (if that makes a difference).

I clicked the link on Amazon and in the following save/open/cancel popup selected "open with clamz [...]".
Afterwards a kio process showed up in the process list, ~"kioexec clamz [...] http://amazon/[...]", and an instance of "clamz [...] /tmp/[...]" was started.

I should have seen a konsole process instead, from which clamz should have been spawned.

Reproducible: Didn't try
Comment 1 Dennis Schridde 2010-06-12 20:58:28 UTC 
(KDE 4.4.4, installed via Gentoo packages)
Comment 2 Dawit Alemayehu 2013-06-18 05:17:25 UTC 
Not exactly sure what the steps are to try and reproduce this problem. I did not fully understand your description above. Do you still have this issue in the latest stable version of KDE, v4.10?
Comment 3 Dennis Schridde 2013-06-18 07:36:08 UTC 
(In reply to comment #2)
> Not exactly sure what the steps are to try and reproduce this problem. I did
> not fully understand your description above. Do you still have this issue in
> the latest stable version of KDE, v4.10?

No, running clamz worked the last time I tried. Must have been fixed at some point in the past.