Uncaught exception (due to SIGHUP signal)

[Günther Thomsen]

My workstation lost briefly its network connectivity (during which it might have been given a new IP address by the DHCP server), which caused some mayhem.  My homedirectory is on a NFS server, so for the time of the outage (about 3m), the workstation was expectedly quite unusable. Not quite so expected was, that multiple applications failed, including caja (whatever that might be), mate-terminal and wnck-applet (wth?) suffered a segfault (in libgdk-3 and libxul).  Most everything failed, except Emacs and VLC.

terminator was started (in background) from bash within a mate terminal window, so it's perhaps expected that it terminated as well, but shouldn't it handle a SIGHUP more gracefully?  Since the mate-terminal crashed, I'm not sure who sent the SIGHUP.  Perhaps the x-session-manager (mate-session) or lightdmq -- it's not obvious from the log files, but dbus-daemon was quite busy activating services once the network came back.

--8<--

Uncaught exception

An error occurred in Terminator:

Exception SignalException: SIGHUP
    at /usr/bin/terminator:194:in `read'
    at /usr/bin/terminator:194:in `have_same_content'
    at /usr/bin/terminator:199:in `install_terminfo_in'
    at /usr/bin/terminator:85:in `launch0'
    at /usr/bin/terminator:21:in `block in launch'
    at /usr/share/software.jessies.org/terminator/Resources/salma-hayek/bin/show-alert.rb:161:in `initialize'
    at /usr/share/software.jessies.org/terminator/Resources/salma-hayek/bin/show-alert.rb:173:in `new'
    at /usr/share/software.jessies.org/terminator/Resources/salma-hayek/bin/show-alert.rb:173:in `report_exceptions'
    at /usr/bin/terminator:21:in `launch'
    at /usr/bin/terminator:238:in `<main>'

Package 28.187.7355
Revision 7355 (7355)
Built 2019-03-13T09:21:16-07:00

Please mail this error message to terminat...@googlegroups.com.

-->8--

Debian 9.8 here, with mate-terminal 1.16.3-1.

cheers

~ Guenther