thunar crashed with SIGSEGV in thunar_file_compare_by_name()

[Weiller]

weiller@weiller-MS-7641:~$ lsb_release -rd
Description: Ubuntu Yakkety Yak (development branch)
Release: 16.10

weiller@weiller-MS-7641:~$ sudo apt-cache policy thunar
[sudo] senha para weiller:
thunar:
  Instalado: 1.6.10-2ubuntu2
  Candidato: 1.6.10-2ubuntu2
  Tabela de versão:
 *** 1.6.10-2ubuntu2 500
        500 http://mirror.ufscar.br/ubuntu yakkety/universe amd64 Packages
        500 http://cz.archive.ubuntu.com/ubuntu yakkety/universe amd64 Packages
        100 /var/lib/dpkg/status
     1.6.10-2ubuntu1 500
        500 http://br.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: thunar 1.6.10-2ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-30.49-generic 4.4.13
Uname: Linux 4.4.0-30-generic x86_64
ApportVersion: 2.20.2-0ubuntu1
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Jul 14 07:33:50 2016
ExecutablePath: /usr/bin/thunar
InstallationDate: Installed on 2016-06-24 (19 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
LocalLibraries: /usr/local/lib/libffi.so.6.0.4
ProcCmdline: Thunar --daemon
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: thunar
StacktraceTop:
 thunar_file_compare_by_name ()
 ?? ()
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_sequence_insert_sorted_iter () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: thunar crashed with SIGSEGV in thunar_file_compare_by_name()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[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 #1495409, 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.