Cannot interrupt busy-printing command via normal means #1

New Issue

Open

opened 2022-10-07 01:54:07 +00:00 by Ghost · 0 comments

Ghost commented

2022-10-07 01:54:07 +00:00

I ran cat /dev/random and then tried to interrupt it using the usual Ctrl-C and Ctrl-\, neither of which worked. I can stop it by ending the terminal emulator process in one of the usual ways, including clicking on the window's Close button and selecting "Force Quit" in my DE's "process is not responding" window. However, it would be nice to stop commands like this without closing the terminal emulator. For what it's worth, gnome-terminal interrupts the command on Ctrl-C and Ctrl-\ as expected.

I get the similar behavior with cat /dev/zero and while true; do printf '\n'; done, but not on while true; do printf ''; done or cat /dev/random | tail. It seems that constantly printing might be keeping the terminal emulator too busy to respond to input. Sometimes pressing the window's Close button quickly after running a command can cause it to exit without a force quit, but it was not consistently reproducible. As a bonus, I somehow got this error once:

[2022-10-07T01:31:33Z ERROR smithay_client_toolkit::event_loop] Error trying to flush the wayland display: Broken pipe (os error 32)

I ran `cat /dev/random` and then tried to interrupt it using the usual `Ctrl-C` and `Ctrl-\`, neither of which worked. I can stop it by ending the terminal emulator process in one of the usual ways, including clicking on the window's Close button and selecting "Force Quit" in my DE's "process is not responding" window. However, it would be nice to stop commands like this without closing the terminal emulator. For what it's worth, `gnome-terminal` interrupts the command on `Ctrl-C` and `Ctrl-\` as expected. I get the similar behavior with `cat /dev/zero` and `while true; do printf '\n'; done`, but not on `while true; do printf ''; done` or `cat /dev/random | tail`. It seems that constantly printing might be keeping the terminal emulator too busy to respond to input. Sometimes pressing the window's Close button quickly after running a command can cause it to exit without a force quit, but it was not consistently reproducible. As a bonus, I somehow got this error once: ``` [2022-10-07T01:31:33Z ERROR smithay_client_toolkit::event_loop] Error trying to flush the wayland display: Broken pipe (os error 32) ```

Ghost changed title from ~~Cannot interrupt busy command via normal means~~ to Cannot interrupt busy-printing command via normal means

2022-10-07 01:54:17 +00:00

No Label

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: mars/piss#1

No description provided.