Ctrl-C doesn't stop processes after updating to util-linux 2.11a anymore.
*** Bug 36840 has been marked as a duplicate of this bug. ***
*** Bug 39237 has been marked as a duplicate of this bug. ***
I reported Bug 39237, which I have now reported as a duplicate of this bug. The
problem is a regression
in /bin/login that happened sometime between util-linux-2.10s-8 and
util-linux-2.11a-4. I noticed the problem when I updated from Rawhide 20010310
(including util-linux-2.10s-8) to Rawhide 20010503
(including util-linux-2.11a-4). I was able to eliminate the problem on my
Rawhide 20010503 system by changing the single file /bin/login back to the
20010310 version of
/bin/login from util-linux-2.10s-8.
Fixed in 2.11b-1
Is there any chance you could make this fix available from people.redhat.com or
somewhere? It breaks more than just ^C, anything using /dev/tty is broken e.g.
"vlock -a" currently doesn't work. I rely on this to securely lock my
workstation here (xlock has some bugs, I don't like xscreensaver).
Aha! Many thanks ... I'll bookmark this!
*** Bug 40225 has been marked as a duplicate of this bug. ***
I just updated to Rawhide 20010701, including util-linux-2.11f-1, and this
problem seems to still
exist in 2.11f-1.
Yes, this seems to have b0rken again. It's not working for me in
It seems that this problem reappeared in util-linux-2.11f-11.7.1.
It's not always reproducible, though. Sometimes Ctrl-C works, sometimes it
The problem still appears in util-linux-2.11f-12 once in a while.
I reliably reproduce "bash: no job control in this shell" using RedHat 7.2
with util-linux-2.11f-12. Every time I telnet from an identically configured
machine to the target machine as a regular user, then "su", I see:
bash: no job control in this shell
Sounds like a race condition?
Anyway, I've seen a recurrence of the problem, symptom is dropping right back to
the login prompt when I log out of GNOME. This was with the latest Raw Hide