thunar crashed with SIGSEGV in g_type_create_instance()

[San]

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu

san@azazel:~$ lsb_release -rd
Description: Ubuntu quantal (development branch)
Release: 12.10

2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center

san@azazel:~/Pobrane$ apt-cache policy thunar
thunar:
  Zainstalowana: 1.4.0-1ubuntu1
  Kandydująca: 1.4.0-1ubuntu1
  Tabela wersji:
 *** 1.4.0-1ubuntu1 0
        500 http://pl.archive.ubuntu.com/ubuntu/ quantal/universe i386 Packages
        100 /var/lib/dpkg/status

3) What you expected to happen

Propably just open thunar.

4) What happened instead

Thunar opened with delay. Not quite shure why it asked me to report.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: thunar 1.4.0-1ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-9.9-generic 3.5.0
Uname: Linux 3.5.0-9-generic i686
ApportVersion: 2.4-0ubuntu6
Architecture: i386
CrashCounter: 1
Date: Sun Aug 12 21:46:28 2012
ExecutablePath: /usr/bin/thunar
InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120626)
ProcCmdline: Thunar --daemon
SegvAnalysis:
 Segfault happened at: 0xb771d5e8: mov (%esi),%eax
 PC (0xb771d5e8) ok
 source "(%esi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: thunar
StacktraceTop:
 ?? ()
 ?? ()
 g_type_create_instance () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_object_newv () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: thunar crashed with SIGSEGV in g_type_create_instance()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin nopasswdlogin 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 #1032340, 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.