Created attachment 999830 [details]
PACKAGES UPDATED and LOG INFO (journalctl -b)
Description of problem:
After latest update (see attached file for packages updated) it was not possible to login as normal user, either using a gdm sesion or via "su <normaluser>", after login as root. Only root can log in.
Once connected as root, the log system (via journalctl command) reports crash messages, apparently related to bash
Version-Release number of selected component (if applicable):
bash version 4.2.53(1)-release (x86_64-redhat-linux-gnu)
Steps to Reproduce:
1. Update a number of packages (su -c 'yum update' followed by reboot)
2. Normal user failed to login. Root user can login
3. As root, su <normaluser> gets blocked. journalctl -b reports "crash in '/usr/bin/bash'"
Please, see attached file (packages updated, plus outputs of journalctl
Trying 'su <normaluser>' while logged in as root, it does not proceed. If I then cancel (Ctrl + C) it takes a while before responding and finally exists with the following message:
Cbash: $TMP: ambiguous redirect
bash: $TMP: ambiguous redirect
bash: [: : integer expression expected
Segmentation fault (core dumped)
Please, note, this is the same issue as Bug 1200367 - [abrt] bash: yyparse(): bash killed by SIGSEGV (edit), for which the report has been generated by abrt and is much more detailed.
Sorry if I am reporting duplicates. It is the first time that I report a bug.
I am able to create a new normal user with 'useradd', and login works perfectly for that user. The bash problem affects only one particular user normal user: the initially existing one. Attempts to "su" to that user get stuck with ~70% CPU usage, and finally get aborted with "bash: $TMP: ambiguous redirect" and "Segmentation fault (core dumped)" messages.
I found the caused of the problem, although I am not sure if I understand the reason...
First of all, it is not a "bash" bag and had nothing to do with updated packages from fedora.
Before the Fedora update, which I mentioned, I installed another program called "edirect" (a bunch of scripts from Entrez (PubMed, a bibliographic database). The automatic installation of that thing, added a new PATH to .bash_profile. It added as well a new line to .bashrc with "source ~/.bash_profile". Apparently, that makes bash crash.
I ignore if this is a bug of bash. I seems to me that it is simply a bad idea to "source" .bash_profile from .bashrc
Well, by default ~/.bash_profile sources ~/.bashrc ...now when ~/.bashrc also sources ~/.bash_profile...I'm sure you get the idea...
So, I think we've found the problem :) Feel free to reopen if this is not your case.
*** Bug 1200367 has been marked as a duplicate of this bug. ***