Hi! On Thu, 2024-08-08 at 01:31:34 +0200, Santiago José López Borrazás wrote: > El 8/8/24 a las 01:21, Guillem Jover escribió: > > Have you really experienced this after running dpkg standalone > > (without using apt or aptitude) on a terminal where Ctrl+C is still > > working before calling dpkg (so not after having called apt)?
> Yes. I experience this in dpkg and doing it outside of aptitude. And even if > I do it with apt as well, three quarters of the same.But it is strange, > because with other applications they do not fail. It does it with aptitude, > apt and dpkg. I will try "exec bash -i", but I don't think it will tell me > anything, I will try it before sending this mail. It shows me all this: > bash: unable to set terminal process group (265894): ioctl function not > appropriate for the device bash: no job control in this shell As I say, it's > strange. Well, I can very easily reproduce this with apt or aptitude, but not with dpkg alone. Just to make sure, before you call dpkg, Ctrl+C works, and after calling dpkg it stops working? Otherwise can you start a clean session where Ctrl+C works, then call the dpkg command you use to reproduce this and then check again whether Ctrl+C works? Thanks, Guillem
