Interrupt signal not handled properly for cli and gtk interfaces
Bug #327810 reported by
Marc Tardif
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Checkbox |
Fix Released
|
Medium
|
Marc Tardif |
Bug Description
When sending an interrupt signal to checkbox, ie ctrl-c, the behavior doesn't actually interrupt the application. For example, in the command line interface, sending the signal after the introduction results in the application proceeding with the subsequent information gathering step. And, in the gtk interface, the application doesn't stop but then pressing next suddenly stops with several repetitive KeyboardInterrupt stack traces. Instead, the behavior should be as expected and the application should simply be interrupted. Ideally, the application should catch the signal and attempt to flush cached information such as the persisted information.
Related branches
Changed in checkbox: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
An annoying side effect of this bug is that the only way to interrupt the application is to set it to background and then send a kill signal to checkbox.