Opened 13 years ago

Closed 13 years ago

Last modified 13 years ago

#2454 closed Bug (fixed)

gtk client handles SIGINT (ctrl-c) oddly

Reported by: charles Owned by: charles
Priority: Normal Milestone: 1.76
Component: GTK+ Client Version: 1.75
Severity: Minor Keywords:
Cc:

Description (last modified by charles)

As pointed out by "claw" the forums, the GTK+ client requires three signals to be sent before passing the signal along to the default signal handler.

I'm not sure why it's done this way. It predates my stint on the GTK+ client and I don't really see the reason for it. The rationale isn't commented anywhere.

At any rate, a first SIGINT should attempt an orderly shutdown as if the "Exit" menu option were clicked. To handle more pressing situations, the second SIGINT should revert to the system's default handler.

Change History (6)

comment:1 Changed 13 years ago by charles

  • Status changed from new to assigned

comment:2 Changed 13 years ago by charles

  • Resolution set to fixed
  • Status changed from assigned to closed

fixed in trunk by r9196 for 1.80.

comment:3 Changed 13 years ago by charles

  • Description modified (diff)

comment:4 Changed 13 years ago by charles

  • Keywords backport added

comment:5 Changed 13 years ago by charles

  • Milestone changed from None Set to 1.80

comment:6 Changed 13 years ago by charles

  • Keywords backport removed
  • Milestone changed from 1.80 to 1.76

backported to 1.7x branch for 1.76 by r9358.

Note: See TracTickets for help on using tickets.