Description of problem: I am running into this issue with rawhide virtual guests. When logging on to guest, it says: -bash: cannot set terminal process group (-1): Inappropriate ioctl for device -bash: no job control in this shell When spawning bash, it does: [root@localhost ~]# bash bash: no job control in this shell [root@localhost ~]# bash bash: no job control in this shell [root@localhost ~]# If ctrl+c is pressed, even if there is a job running on the foreground, the shell takes it in as ctrl+alt+del sequence and reboots: [ root@localhost ~]# ping www.redhat.com PING origin-www.redhat.com (209.132.177.50) 56(84) bytes of data. 64 bytes from www.redhat.com (209.132.177.50): icmp_seq=1 ttl=115 time=85.5 ms 64 bytes from www.redhat.com (209.132.177.50): icmp_seq=2 ttl=115 time=84.7 ms Broadcast message from root (unknown) at 18:17 ... The system is going down for reboot NOW! Control-Alt-Delete pressed Version-Release number of selected component (if applicable): # rpm -q bash bash-4.0.33-1.fc12.x86_64 How reproducible: Everytime. Steps to Reproduce: 1. Install rawhide. Install a guest with the rawhide distro: virt-install --name rawhide-20091005_x86_64 --location http://qafiler.bos.redhat.com/fedora/rawhide/nightly/rawhide-20091005/x86_64/os/ --hvm --nographics --ram 1024 --file-size 10 --file /var/lib/libvirt/images/rawhide-20091005_x86_64.img --accelerate --os-variant=virtio26 --extra-args " console=tty0 console=ttyS0,115200 " 2. Login to the guest. 3. Actual results: Expected results: Additional info:
This seems to be similar to bug #519237. Can you please try to update to util-linux-ng-2.16-10.2.fc12?
(In reply to comment #1) > This seems to be similar to bug #519237. Can you please try to update to > util-linux-ng-2.16-10.2.fc12? Seems like it didn't help?: login: root Password: Last login: Wed Oct 7 07:08:27 on ttyS0 -bash: cannot set terminal process group (-1): Inappropriate ioctl for device -bash: no job control in this shell [root@localhost ~]# rpm -q util-linux-ng util-linux-ng-2.16-10.2.fc12.x86_64 [root@localhost ~]#
And when you do same steps like James in comment #27 (rebuild dracut initrd and reboot)?
(In reply to comment #3) > And when you do same steps like James in comment #27 (rebuild dracut initrd and > reboot)? That worked.. Looks like # dracut --force /boot/initramfs-$(uname -r).img $(uname -r) was the cure.
So it's absolutely duplicate of bug #519237. *** This bug has been marked as a duplicate of bug 519237 ***