Bug 1887179 - toolbox env tracking leaking through ssh connection
Summary: toolbox env tracking leaking through ssh connection
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-terminal
Version: 32
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2020-10-11 15:29 UTC by Alexander Boström
Modified: 2021-05-25 16:52 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-05-25 16:52:33 UTC
Type: Bug

Attachments (Terms of Use)

Description Alexander Boström 2020-10-11 15:29:35 UTC
Description of problem:
Terminal environment duplication feature confused by ssh connections.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Open Terminal
2. ssh to other host
3. toolbox enter (on remote host)
4. Open a new terminal tab or new window from the existing window

Actual results:
New terminal opens inside local toolbox.

Expected results:
New terminal opens in default environment / the env that ssh client was started from / with the remote ssh environment duplicated.

Additional info:
I wish the env duplication feature was or could be bound to a separate hotkey (because it often gets in the way), but this specific case is clearly wrong.

Comment 1 Alexander Boström 2020-10-11 15:32:02 UTC
Remote host when testing was Silverblue.

Comment 2 Fedora Program Management 2021-04-29 16:40:52 UTC
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '32'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 32 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Ben Cotton 2021-05-25 16:52:33 UTC
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.