Bug 1294

Summary: Konsole terminal support does not work with KDE SC 4.x
Product: [Build System, Metadata & Runtime] Meta-yocto Reporter: Paul Eggleton <bluelightning>
Component: meta-yoctoAssignee: Paul Eggleton <bluelightning>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Low CC: josh, poky.bs.watcher, poky.watcher, sgw
Version: unspecified   
Target Milestone: 1.1   
Hardware: x86   
OS: Multiple   
Whiteboard: Fixes merged
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: ---

Description Paul Eggleton 2011-07-26 03:44:55 UTC
Right now our Konsole terminal support just does not work with current versions of Konsole, because since KDE 4.0 Konsole forks into the background and returns control to the calling process immediately instead of waiting. Adding the --nofork command line option which is supposed to make it wait does not work either, because if the controlling terminal is not interactive it assumes there is no other instance of Konsole running, tries to register a DBUS service and fails (and it's hard to imagine someone using KDE and running bitbake without having an instance of Konsole running already).
 
A while ago I had a look adding a command line option to Konsole itself to 
make this work but didn't get very far, although I don't think it should be 
too difficult. There is a workaround script [1] but when I tried it just now I 
found it again has problems if the controlling terminal is not interactive 
(never returns). Frankly the script is hideous and maybe it was broken in a 
version of KDE since the script was written, I don't know.

It might be prudent to remove the Konsole support until it has been fixed 
appropriately; at the very least it should be documented to only work with 
Konsole from KDE 3.x.

[1] http://lists.kde.org/?l=kde-core-devel&m=123188146810950&w=2
Comment 1 Richard Purdie 2011-08-10 11:16:52 UTC
We have already documented this is 3.x only in the conf file. Perhaps we could add a sanity test when this is invoked to test for kconsole 4.x and show an error message. If we do that perhaps we can close this issue?
Comment 2 Joshua Lock - Disabled 2011-09-15 14:29:43 UTC
This issue is compounded by the recent terminal changes.

By default a terminal is auto-detected based on an arbitrary priority such that if konsole is installed on the users system it will become the default terminal (despite having the same priority as gnome-terminal it seems to be picked first) making devshell, etc, unusable without tweaking.

I suggest we either add the sanity check and warn the user to set an appropriate variable in local.conf *or* modify lib/oe/terminal.py to prevent konsole being used.

Further, I'm fairly certain the arguments defined for konsole in terminal.py are not correct.
Comment 3 Paul Eggleton 2011-09-16 08:36:30 UTC
I tried using konsole with devshell and it appears there are a number of problems:

1) bash running within konsole doesn't inherit any of the environment or appropriate workdir. I'm  not sure what's happening here but in this state it's practically useless.

2) Even if you change the command line to use --title instead of -T it just ignores it and uses the default title. It appears this option only works if you run it from within konsole.

I use konsole every day, but for this purpose it's so broken I'm tempted to just remove support for it altogether :(
Comment 4 Paul Eggleton 2011-09-19 01:54:03 UTC
Added a sanity check in commit 3a6a38e3c60600ac9272d9e73d1bf05c0ae7e3ae

Added a fix for the OE_TERMINAL issue in 9b5175255b134d5d855234a44316a6a034a1f210

The underlying problems have not been fixed, however these are issues within Konsole itself, so I'm marking this bug as fixed.