Welcome to the Pacman bug tracker. Please search the current bugs and feature requests before filing a new one! Use advanced search and select "Search in Comments".

* Please select the correct category and version.
* Write a descriptive summary, background info, and provide a reproducible test case whenever possible.

FS#9147 - No newline printed when pacman receives SIGINT

Attached to Project: Pacman
Opened by Darwin Bautista (djclue917) - Thursday, 10 January 2008, 11:06 GMT
Last edited by Dan McGee (toofishes) - Friday, 11 January 2008, 05:16 GMT
Task Type Bug Report
Category Output
Status Closed
Assigned To Dan McGee (toofishes)
Architecture All
Severity Very Low
Priority Normal
Reported Version 3.1.0
Due in Version 3.1.1
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


Summary and Info:

pacman doesn't print a newline when it receives SIGINT:
* when it is asking for confirmation:
":: <pkg1> conflicts with <pkg2>. Remove <pkg2>? [Y/n]"
"Proceed with installation? [Y/n]"
* during a download (package and db)

Steps to Reproduce:
pacman -S <pkg> and pacman -Sy, then hit Ctrl+C.
This task depends upon

Closed by  Dan McGee (toofishes)
Friday, 11 January 2008, 05:16 GMT
Reason for closing:  Fixed
Additional comments about closing:  fixed in git .cgi?p=pacman.git;a=commit;h=0a65de10b1c d8bd450e47e735cb909eec13822d0
Comment by Dan McGee (toofishes) - Thursday, 10 January 2008, 13:55 GMT
Example output would be nice, can you attach a file with some?
Comment by Darwin Bautista (djclue917) - Thursday, 10 January 2008, 14:10 GMT
Attached the pacman output.
Comment by Xavier (shining) - Thursday, 10 January 2008, 15:42 GMT
Should we always print a newline when receiving a SIGINT then?
That sounds a bit funny, but why not?