terminator crashed with SIGSEGV in g_signal_emit_valist()

[Stephan Springer]

I did nothing special, and suddenly terminator crashed.

ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: terminator 0.97-4
ProcVersionSignature: Ubuntu 4.2.0-30.35-generic 4.2.8-ckt3
Uname: Linux 4.2.0-30-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Feb 26 12:33:48 2016
ExecutablePath: /usr/share/terminator/terminator
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/terminator
SegvAnalysis:
 Segfault happened at: 0x7f1ef3414039: testb $0x10,0x14(%rax)
 PC (0x7f1ef3414039) ok
 source "$0x10" ok
 destination "0x14(%rax)" (0x00000014) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: terminator
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_by_name () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
Title: terminator crashed with SIGSEGV in g_signal_emit_valist()
UpgradeStatus: Upgraded to wily on 2015-09-29 (150 days ago)
UserGroups: adm cdrom dialout dip libvirtd lpadmin plugdev sambashare sudo video wireshark

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1232289, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

[Stephan Springer (geryon)]

Duplicate of a private bug? Sorry, I won't accept that.

[Stephen Boddy (stephen-j-boddy)]

Hi Stephan. I realise English is most likely a second language, but your comment #3 comes across like attitude. As far as I can tell the apport reported bugs have a degree of Launchpad automation. No person handled this and set it to be a duplicate of a private bug. I think the apport related bugs are reported initially as Private because they could contain sensitive details. It seems like Launchpad does not recognise that an earlier bug is still Private (i.e. the reporter never set it to Public) and marks newer bugs as duplicate of the still Private bug. This is why you are not able to see the original bug - neither can I. There is an even earlier Public bug #976158 which has the same kind of error. As someone who can code Python, I do not personally have the skills to dig into internal GTK stack traces to understand the cause of the SIGSEGV's.

[Stephen Boddy (stephen-j-boddy)]

Furthermore, you have not attached stack traces and the like, meaning this bug would be impossible to investigate even for someone who did have the necessary C skills. Bug #976158 does have traces, but of course there might be a different root cause there.

Marking as a duplicate of #976158.