This bug was reported to Ubuntu Launchpad as: https://bugs.launchpad.net/bugs/609500 Opened xfce4-terminal preferences by clicking on "Edit -> Preferences". After simply clicking on each tab to verify the settings, I clicked the close button in the upper right corner. Instead of closing, the terminal crashed, taking all open instances down. DistroRelease: Ubuntu 10.10 Package: xfce4-terminal 0.4.5-1ubuntu1 Architecture: amd64 ExecutablePath: /usr/bin/xfce4-terminal ProcCmdline: xfce4-terminal --geometry=80x22 --display :0.0 --role=Terminal-0x1c5c000-8020-1279743176 --show-menubar --show-borders --hide-toolbars --working-directory /home/username SegvAnalysis: Segfault happened at: 0x7f266a4cf420 <exo_mutual_binding_unbind>: mov 0x20(%rdi),%rsi PC (0x7f266a4cf420) ok source "0x20(%rdi)" (0x00000020) not located in a known VMA region (needed readable region)! destination "%rsi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: xfce4-terminal StacktraceTop: exo_mutual_binding_unbind () terminal_preferences_dialog_response ( g_closure_invoke (closure=0xde4b90, signal_emit_unlocked_R (node=0xcd8580, g_signal_emit_valist (instance=0xfa00a0, Stacktrace available: https://bugs.launchpad.net/ubuntu/+source/xfce4-terminal/+bug/609500/+attachment/1474609/+files/Stacktrace.txt
Could someone give me a backtrace with exo + terminal compiled with debugging? Because I can't reproduce this.
Will a gdb backtrace work, or do I need to re-compile terminal?
with debugging it might give some better indication
Marking this one as resolved. It was found to be downstream only.