Bug#677508: gnome-terminal: received signal SIGSEGV in g_object_notify kills all terminals

2017-09-01 Thread doak
All terminal windows will still be closed if any one is killed by an SIGSEGV. Version: ii gnome-terminal 3.22.2-1 amd64 GNOME terminal emulator application There is a workaround starting a dedicated 'gnome-terminal-server:

Bug#677508: gnome-terminal: received signal SIGSEGV in g_object_notify kills all terminals

2014-07-15 Thread Oriol Mula-Valls
Hi, Our machines using Debian stable are currently affected by this bug. This is the stack trace: Core was generated by `gnome-terminal'. Program terminated with signal 11, Segmentation fault. #0 0x7f784f7bd816 in g_object_notify (object=0xc89b10, property_name=0x7f7850a3bf02

Bug#677508: gnome-terminal: received signal SIGSEGV in g_object_notify kills all terminals

2012-06-25 Thread Teodor MICU
2012/6/24 Josselin Mouette j...@debian.org: Thanks for the backtrace. However it is not usable per se. Could you install debugging symbols for gtk3 and vte, and try again? I've installed some additional gtk3 debug packages (libgtk-3-0-dbg was already installed). However, I cannot find any vte

Bug#677508: gnome-terminal: received signal SIGSEGV in g_object_notify kills all terminals

2012-06-24 Thread Josselin Mouette
Le jeudi 14 juin 2012 à 14:42 +0300, Teodor a écrit : Today I investigated why on some circumstances gnome-terminal will crash and kills all open terminals (and remote sessions). I can reproduce this problem by moving one tab between two g-t windows. The tab to be moved had an 'man ps'

Bug#677508: gnome-terminal: received signal SIGSEGV in g_object_notify kills all terminals

2012-06-14 Thread Teodor
Package: gnome-terminal Version: 3.4.1.1-1 Severity: important Hi, Today I investigated why on some circumstances gnome-terminal will crash and kills all open terminals (and remote sessions). I can reproduce this problem by moving one tab between two g-t windows. The tab to be moved had an 'man