/bin/bash not in /etc/shells, causing login window/fast user switch applet hilarity

There was a bash update recently (3.2-0ubuntu17), so I'm guessing it was that.

bash.postrm correctly removes /bin/bash and /bin/rbash from /etc/shells.

bash.postinst should have added them, but seems not to have.

Workaround:
sudo /usr/sbin/add-shell /bin/bash
sudo /usr/sbin/add-shell /bin/rbash

Confirming. This affects the package (3.2-0ubuntu17) in hardy-proposed, and probably should be high importance.

From the changelog: 'Only call add-shell on new installations; guard remove-shell in post removal.' - however, the guarding of remove-shell doesn't work because the old postrm script gets executed in the upgrade (I think)

Same problem, following is the package update log

Commit Log for Sat May 10 11:03:27 2008
Upgraded the following packages:
bash (3.2-0ubuntu16) to 3.2-0ubuntu17
friendly-recovery (0.1) to 0.1.2
libmysqlclient15off (5.0.51a-3ubuntu5) to 5.0.51a-3ubuntu5.1
mysql-common (5.0.51a-3ubuntu5) to 5.0.51a-3ubuntu5.1

No users in login window (with human-list theme) and just current user in user-switcher gnome panel applet

Yep. The same for me after recent update. 'sudo add-shell /bin/bash' didn't make me happy 'cause the story continues — there's no faces.

Oh sorry. It solved. Thank you!

fixed in 3.2-3ubuntu1

uploaded bash 3.2-0ubuntu18 to hardy-proposed

This solved my problem as well.

Why does 3.2-0ubuntu18 change the behaviour in the postrm? Now remove-shell is not called any more on package removal. This change should be dropped, or properly justified in the changelog.

I concur with Martin's comments; it looks wrong to not call remove-shell on postrm remove, so this is a regression.

Why the need to guard add-shell in postinst (so it only runs on new installs) in the first place? Why not just run it regardless like before? If the shells are already in /etc/shells, they don't get added a second time.

Accepted into -proposed, please test and give feedback here

All right, I can see /bin/bash in /etc/shells again after updating to 3.2-0ubuntu18 (from 3.2-0ubuntu17).

Works here, too.

This bug only affected the previous hardy-proposed version, thus it can be closed in Hardy now.

mayank - Why did you add a remote bug link (with no actual upstream bug and no comment) to an already fixed bug?