[Konsole-devel] Environment of non-forked konsole-sessions

[Jekyll Wu]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

于 2012年01月12日 22:28, Thomas Bach 写道:
> Hello
> 
> We're currently upgrading our linux workstations from centos 5 to
> centos 6.
> 
> In centos 6 I experience some strange behaviour of konsole compared
> to the one in centos 5
> 
> Centos 6 version informations $ konsole -v Qt: 4.6.2 KDE: 4.3.4
> (KDE 4.3.4) Konsole: 2.3.3
> 
> Centos 5 version informations $ konsole -v Qt: 3.3.6 KDE:
> 3.5.4-25.el5.centos.1 Red Hat Konsole: 1.6.4
> 
> Following a simple reproduction of my problem with centos 6 (KDE
> 4.3.4):
> 
> Case A: KDE-App-Launcher -> starts simple PyQt-App (see below) 
> start "konsole -e --noclose /bin/env" with specific environment 
> start "konsole -e --noclose /bin/env" with changed env variable
> 
> then the changed env-variable will not be transmitted to the
> second konsole-call On the other hand:
> 
> Case B: start konsole -> start simple PyQt-App (see below) start
> "konsole -e --noclose /bin/env" with specific environment start
> "konsole -e --noclose /bin/env" with changed env variable
> 
> then everything works as I expected
> 
> I think this might be due to the isatty-call of the following
> function in the main.cpp: bool shouldUseNewProcess() respectively 
> bool forceNewProcess() in older versions
> 
> in case A there is only one konsole-process in case B there are two
> different konsole-processes
> 
> Is there a way to tell konsole to always start a new process (and 
> environment) for every call. What we need is the
> environment-behaviour as in case B without the need of the initial
> konsole-call.
> 
> I don't know weather this is as intended or if this is a bug. Could
> you explain me, what the behaviour of case A is as described?
> 
> Many thanks in advance and kind regards, thomas
> 

Hi Thomas:

This is a feature or a known issue : Konsole tries to be a unique
process. You might be interested in reading these two bug reports:

https://bugs.kde.org/show_bug.cgi?id=262169
https://bugs.kde.org/show_bug.cgi?id=288200

The bad news is there is no workaround in your version or any existing
version. If you build konsole from latest git code(including the
commit mentioned in bug 288200), I think you can use the --nofork
option to force konsole to alway use new process.

Jekyll

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJPDz1kAAoJEOemZ9znWXlAH2QP/0D7XfWQcZQL0UikgSKvQJHd
zKfa/7k55Fna5AzWjPLBX3/eqK7ETR/IFVySQq7t1Tth+Hf02Qs3L82gk1HDBIpn
gr3rP7eUdRiLVLmId0oOxDD8UjGjhQ5y8Iv6MCHEb83Qn+ETpVqPNtCf6EQqdQkD
GCatLFI1/xzBD2GZ2RwI6O1+33b5Xt4Ie71BRgl9lFVOCHsdOY2goPo9STuHDtSS
ZTOX40O1movW1PQ3f1juNfYBSky4hFkPr8a/7wrCUXHs8/Fce+H2s/eYKm0DQ2S9
eHHtNq+34jQmqWrsw41tPSBeIcIryGJISraiht9CL3yvu8uqutsETFDPhGzN1TWE
CGueDST9YDRpOO3RgRapDtgFVcycgxTbRJOz7haH/3IX3qEMBcH/b4rD8EWaN+2W
r/Mzm/08fjP8U2s4NFtSvxqG/ACThRmaVLrTaz26KaPLw6tPYw7UhkosAyYtUGiU
nawERxXFbWOvLtJiPM+u2nmQZu/yDWmJDlc0ycm6klP9yZ5n5Evpg/NbT6Oq9AjQ
YavCuv20pO4CY1YJsZZuX6P3SPqRfiZSMY8a1RvoTzYCC8A09PyUWXMalY4yXy7l
31NLV4N2m5hC9qBIBgKxq4A8UdwX4Mrw5j5Ngkll0ANiFbCdPkuiCbnAQGFkBCwY
UK4twf9gJUaaixUddWz6
=VmRL
-----END PGP SIGNATURE-----