Bug 1172381

Probably not environment-modules problem. See bug 1147043. However, I'm not sure if this particular problem is related to "at", so I'm leaving the bug open for now.

huh - what has at to do with opening konsole?

Oops, sorry, didn't mean to change the component to at...

(In reply to Rex Dieter from comment #0)
> I *think* this started recently with bash security fixes...  opening a
> konsole now gives initial output:
> 
> bash: module: line 1: syntax error: unexpected end of file
> bash: error importing function definition for `BASH_FUNC_module'

Does this go away with a system reboot?  This will happen if you update bash across versions with different function name mangling, without restarting all processes which have function definitions in their environment.

I've rebooted at least several times since this started.

(In reply to Rex Dieter from comment #5)
> I've rebooted at least several times since this started.

Thanks.  I cannot reproduce this with the package versions you provided.  It is likely that this is an interaction with a local system settings or another package.

Does “bash -l” show the same error message?  If yes, could you attach the output of “bash -x -l </dev/null 2>log.txt” to this bug (or send it to me privately in case you are worried about the data found in it)?

OK, I'll dig deeper when I have access to this laptop again.  (marking needinfo on myself). :)

I can confirm this does not happen on other f20 boxes I have at work, so you're likely right this is coming from somewhere besides what we've looked at yet.

Created attachment 983547 [details]
requested log.txt

Seeing it on my f21 laptop now too. :(

Rex - I think the output of "env" from your login shell would be useful, perhaps from a kde autostart script?

install eclipse TCF 1.2 plugin from marketplace
http://marketplace.eclipse.org/content/tcf-terminals

1) start eclipse
2) ctrl-alt-T, start a new terminal

any time bash is executed inside this different kind of TTY, the error throws up

bash: module: line 1: syntax error: unexpected end of file
bash: error importing function definition for `BASH_FUNC_module'
[user1@localhost ~]$ 
[user1@localhost ~]$ bash -c "pwd"
bash: module: line 1: syntax error: unexpected end of file
bash: error importing function definition for `BASH_FUNC_module'
/home/user1
[user1@localhost ~]$ echo $TERM
ansi

did not happen in
xterm
linux-console
gnome-terminal

speculation
may have something to do with 
a) TTY
b) being the sub-process of another process

does not have to do with being a login shell

Created attachment 989320 [details]
diff_ansi_gnometerminal.txt

attached is a diff between the exported environment of the eclipse-term and gnome-terminal 
set > ~/tmp/a1 # eclipse
set > ~/tmp/a2 # gnome-terminal
diff ~/tmp/a1 ~/tmp/a2

there is an environment declaration 
declare -x BASH_FUNC_module
in the eclipse term

$ bash --version
GNU bash, version 4.3.33(1)-release (x86_64-redhat-linux-gnu)
Copyright (C) 2013 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.

Created attachment 989321 [details]
diff_ansi_gnometerminal_exports.txt

this contains the BASH_FUNC_module

export > ~/tmp/a1 # eclipse
export > ~/tmp/a2 # gnome-terminal
diff ~/tmp/a1 ~/tmp/a2

This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 '20'.

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 20 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.

Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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
bug.

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