Seems to be fixed with latest bash update:
bash (4.4-2) unstable; urgency=medium
* Apply upstream patches 001 - 005.
- Closes: #844299, LP: #1641832.
* Don't build with PIE. Closes: #842037.
-- Matthias Klose Tue, 15 Nov 2016 19:49:00 +0100
I ran into the same issue. After increasing swap, I am now able to login again.
However, every bash process now uses over 1 GB of virtual memory:
18541 pts/2Ss 0:00241 1021 1069166 4828 0.4 /bin/bash
18553 pts/3Ss 0:01120 1021 1069234 1628 0.1 /bin/bash
18639 pts/4
Can confirm this bug. Just for the record. As a workaround I use for remote
login:
ssh -t root@server "/bin/dash"
or locally
su -l -s "/bin/dash"
After got the root shell changed to zsh I'm able to make some more
actions. Starting bash as login shell results in error (see appended
strace-log)
When starting without "-l" there is no problem. So something went wrong
in loginscripts? Have no idea where to search.
execve("/bin/bash", ["bash
Package: bash
Version: 4.4-1
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Tried to login on server or "su -" but got only
-su: xmalloc: cannot allocate 80008 bytes (1626112 bytes allo
5 matches
Mail list logo
