gedit crashed with SIGSEGV on file save

[Clemens Vermeulen]

Gedit crashed on file save.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: gedit 3.20.2-0ubuntu1~xenial1 [origin: LP-PPA-gnome3-team-gnome3-staging]
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri May 20 16:14:19 2016
ExecutablePath: /usr/bin/gedit
InstallationDate: Installed on 2016-05-05 (15 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421)
ProcCmdline: gedit
SegvAnalysis:
 Segfault happened at: 0x7f8aba82ae01: testb $0x40,0x310(%rbp)
 PC (0x7f8aba82ae01) ok
 source "$0x40" ok
 destination "0x310(%rbp)" (0x00000310) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gedit
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gedit crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Ubuntu GNOME (ug-bot)]

StacktraceTop:
 compare_directory (model=model@entry=0x14d3810, a=a@entry=0x7fff84bf7cc0, b=b@entry=0x7fff84bf7ce0, impl=<optimized out>) at /build/gtk+3.0-BjsMee/gtk+3.0-3.20.5/./gtk/gtkfilechooserwidget.c:4112
 name_sort_func (model=0x14d3810, a=0x7fff84bf7cc0, b=0x7fff84bf7ce0, user_data=<optimized out>) at /build/gtk+3.0-BjsMee/gtk+3.0-3.20.5/./gtk/gtkfilechooserwidget.c:4195
 compare_array_element (a=<optimized out>, b=<optimized out>, user_data=0x7fff84bf8060) at /build/gtk+3.0-BjsMee/gtk+3.0-3.20.5/./gtk/gtkfilesystemmodel.c:766
 msort_with_tmp () at /tmp/apport_sandbox_AYysUW/lib/x86_64-linux-gnu/libglib-2.0.so.0
 msort_with_tmp () at /tmp/apport_sandbox_AYysUW/lib/x86_64-linux-gnu/libglib-2.0.so.0

[Jeremy Bícha (jbicha)]

This is fixed with today's GTK 3 update in the GNOME3 PPA.

Thank you for taking the time to report this bug!