thunar crashed with SIGSEGV in thunar_file_is_directory()

[Jackson Doak]

Thunar crashed when pressing the up directory button. This happens semi-regularly, but cannot be reliably reproduced.

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: thunar 1.6.3-1ubuntu5
ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4
Uname: Linux 3.16.0-22-generic x86_64
ApportVersion: 2.14.7-0ubuntu5
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon Oct 13 18:46:02 2014
ExecutablePath: /usr/bin/thunar
InstallationDate: Installed on 2014-05-25 (141 days ago)
InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140524)
ProcCmdline: Thunar --sm-client-id 248756da2-e782-4371-8ee7-18753c39a4bd --daemon
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f34ba71b4c2 <thunar_file_is_directory+2>: cmpl $0x2,0x20(%rdi)
 PC (0x7f34ba71b4c2) ok
 source "$0x2" ok
 destination "0x20(%rdi)" (0x00000020) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: thunar
StacktraceTop:
 thunar_file_is_directory (file=file@entry=0x0) at thunar-file.c:2533
 thunar_list_model_cmp_func (a=0x7f348c2db4c0, b=0x0, user_data=<optimised out>) at thunar-list-model.c:1017
 ?? () 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_is_directory()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm autopilot 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 #1147349, 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.