| 2021-04-07 04:38:11 |
Matthew Ruffell |
bug |
|
|
added bug |
| 2021-04-07 04:38:20 |
Matthew Ruffell |
nominated for series |
|
Ubuntu Hirsute |
|
| 2021-04-07 04:38:20 |
Matthew Ruffell |
bug task added |
|
gnome-terminal (Ubuntu Hirsute) |
|
| 2021-04-07 04:39:34 |
Matthew Ruffell |
tags |
|
hirsute |
|
| 2021-04-07 04:56:44 |
Matthew Ruffell |
bug watch added |
|
https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/253 |
|
| 2021-04-07 05:03:08 |
Matthew Ruffell |
bug watch added |
|
https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/303 |
|
| 2021-04-09 01:23:41 |
Dominique Poulain |
bug |
|
|
added subscriber Dominique Poulain |
| 2021-04-13 00:52:47 |
Matthew Ruffell |
description |
[Impact]
If you launch gnome-terminal by right clicking a directory in Nautilus, selecting "Open in Terminal", you get a fully functional terminal window.
If you then press the new tab button, or ctrl-shift-t to open a new terminal tab, you will find that most environment variables have become unset, and you see the text:
To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.
Comparing printenv between:
Normal terminal: https://paste.ubuntu.com/p/2hcCY9hbHQ/
Broken new terminal tab: https://paste.ubuntu.com/p/zYsjRHVJH7/
Most commands won't run in the new terminal tab, due to $HOME and $USER not being set.
Note, if you launch gnome-terminal from gnome-shell or the dock, and create a new tab, everything works perfectly. Is something wrong with the Nautilus option for "Open in Terminal"? |
[Impact]
If you launch gnome-terminal by right clicking a directory in Nautilus, selecting "Open in Terminal", you get a fully functional terminal window.
If you then press the new tab button, or ctrl-shift-t to open a new terminal tab, you will find that most environment variables have become unset, and you see the text:
To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.
Comparing printenv between:
Normal terminal: https://paste.ubuntu.com/p/2hcCY9hbHQ/
Broken new terminal tab: https://paste.ubuntu.com/p/zYsjRHVJH7/
Most commands won't run in the new terminal tab, due to $HOME and $USER not being set.
Note, if you launch gnome-terminal from gnome-shell or the dock, and create a new tab, everything works perfectly. Is something wrong with the Nautilus option for "Open in Terminal"?
[Testcase]
1. Launch Nautilus to home directory
2. Right click > "Open in Terminal"
3. Run "printenv" to see full list of env variables
4. Click new tab button, or ctrl-shift-t
5. Run "printenv" see the lack of env variables
I have a test package available in the below ppa:
https://launchpad.net/~mruffell/+archive/ubuntu/lp1922839-test
The build in the ppa has 16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac reverted.
If you install this package, environment variables will be set correctly.
[Where problems could occur]
I think there is some risk with re-instating a commit which has been reverted, and users could run into similar issues as found in the upstream bug.
We do have some supporting evidence that the commit isn't too harmful, since it is applied to Groovy currently, things work as intended there, and users haven't complained about the issues in the upstream bug applying to Groovy.
If a regression were to occur, then launching a new gnome-terminal or opening a new tab could land the user with a terminal with little to no environment variables set. A workaround will be to launch gnome-terminal from gnome-shell overview.
[Other info]
Groovy has the following commit applied:
commit fd5ac772154426e2da5afd633b336414bca33be9
Author: Christian Persch <chpe@src.gnome.org>
Date: Mon Mar 23 09:57:56 2020 +0100
Subject: screen: Use clean env when creating new tab
Link: https://gitlab.gnome.org/GNOME/gnome-terminal/-/commit/fd5ac772154426e2da5afd633b336414bca33be9
This was then reverted in 3.38.1 due to the upstream bug:
https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/253
The reverted commit is:
commit 16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac
Author: Christian Persch <chpe@src.gnome.org>
Date: Thu Sep 17 17:10:47 2020 +0200
Subject: Revert "screen: Use clean env when creating new tab"
Link: https://gitlab.gnome.org/GNOME/gnome-terminal/-/commit/16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac
This revert seems to have broken Hirsute. If we revert the revert, that is,
apply the commit again, things work as intended.
To fix this, we need to revert 16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac. |
|
| 2021-04-13 03:10:22 |
Matthew Ruffell |
description |
[Impact]
If you launch gnome-terminal by right clicking a directory in Nautilus, selecting "Open in Terminal", you get a fully functional terminal window.
If you then press the new tab button, or ctrl-shift-t to open a new terminal tab, you will find that most environment variables have become unset, and you see the text:
To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.
Comparing printenv between:
Normal terminal: https://paste.ubuntu.com/p/2hcCY9hbHQ/
Broken new terminal tab: https://paste.ubuntu.com/p/zYsjRHVJH7/
Most commands won't run in the new terminal tab, due to $HOME and $USER not being set.
Note, if you launch gnome-terminal from gnome-shell or the dock, and create a new tab, everything works perfectly. Is something wrong with the Nautilus option for "Open in Terminal"?
[Testcase]
1. Launch Nautilus to home directory
2. Right click > "Open in Terminal"
3. Run "printenv" to see full list of env variables
4. Click new tab button, or ctrl-shift-t
5. Run "printenv" see the lack of env variables
I have a test package available in the below ppa:
https://launchpad.net/~mruffell/+archive/ubuntu/lp1922839-test
The build in the ppa has 16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac reverted.
If you install this package, environment variables will be set correctly.
[Where problems could occur]
I think there is some risk with re-instating a commit which has been reverted, and users could run into similar issues as found in the upstream bug.
We do have some supporting evidence that the commit isn't too harmful, since it is applied to Groovy currently, things work as intended there, and users haven't complained about the issues in the upstream bug applying to Groovy.
If a regression were to occur, then launching a new gnome-terminal or opening a new tab could land the user with a terminal with little to no environment variables set. A workaround will be to launch gnome-terminal from gnome-shell overview.
[Other info]
Groovy has the following commit applied:
commit fd5ac772154426e2da5afd633b336414bca33be9
Author: Christian Persch <chpe@src.gnome.org>
Date: Mon Mar 23 09:57:56 2020 +0100
Subject: screen: Use clean env when creating new tab
Link: https://gitlab.gnome.org/GNOME/gnome-terminal/-/commit/fd5ac772154426e2da5afd633b336414bca33be9
This was then reverted in 3.38.1 due to the upstream bug:
https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/253
The reverted commit is:
commit 16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac
Author: Christian Persch <chpe@src.gnome.org>
Date: Thu Sep 17 17:10:47 2020 +0200
Subject: Revert "screen: Use clean env when creating new tab"
Link: https://gitlab.gnome.org/GNOME/gnome-terminal/-/commit/16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac
This revert seems to have broken Hirsute. If we revert the revert, that is,
apply the commit again, things work as intended.
To fix this, we need to revert 16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac. |
[Impact]
If you launch gnome-terminal by right clicking a directory in Nautilus, selecting "Open in Terminal", you get a fully functional terminal window.
If you then press the new tab button, or ctrl-shift-t to open a new terminal tab, you will find that most environment variables have become unset, and you see the text:
To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.
Comparing printenv between:
Normal terminal: https://paste.ubuntu.com/p/2hcCY9hbHQ/
Broken new terminal tab: https://paste.ubuntu.com/p/zYsjRHVJH7/
Most commands won't run in the new terminal tab, due to $HOME and $USER not being set.
Note, if you launch gnome-terminal from gnome-shell or the dock, and create a new tab, everything works perfectly. Is something wrong with the Nautilus option for "Open in Terminal"?
[Testcase]
1. Launch Nautilus to home directory
2. Right click > "Open in Terminal"
3. Run "printenv" to see full list of env variables
4. Click new tab button, or ctrl-shift-t
5. Run "printenv" see the lack of env variables
I have a test package available in the below ppa:
https://launchpad.net/~mruffell/+archive/ubuntu/lp1922839-test
The build in the ppa has 16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac reverted.
If you install this package, environment variables will be set correctly.
[Where problems could occur]
I think there is some risk with re-instating a commit which has been reverted, and users could run into similar issues as found in the upstream bug.
We do have some supporting evidence that the commit isn't too harmful, since it is applied to Groovy currently, things work as intended there, and users haven't complained about the issues in the upstream bug applying to Groovy.
If a regression were to occur, then launching a new gnome-terminal or opening a new tab could land the user with a terminal with little to no environment variables set. A workaround will be to launch gnome-terminal from gnome-shell overview.
[Other info]
Focal and Groovy have the following commit applied:
commit fd5ac772154426e2da5afd633b336414bca33be9
Author: Christian Persch <chpe@src.gnome.org>
Date: Mon Mar 23 09:57:56 2020 +0100
Subject: screen: Use clean env when creating new tab
Link: https://gitlab.gnome.org/GNOME/gnome-terminal/-/commit/fd5ac772154426e2da5afd633b336414bca33be9
This was then reverted in 3.38.1 due to the upstream bug:
https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/253
The reverted commit is:
commit 16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac
Author: Christian Persch <chpe@src.gnome.org>
Date: Thu Sep 17 17:10:47 2020 +0200
Subject: Revert "screen: Use clean env when creating new tab"
Link: https://gitlab.gnome.org/GNOME/gnome-terminal/-/commit/16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac
This revert seems to have broken Hirsute. If we revert the revert, that is, apply the commit again, things work as intended.
To fix this, we need to revert 16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac. |
|
| 2021-04-13 03:11:40 |
Matthew Ruffell |
attachment added |
|
gnome-terminal debdiff for hirsute https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1922839/+attachment/5487098/+files/lp1922839_hirsute.debdiff |
|
| 2021-04-13 03:14:53 |
Matthew Ruffell |
description |
[Impact]
If you launch gnome-terminal by right clicking a directory in Nautilus, selecting "Open in Terminal", you get a fully functional terminal window.
If you then press the new tab button, or ctrl-shift-t to open a new terminal tab, you will find that most environment variables have become unset, and you see the text:
To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.
Comparing printenv between:
Normal terminal: https://paste.ubuntu.com/p/2hcCY9hbHQ/
Broken new terminal tab: https://paste.ubuntu.com/p/zYsjRHVJH7/
Most commands won't run in the new terminal tab, due to $HOME and $USER not being set.
Note, if you launch gnome-terminal from gnome-shell or the dock, and create a new tab, everything works perfectly. Is something wrong with the Nautilus option for "Open in Terminal"?
[Testcase]
1. Launch Nautilus to home directory
2. Right click > "Open in Terminal"
3. Run "printenv" to see full list of env variables
4. Click new tab button, or ctrl-shift-t
5. Run "printenv" see the lack of env variables
I have a test package available in the below ppa:
https://launchpad.net/~mruffell/+archive/ubuntu/lp1922839-test
The build in the ppa has 16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac reverted.
If you install this package, environment variables will be set correctly.
[Where problems could occur]
I think there is some risk with re-instating a commit which has been reverted, and users could run into similar issues as found in the upstream bug.
We do have some supporting evidence that the commit isn't too harmful, since it is applied to Groovy currently, things work as intended there, and users haven't complained about the issues in the upstream bug applying to Groovy.
If a regression were to occur, then launching a new gnome-terminal or opening a new tab could land the user with a terminal with little to no environment variables set. A workaround will be to launch gnome-terminal from gnome-shell overview.
[Other info]
Focal and Groovy have the following commit applied:
commit fd5ac772154426e2da5afd633b336414bca33be9
Author: Christian Persch <chpe@src.gnome.org>
Date: Mon Mar 23 09:57:56 2020 +0100
Subject: screen: Use clean env when creating new tab
Link: https://gitlab.gnome.org/GNOME/gnome-terminal/-/commit/fd5ac772154426e2da5afd633b336414bca33be9
This was then reverted in 3.38.1 due to the upstream bug:
https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/253
The reverted commit is:
commit 16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac
Author: Christian Persch <chpe@src.gnome.org>
Date: Thu Sep 17 17:10:47 2020 +0200
Subject: Revert "screen: Use clean env when creating new tab"
Link: https://gitlab.gnome.org/GNOME/gnome-terminal/-/commit/16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac
This revert seems to have broken Hirsute. If we revert the revert, that is, apply the commit again, things work as intended.
To fix this, we need to revert 16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac. |
[Impact]
If you launch gnome-terminal by right clicking a directory in Nautilus, selecting "Open in Terminal", you get a fully functional terminal window.
If you then press the new tab button, or ctrl-shift-t to open a new terminal tab, you will find that most environment variables have become unset, and you see the text:
To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.
Comparing printenv between:
Normal terminal: https://paste.ubuntu.com/p/2hcCY9hbHQ/
Broken new terminal tab: https://paste.ubuntu.com/p/zYsjRHVJH7/
Most commands won't run in the new terminal tab, due to $HOME and $USER not being set.
Note, if you launch gnome-terminal from gnome-shell or the dock, and create a new tab, everything works perfectly. Is something wrong with the Nautilus option for "Open in Terminal"?
[Testcase]
1. Launch Nautilus to home directory
2. Right click > "Open in Terminal"
3. Run "printenv" to see full list of env variables
4. Click new tab button, or ctrl-shift-t
5. Run "printenv" see the lack of env variables
I have a test package available in the below ppa:
https://launchpad.net/~mruffell/+archive/ubuntu/lp1922839-test
The build in the ppa has 16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac reverted.
If you install this package, environment variables will be set correctly.
[Where problems could occur]
I think there is some risk with re-instating a commit which has been reverted, and users could run into similar issues as found in the upstream bug.
We do have some supporting evidence that the commit isn't too harmful, since it is applied to Groovy currently, things work as intended there, and users haven't complained about the issues in the upstream bug applying to Groovy.
If a regression were to occur, then launching a new gnome-terminal or opening a new tab could land the user with a terminal with little to no environment variables set. A workaround will be to launch gnome-terminal from gnome-shell overview.
[Other info]
Focal and Groovy have the following commit applied:
commit fd5ac772154426e2da5afd633b336414bca33be9
Author: Christian Persch <chpe@src.gnome.org>
Date: Mon Mar 23 09:57:56 2020 +0100
Subject: screen: Use clean env when creating new tab
Link: https://gitlab.gnome.org/GNOME/gnome-terminal/-/commit/fd5ac772154426e2da5afd633b336414bca33be9
This was then reverted in 3.38.1 due to the upstream bug:
https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/253
The reverted commit is:
commit 16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac
Author: Christian Persch <chpe@src.gnome.org>
Date: Thu Sep 17 17:10:47 2020 +0200
Subject: Revert "screen: Use clean env when creating new tab"
Link: https://gitlab.gnome.org/GNOME/gnome-terminal/-/commit/16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac
This revert seems to have broken Hirsute. If we revert the revert, that is, apply the commit again, things work as intended.
To fix this, we need to re-apply fd5ac772154426e2da5afd633b336414bca33be9. |
|
| 2021-04-13 04:24:39 |
Ubuntu Foundations Team Bug Bot |
tags |
hirsute |
hirsute patch |
|
| 2021-04-13 04:24:45 |
Ubuntu Foundations Team Bug Bot |
bug |
|
|
added subscriber Ubuntu Sponsors Team |
| 2021-04-13 10:58:10 |
Marco Trevisan (Treviño) |
tags |
hirsute patch |
hirsute patch rls-ff-incoming |
|
| 2021-04-13 11:14:34 |
Marco Trevisan (Treviño) |
tags |
hirsute patch rls-ff-incoming |
hirsute patch rls-hh-incoming |
|
| 2021-04-15 15:18:15 |
Iain Lane |
gnome-terminal (Ubuntu Hirsute): assignee |
|
Iain Lane (laney) |
|
| 2021-04-15 15:18:39 |
Ken VanDine |
tags |
hirsute patch rls-hh-incoming |
hirsute patch |
|
| 2021-04-23 06:29:01 |
Mathew Hodson |
gnome-terminal (Ubuntu Hirsute): importance |
Undecided |
Medium |
|
| 2021-05-02 02:48:18 |
Mathew Hodson |
bug watch removed |
https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/253 |
|
|
| 2021-05-02 02:50:06 |
Mathew Hodson |
bug task added |
|
gnome-terminal |
|
| 2021-06-18 12:17:55 |
Launchpad Janitor |
gnome-terminal (Ubuntu): status |
New |
Confirmed |
|
| 2021-06-18 12:17:55 |
Launchpad Janitor |
gnome-terminal (Ubuntu Hirsute): status |
New |
Confirmed |
|
| 2021-10-06 03:49:41 |
Gunnar Hjalmarsson |
gnome-terminal (Ubuntu): status |
Confirmed |
Fix Committed |
|
| 2021-10-06 03:49:41 |
Gunnar Hjalmarsson |
gnome-terminal (Ubuntu): assignee |
Iain Lane (laney) |
Gunnar Hjalmarsson (gunnarhj) |
|
| 2021-10-06 03:50:00 |
Gunnar Hjalmarsson |
gnome-terminal (Ubuntu Hirsute): status |
Confirmed |
In Progress |
|
| 2021-10-06 03:50:00 |
Gunnar Hjalmarsson |
gnome-terminal (Ubuntu Hirsute): assignee |
Iain Lane (laney) |
Gunnar Hjalmarsson (gunnarhj) |
|
| 2021-10-06 18:21:03 |
Launchpad Janitor |
gnome-terminal (Ubuntu): status |
Fix Committed |
Fix Released |
|
| 2021-10-08 16:35:42 |
Timo Aaltonen |
gnome-terminal (Ubuntu Hirsute): status |
In Progress |
Fix Committed |
|
| 2021-10-08 16:35:43 |
Timo Aaltonen |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2021-10-08 16:35:46 |
Timo Aaltonen |
bug |
|
|
added subscriber SRU Verification |
| 2021-10-08 16:35:49 |
Timo Aaltonen |
tags |
hirsute patch |
hirsute patch verification-needed verification-needed-hirsute |
|
| 2021-10-11 16:18:41 |
Gunnar Hjalmarsson |
tags |
hirsute patch verification-needed verification-needed-hirsute |
hirsute patch verification-done verification-done-hirsute |
|
| 2021-10-14 21:13:04 |
Brian Murray |
removed subscriber Ubuntu Sponsors Team |
|
|
|
| 2021-10-19 16:48:16 |
Launchpad Janitor |
gnome-terminal (Ubuntu Hirsute): status |
Fix Committed |
Fix Released |
|
| 2021-10-19 16:48:22 |
Brian Murray |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2022-05-20 16:03:50 |
Bug Watch Updater |
gnome-terminal: status |
Unknown |
Fix Released |
|
