Description of problem: crontab -e fails due to missing /bin/vi when the EDITOR environment variable is not set and exported Version-Release number of selected component (if applicable): [root@v5218c3 tmp]# rpm -qf /usr/bin/crontab cronie-1.4.8-10.fc16.i686 [root@v5218c3 tmp]# How reproducible: always Steps to Reproduce: [root@v5218c3 tmp]# unset EDITOR [root@v5218c3 tmp]# crontab -e -u vopicka /bin/sh: /bin/vi: No such file or directory crontab: "/bin/vi" exited with status 127 [root@v5218c3 tmp]# Actual results: bin/vi: No such file or directory Expected results: crontab file opened in vi Additional info: There is easy workaround EDITOR=/usr/bin/vi crontab -e -u vopicka or export EDITOR=/usr/bin/vi crontab -e -u vopicka but anyway, this is a bug and should be fixed.
It's bug of vim, you can add karma: https://admin.fedoraproject.org/updates/FEDORA-2012-8354/vim-7.3.515-2.fc16 *** This bug has been marked as a duplicate of bug 822314 ***