mcabber only handles SIGTERM and SIGINT, initiating a clean shutdown
sequence when receiving those signals. However, shutting down the system
or closing an xterm running mcabber produces SIGHUP, which is not
handled by mcabber and leaves the XMPP session in an undefined state.
This shows up as chat participants who have shut down their systems or
closed the terminal window still being shown as available for some
minutes, because the XMPP session was not properly terminated.

- -- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.10-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/mksh

Versions of packages mcabber depends on:
ii  libaspell15      0.60.7~20110707-1
ii  libassuan0       2.1.1-1
ii  libc6            2.17-92+b1
ii  libglib2.0-0     2.36.4-1
ii  libgpg-error0    1.12-0.1
ii  libgpgme11       1.4.3-0.1
ii  libidn11         1.28-1
ii  libloudmouth1-0  1.4.3-9
ii  libncursesw5     5.9+20130608-1
ii  libotr5          4.0.0-2.2
ii  libtinfo5        5.9+20130608-1

mcabber recommends no packages.

mcabber suggests no packages.

- -- no debconf information
iQJOBAEBCAA4BQJSM4gSMRpodHRwczovL3d3dy5kb21pbmlrLWdlb3JnZS5kZS9n
cGctcG9saWN5LnR4dC5hc2MACgkQt5o8FqDE8pZXAA/+Nu76ebZjVw49Te6BLi0E
oEe41j7K8pwkyZ5Uqj6hxDx0kQCdVV2XS9L3xcBaULbhoxNGs+W+YpWscReWrxkE
gAC7Yb9OlhR6B4PGR3lMapY2KN80K9+QxJUwoUmtvZTdcxb7FaQOmELy2LPDet9Q
zG+iIe42ISLnOAlxkDKdPqByIsPkZXnxihg1dOw3jxd3mxwlQr4n5Gig3bIjExIy
YHBr2OSRWPK2R16LU3feSWYlLMvTDQyrYOKJvc5PPZZFqeJpm6dukirTLCJM6eRH
sXUwo7ZgyFdLIMaKrmKqsWuiZYicmi5lQrNn5B7E12CP3A/mLx/3j9cWDAynCkp8
zsu4pFe1MzeJPgZOr2tcP1y7iXBYPFryMDg1pN9EMuGs13pN6AtGw2Axx27ynrmk
R6m7sJaDNLs031vtpAJAu9uRjCw6l7hGx0uVt0fkqGrWzVr8bHMjWuIrhSnVXLQG
586YFDAKf1eMw5CLQxiWxs6aETxgQ9KIL+P2dq6o3bC2CLqQ9l5HQOVFNyB9JzZW
K9BM4RK2zNPbrjZnP0/W/sHdJIAXOAOUI4b8fPAeMPVuRPowuN2+4mOPxsNXynPh
GrkBAN0Aqbi0BIatDmgDz3OcCpDYZ781s6MlaFNWjuK/gg/L6290KDEWe03r9qau
SKhIBHN3PO/5rGZN+VM2yAI=
=DaCE
-----END PGP SIGNATURE-----

Attached is a patch that fixes the issue; sent upstream.

Please note that the BTS web interface mangles cleartext attachments.
iQJOBAEBCAA4BQJSM5DyMRpodHRwczovL3d3dy5kb21pbmlrLWdlb3JnZS5kZS9n
cGctcG9saWN5LnR4dC5hc2MACgkQt5o8FqDE8pbM5RAA1XeKQsh/Oanq/L8NP4sB
+wsEN53uESgcCnnfOifzAKpuVdsvtPRldAi5J2IEEBmRoDbD5E9grhbb+SXyj1Cv
e13sJPOidoC4UrapQst40tkb7fNdFxjRBt89wLMKlJ6zdfyT5M9u4azGMAghJV7x
ugwrTUewNgTJuXtHRnpmn2fgbTdHqeQRt/NnCdfqUVQ7uuXwH4Fmql1lpqZPq5y1
Z8QRKVdco9Kn3brZdwPrE5K3nhyJk06wwZC6Qvjkf+BeD/ABI28X/xHgu/IUOv5i
miQyQVUHDwL+kEKC/woXnIO9Ec9w4MnB6xFZJ1TUN6ibBoW3o4GHOVaMlLM38wpz
zhMxwKcGnlarNNHfi7zKaOv5C7YIiTOlzW/NZ2pRR1Jwu3Spm8x+dWu4QQZnlpvY
IabzskxxPu8/32emHZrmUwPmvO39q7uaMgfRx+cJgo6wdn8UIB7I+owUt5RuUrKo
eE1VihbRwUsrEz9aaaEFbxRBn7bm8Del8J15qieveeeMDjUykcNIu9gMuMy9AUK4
5RLN0/KcOt1XmRBpn8uVA0cbiQvEGWLQ/tlpbp2PUmCXlOWdSBZkNmxT+WDtbOXE
4j0UXPbQYUGR++UNnq26nxu8ioKhZG3fknEhcl5kbWLaVQ/CTiLmql0CN/ADSXzY
qlC906mtfkjaxnfPAoV5iUE=
=4y0O
-----END PGP SIGNATURE-----

Hi,

Thanks for providing a patch for that problem. I'll review it and include
it with the next upload.

Cheers,
Rhalina

The patch has been included upstream.

- -- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.11-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/mksh

Versions of packages mcabber depends on:
ii  libaspell15      0.60.7~20110707-1
ii  libassuan0       2.1.1-1
ii  libc6            2.17-93
ii  libglib2.0-0     2.36.4-1
ii  libgpg-error0    1.12-0.2
ii  libgpgme11       1.4.3-0.1
ii  libidn11         1.28-1
ii  libloudmouth1-0  1.4.3-9
ii  libncursesw5     5.9+20130608-1
ii  libotr5          4.0.0-2.2
ii  libtinfo5        5.9+20130608-1

mcabber recommends no packages.

mcabber suggests no packages.

- -- no debconf information
iQJOBAEBCAA4BQJSd5aiMRpodHRwczovL3d3dy5kb21pbmlrLWdlb3JnZS5kZS9n
cGctcG9saWN5LnR4dC5hc2MACgkQt5o8FqDE8paBsRAAnMYEMYqyf/RgtTtnt4hh
BbI0JLVoNEaZ5OFw2zlO/AVNQzr816L1j95SJUom2XzI+uNXDm5QGd0Th0ghu/T3
A09w4rGK4RJL+TZKUKYZChu9FvyiTtTlirltwj3fh12lkI1Wy1tJ3Jt1irKTMSLW
S2ap+E/X1e9/osFFGXwDYncdAtHUFcjl0NUHxMcFkIdx3UAoN9tdR1QJZyyd7r0D
vJBMe+3V5mbCovkXVun1oLEB+a7aWKFbII6bHSUm0L02/2mqNzF930SansyvT97A
8r5AuQtXXCylcjzYKuGdLb38vuVGEWv15qKJAFgF+hpOiOekhHY1al9DJI9YWJyv
IDxbeTO41BctWOUI2MXE32FGONDqWO+fzkJcljec4QdJzbg6lNV/ew7m0cpl+qcC
Ol/3XrRSrr1cndRjjRP7sSjbGftVqJBZ3EV7v60SAaAvaPoOu8c9aAAU+QAuftsu
kshL1cW8JvtEe61F+bI8HsPLJcFApWiVhV4svIz+J50uIgrvVgcxImqLsM9OwfUw
ia9OwakXM2jobgUGMokw8Tq+IsnQS0kRdOl/fJ+tqgrt36rUre+VcdKZFOnTmc+c
YOEDOOUreelAeNtMj/1ZMqYE6HUX5JoZUORoo9XzJCzkr5qcKyv7RSaNoG5d34rI
BNYba4gBGG1wHjakfJGOynk=
=2U2U
-----END PGP SIGNATURE-----

I checked the code for 1.1.2-2 in Debian. Looks good.
I checked git repo of upstream, looks it has been fixed in
0.10.3.