Interrupt signal not handled properly for cli and gtk interfaces

Bug #327810 reported by Marc Tardif
2
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

Revision history for this message
Marc Tardif (cr3) wrote :

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.

Changed in checkbox:
assignee: nobody → cr3
importance: Undecided → Medium
status: New → Fix Committed
Revision history for this message
Marc Tardif (cr3) wrote :

This has been fixed by changing the way response messages are handled in the gtk interface which now raise a KeyboardInterrupt exception when the application is closed or interrupt. And, by letting the KeyboardInterrupt exception percolate in the command line interface which was previously calling sys.exit(1). In both cases, the reactor can now handle the same exception consistently.

Marc Tardif (cr3)
Changed in checkbox:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.