Bug 827844

Summary: Unable to use chsh
Product: [Fedora] Fedora Reporter: Michael S. <misc>
Component: util-linuxAssignee: Karel Zak <kzak>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: jonathan, kzak, mluscon
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-03 09:39:31 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
patch to not hardcode /bin in the spec
none
Do not hardcode /bin none

Description Michael S. 2012-06-03 09:13:52 UTC
Description of problem:
chsh refuse to change the shell to zsh, as it was moved from /bin/ to /usr/bin, and neither /etc/shells not the package have taken this in account.

See http://ask.fedoraproject.org/question/1785/why-chsh-shell-not-changed

Version-Release number of selected component (if applicable):
zsh-4.3.17-1.fc17.x86_64

How reproducible:
each time

Steps to Reproduce:
1. chsh -s /bin/zsh
  
Actual results:
"Shell not changed"

Expected results:
"Shell was changed"

Additional info:

A way to fix is to add to /etc/shells the correct path of zsh, ie in /usr/bin/

Comment 1 Michael S. 2012-06-03 09:17:24 UTC
Created attachment 588811 [details]
patch to not hardcode /bin in the spec

Here is a patch, I didn't test it yet, and I think we should take in account the upgrade issue ( ie, cleaning /etc/shells )

Comment 2 Michael S. 2012-06-03 09:20:55 UTC
Created attachment 588812 [details]
Do not hardcode /bin

Comment 3 Michael S. 2012-06-03 09:31:04 UTC
Comment on attachment 588811 [details]
patch to not hardcode /bin in the spec

Oops, uploaded the patch twice

Comment 4 Michael S. 2012-06-03 09:39:31 UTC
Mhh, seems I was wrong with the whole bug stuff and my testing was wrong, let me close the bug.