thunar crashed with SIGSEGV in thunar_file_is_directory()

[k3t4mf3t4]

thunar crashed with SIGSEGV in g_scanner_unexp_token()

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: thunar 1.6.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-12.8-lowlatency 3.8.2
Uname: Linux 3.8.0-12-lowlatency i686
ApportVersion: 2.9.2-0ubuntu2
Architecture: i386
Date: Sat Mar 23 15:20:20 2013
ExecutablePath: /usr/bin/thunar
InstallationDate: Installed on 2013-03-23 (0 days ago)
InstallationMedia: Ubuntu-Studio 13.04 "Raring Ringtail" - Alpha i386 (20130312)
MarkForUpload: True
ProcCmdline: Thunar --daemon
SegvAnalysis:
 Segfault happened at: 0xb7769bc4: cmpl $0x2,0x10(%eax)
 PC (0xb7769bc4) ok
 source "$0x2" ok
 destination "0x10(%eax)" (0x00000010) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: thunar
StacktraceTop:
 ?? ()
 ?? ()
 g_scanner_unexp_token () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: thunar crashed with SIGSEGV in g_scanner_unexp_token()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 thunar_file_is_directory (file=file@entry=0x0) at thunar-file.c:2533
 thunar_list_model_cmp_func (a=0xb9a4a1e0, b=0x0, user_data=0xb99a80f8) at thunar-list-model.c:1016
 iter_compare (node1=node1@entry=0xb97b8738, node2=node2@entry=0xb97b8750, data=data@entry=0xbfbcf584) at /build/buildd/glib2.0-2.35.8/./glib/gsequence.c:232
 node_find_closest (haystack=0xb97b8738, needle=0xb97b8750, end=0xb9947490, iter_cmp=0xb6ca60c0 <iter_compare>, cmp_data=0xbfbcf584) at /build/buildd/glib2.0-2.35.8/./glib/gsequence.c:1766
 node_insert_sorted (node=<optimized out>, new=new@entry=0xb97b8750, end=0xb9947490, iter_cmp=iter_cmp@entry=0xb6ca60c0 <iter_compare>, cmp_data=cmp_data@entry=0xbfbcf584) at /build/buildd/glib2.0-2.35.8/./glib/gsequence.c:2004

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Sean Davis (bluesabre)]

Seems likely to be a one-off crash. Closing this issue out.