[Bug 1951155] [NEW] export i fails to work in bash
ytxmobile
1951155 at bugs.launchpad.net
Tue Nov 16 18:42:52 UTC 2021
Public bug reported:
I ran the following commands:
```
# In parent shell
export a=1
export i=2
bash # open child shell
# In child shell
echo $a # 1
echo $i # (empty)
exit
```
This bug happens when exporting the "i" variable from parent shell to child shell.
I have not tested what other variable names would trigger this bug.
* My OS: Ubuntu 20.04 LTS
* Bash version (running `bash --version`):
```
GNU bash, version 5.0.17(1)-release (x86_64-pc-linux-gnu)
Copyright (C) 2019 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
```
I have also tested in the `sh` shell and did not see the problem:
```
# In parent shell
export a=1
export i=2
sh # open child shell
# In child shell
echo $a # 1
echo $i # 2
exit
```
** Affects: bash (Ubuntu)
Importance: Undecided
Status: New
** Tags: export
** Description changed:
Try to run the following commands:
```
# In parent shell
export a=1
export i=2
bash # open child shell
# In child shell
echo $a # 1
echo $i # (empty)
+ exit
```
This bug happens when exporting the "i" variable from parent shell to child shell.
I have not tested what other variable names would trigger this bug.
* My OS: Ubuntu 20.04 LTS
* Bash version (running `bash --version`):
```
GNU bash, version 5.0.17(1)-release (x86_64-pc-linux-gnu)
Copyright (C) 2019 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
```
+
+ I have also tested in the `sh` shell and did not see the problem:
+ ```
+ # In parent shell
+ export a=1
+ export i=2
+ sh # open child shell
+ # In child shell
+ echo $a # 1
+ echo $i # 2
+ exit
+ ```
** Description changed:
- Try to run the following commands:
+ I ran the following commands:
```
# In parent shell
export a=1
export i=2
bash # open child shell
# In child shell
echo $a # 1
echo $i # (empty)
exit
```
This bug happens when exporting the "i" variable from parent shell to child shell.
I have not tested what other variable names would trigger this bug.
* My OS: Ubuntu 20.04 LTS
* Bash version (running `bash --version`):
```
GNU bash, version 5.0.17(1)-release (x86_64-pc-linux-gnu)
Copyright (C) 2019 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
```
I have also tested in the `sh` shell and did not see the problem:
```
# In parent shell
export a=1
export i=2
sh # open child shell
# In child shell
echo $a # 1
echo $i # 2
exit
```
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to bash in Ubuntu.
https://bugs.launchpad.net/bugs/1951155
Title:
export i fails to work in bash
Status in bash package in Ubuntu:
New
Bug description:
I ran the following commands:
```
# In parent shell
export a=1
export i=2
bash # open child shell
# In child shell
echo $a # 1
echo $i # (empty)
exit
```
This bug happens when exporting the "i" variable from parent shell to child shell.
I have not tested what other variable names would trigger this bug.
* My OS: Ubuntu 20.04 LTS
* Bash version (running `bash --version`):
```
GNU bash, version 5.0.17(1)-release (x86_64-pc-linux-gnu)
Copyright (C) 2019 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
```
I have also tested in the `sh` shell and did not see the problem:
```
# In parent shell
export a=1
export i=2
sh # open child shell
# In child shell
echo $a # 1
echo $i # 2
exit
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1951155/+subscriptions
More information about the foundations-bugs
mailing list