XPost: linux.debian.bugs.dist
From: [email protected]

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

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)

XPost: linux.debian.bugs.dist
From: [email protected]

Hi!

On Thu, 2024-08-08 at 08:10:29 +0200, Santiago José López Borrazás wrote:

El 8/8/24 a las 02:27, Guillem Jover escribió:

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?

It plays after dpkg. Both apt, aptitude and dpkg play it for me.

Hmm, I can still not reproduce it with dpkg, while I can with apt and
aptitude.

In text consoles, the famous F2 to F6, something happens to me, as I described before, when I do it, both with apt; aptitude and dpkg, the
console closes when I finish the installation of a package.

Ah, thanks for the Linux console hint, I had not seen that behavior
before.

I'm sorry to insist, but can you show exactly the sequence of actions
that you do, because I still cannot reproduce this at all with only
dpkg. Here is my sequence with both dpkg and apt:

[On a normal terminal on the /root, do something like:]
# apt download pci.ids

[Ctrl+Alt+F2]
Debian ... tty2
login:
[Login as root into Linux console 2]
# dpkg -i pci.ids_*_all.deb
# echo "all ok"
[Ctrl+C works, everything ok.]

[Ctrl+Alt+F3]
Debian ... tty3
login:
[Login as root into Linux console 3]
# apt reinstall ./pci.ids_*_all.deb
[Session gets terminated, no further commands can be introduced, a
new login is required.]

Thanks,
Guillem

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)

XPost: linux.debian.bugs.dist
From: [email protected]

Control: tags -1 unreproducible moreinfo

Hi!

On Thu, 2024-08-08 at 00:05:38 +0200, Santiago José López Borrazás wrote:

Package: dpkg
Version: 1.22.11
Severity: important

With dpkg, when I am in console mode, with konsole, the combination
CTRL + C breaks. Non-graphical consoles break when installing a
package, either with dpkg or with apt.

In konsole it crashes when I want to install a package under dpkg
that does not work the console under konsole when doing CTRL + C and
with certain commands.

It also breaks when I do a ssh in local area that does not allow to
connect to certain devices remotely. It messes it up.

Check and fix it so it's not bad source code, because it's crashing
quite a bit through this package more than anything else.

I've seen this breakage after using apt or aptitude within a tmux
terminal within konsole, where after these commands end, job control
gets disabled on the terminal and Ctrl+C does not work anymore, and
doing «exec bash -i» will show a message stating so. But I've never
seen this behavior when running dpkg directly.

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)?

Thanks,
Guillem

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)

XPost: linux.debian.bugs.dist
From: [email protected]

Hi!

[ The quoting in your previous message got mangled, so it was a bit
hard to read. ]

On Thu, 2024-08-08 at 16:53:07 +0200, Santiago José López Borrazás wrote:

El 8/8/24 a las 13:09, Guillem Jover escribió:

Hmm, I can still not reproduce it with dpkg, while I can with apt > and aptitude. Me, with apt, aptitude and dpkg.
Ah, thanks for the Linux console hint, I had not seen that behavior > before.

I do, that's why I was reporting, that's the behavior that makes me, not
only in the text consoles, but also, in the Konsole, that's why this behavior.

Sorry, I meant that the Linux console closing was a new behavior I had
not seen before. I've seen this behavior on a terminal (such as
konsole) also inside tmux.

I'm sorry to insist, but can you show exactly the sequence of >

actions

that you do, because I still cannot reproduce this at all > with only dpkg. Here is my sequence with both dpkg and apt:

But... Do you have the unstable? Because I'm under Sid/Unstable.

I use unstable, updated several times a day.

So far so good, I have 4250 packages, plus 44 of Libreoffice.org and other Debian packages (AutoFirma de Spain, the local area printer I have, the FNMT configurator and Teamviewer).

[On a normal terminal on the /root, do something like:] # apt >

download pci.ids > > [Ctrl+Alt+F2] Debian ... tty2 login: [Login as root
into Linux > console 2] # dpkg -i pci.ids_*_all.deb # echo "all ok" [Ctrl+C

works, everything ok.]

The console closes, no matter if I do it in tty1 to tty6, it closes the same.

I'm still very surprised by this, and I can not reproduce it with
dpkg. Do you have any dpkg.cfg.d/ hooks installed, and what packages
do provide them? If you move those configuration fragments aside and
try running dpkg, does it still produce a non-working Ctrl+C?

[Ctrl+Alt+F3] Debian ... tty3 login: [Login as root into Linux > console
3] # apt reinstall ./pci.ids_*_all.deb [Session gets >

terminated, no further commands can be introduced, a new login is > required.]

Ditto, closes it.

At least for the issue I've seen with apt and Ctrl+C, I've tracked
this down to having the «adequate» package installed. If I remove that package then apt stops misbehaving. I'll either reassign the apt bugs
to adequate or file a new one, because I'm not sure who is misbehaving,
but I'd suspect adequate is the real culprit, which got recently
rewritten in Golang.

Thanks,
Guillem

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)