Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Opening a terminal in the Konqueror browser or the Dolphin browser while using Filemanager mode led to a situation when any environment variable manually set before launching Konqueror was not inherited by the newly opened terminal. A patch has been applied to fix this bug, and environment variables are now inherited as expected.
DescriptionRon van der Wees
2014-04-17 12:50:33 UTC
Created attachment 887169[details]
Proposed patch to change this kpart behavior when opening a terminal
Description of problem:
Opening a terminal in Konqueror while being in Filemanager mode (Tools -> Open
Terminal, or press F4) will connect, via dbus, to org.kde.klauncher requesting
a new terminal to be spawned. Since this terminal is opened by klauncher, any
environment variable manually set before launching Konqueror will not be
inherited by the newly open terminal.
From an strace:
~~~
3568 socket(PF_FILE, SOCK_STREAM, 0) = 8
3568 connect(8, {sa_family=AF_FILE, path=@"/tmp/dbus-OEtdZiyDQB"}, 23) = 0
...
3568 writev(8, [{"l\1\0\1\26\0\0\0R\0\0\0\177\0\0\0\1\1o\0\25\0\0\0/org/fre"..., 144}, {"\21\0\0\0org.kde.klauncher\0", 22}], 2) = 166
3568 writev(8, [{"l\1\0\1\230\0\0\0S\0\0\0\215\0\0\0\1\1o\0\n\0\0\0/KLaunch"..., 160}, {"\7\0\0\0konsole\0$\0\0\0\t\0\0\0--workdir\0\0\0"..., 152}], 2) = 312
~~~
This behavior is different from previous KDE versions (i.e. KDE3 in RHEL5)
where it did inherit the environment variables. Moreover, openening a terminal
by:
Right clicking a folder -> Actions -> Open Terminal here
opens a terminal in a different way which *does* inherit environment
variables. This together with the behavior from KDE3 is inconsistent and
confuses customers / end-users.
Version-Release number of selected component (if applicable):
kdebase-4.3.4-6.el6:6.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Run: THISENV=1 konqueror
2. Navigate to: file:///home/<username>
3. Press F4
4. Check the THISENV environment variable
Actual results:
$ echo ${THISENV:-doesnotexists}
doesnotexist
Expected results:
$ echo ${THISENV:-doesnotexists}
1
Additional info:
This same behavior is shown in Dolphin.
In Konqueror the FileManager view is handle by kpart
(kdebase-4.3.4/apps/dolphin/src/dolphinpart.cpp)
Attached is a patch (kdebase-4.3.4-terminal-env.patch) which change this behavior for kpart.
Created attachment 887169 [details] Proposed patch to change this kpart behavior when opening a terminal Description of problem: Opening a terminal in Konqueror while being in Filemanager mode (Tools -> Open Terminal, or press F4) will connect, via dbus, to org.kde.klauncher requesting a new terminal to be spawned. Since this terminal is opened by klauncher, any environment variable manually set before launching Konqueror will not be inherited by the newly open terminal. From an strace: ~~~ 3568 socket(PF_FILE, SOCK_STREAM, 0) = 8 3568 connect(8, {sa_family=AF_FILE, path=@"/tmp/dbus-OEtdZiyDQB"}, 23) = 0 ... 3568 writev(8, [{"l\1\0\1\26\0\0\0R\0\0\0\177\0\0\0\1\1o\0\25\0\0\0/org/fre"..., 144}, {"\21\0\0\0org.kde.klauncher\0", 22}], 2) = 166 3568 writev(8, [{"l\1\0\1\230\0\0\0S\0\0\0\215\0\0\0\1\1o\0\n\0\0\0/KLaunch"..., 160}, {"\7\0\0\0konsole\0$\0\0\0\t\0\0\0--workdir\0\0\0"..., 152}], 2) = 312 ~~~ This behavior is different from previous KDE versions (i.e. KDE3 in RHEL5) where it did inherit the environment variables. Moreover, openening a terminal by: Right clicking a folder -> Actions -> Open Terminal here opens a terminal in a different way which *does* inherit environment variables. This together with the behavior from KDE3 is inconsistent and confuses customers / end-users. Version-Release number of selected component (if applicable): kdebase-4.3.4-6.el6:6.x86_64 How reproducible: Always Steps to Reproduce: 1. Run: THISENV=1 konqueror 2. Navigate to: file:///home/<username> 3. Press F4 4. Check the THISENV environment variable Actual results: $ echo ${THISENV:-doesnotexists} doesnotexist Expected results: $ echo ${THISENV:-doesnotexists} 1 Additional info: This same behavior is shown in Dolphin. In Konqueror the FileManager view is handle by kpart (kdebase-4.3.4/apps/dolphin/src/dolphinpart.cpp) Attached is a patch (kdebase-4.3.4-terminal-env.patch) which change this behavior for kpart.