Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#63276 - Pacman should reset or ask to set a valid shell after in- and uninstallation of a shell
Attached to Project:
Arch Linux
Opened by P. S. (postix) - Thursday, 25 July 2019, 12:41 GMT
Last edited by Doug Newgard (Scimmia) - Thursday, 25 July 2019, 13:08 GMT
Opened by P. S. (postix) - Thursday, 25 July 2019, 12:41 GMT
Last edited by Doug Newgard (Scimmia) - Thursday, 25 July 2019, 13:08 GMT
|
DetailsShort description:
pacman changes shell in /etc/passwd for logged in the user at installation of the shell, but keeps this uninstalled shell in /etc/passwd after removal. Details: If zsh is installed via pacman: > pacman -S zsh but not set as default by the user and later removed again with > pacman -R zsh it happend to me that the shell defined for my user account in /etc/passwd has been changed from bash to zsh. After the removal and a reboot it kept beeing zsh and sddm throw me an error at the login, saying "invalid password". I think at this point pacman is responsible to reset the defined shell back to the former one or to prompt the user to choose another valid shell. Additional info: Pacman v5.1.3 - libalpm v11.0.3 |
This task depends upon
Because this is something, which really annoyed me: An application which changes import config files without telling the user and keeps them even after uninstallation.