Bug 804975

Summary:	sys-apps/qingy resetting terminal trigger has incorrect behavoiur
Product:	Gentoo Linux	Reporter:	Bogdan <bogdan.pylypenko107>
Component:	Current packages	Assignee:	Gentoo's Team for Core System packages <base-system>
Status:	UNCONFIRMED ---
Severity:	normal	CC:	hangglider, sam
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Bogdan 2021-07-29 09:03:53 UTC

Qingy resets login prompt so quickly, that pressed Ctrl-C combination may call qingy trigger, which block tty after some number of prompt resettings.

Please, add some timeout after resetting terminal, before enabling read info from stdin. For example - this timeout may be 333ms (1/3 of second) - it is enough to delay before entering a new login and comfort for human, but not enough to overload the system.

Reproducible: Always

Steps to Reproduce:
1. Configure qingy on tty2.
2. Switch to tty2 (by calling Ctrl-Alt-F2).
3. Stay pressed Ctrl-C combination.
Actual Results:  
qingy block tty for 5 minutes.

Expected Results:  
Qingy must clear/flush stdin at new login prompt session and delay before read new login/password combination.

Please, resets display fully, not just by adding new prompt to the end of display buffer. More info at https://bugs.gentoo.org/show_bug.cgi?id=804972

Expected usage case:
1) start login prompt session;
2) block reading of chars/events/key-combinations from input devices (keyboard/stdin/etc);
3) start delay for unblock input buffer of session;
4) clear display buffer;
5) put login prompt;
6) on delay finished (from point 3) - clear stdin buffer and start reading of next chars/events/key-kombinations from input devices (keyboard/stdin/etc).

Comment 1 Sam James archtester

2021-08-01 05:49:38 UTC

This sounds like it needs to be reported upstream, but it seems rather inactive.

Comment 2 hangglider 2023-10-04 12:11:38 UTC

Same here, and yes, seems to be an upstream issue.