Version details: 2.8.1
Distribution/Version: Debian/AMD64 gcc-3.4/4.0

I'm running Debian/AMD64 compiled with gcc-3.4/4.0 I have a chroot with three
bind mounts. One of them causes GSM to crash on startup. I don't know why, but
unmounting this particular one fixes the problem.

Here's the strace output that put me on track:
[pid  1611] stat("/var/chroot/sid-ia32/home", {st_mode=S_IFDIR|S_ISGID|0775,
st_size=4096, ...}) = 0
[pid  1611] --- SIGSEGV (Segmentation fault) @ 0 (0) ---

Here's my fstab:
proc            /proc           proc    defaults        0       0
/dev/hda2       /               ext2    defaults,errors=remount-ro 0       1
/dev/hda5       /home           ext3    defaults        0       2
/dev/hda6       none            swap    sw              0       0
/dev/hdc        /media/cdrom0   iso9660 ro,user,noauto  0       0
/dev/hda1       /c              ntfs    ro,noauto       0       0

# IA32 chroot
/home           /var/chroot/sid-ia32/home       none    bind    0       0
/tmp            /var/chroot/sid-ia32/tmp        none    bind    0       0
proc            /var/chroot/sid-ia32/proc       proc    defaults        0      0
sysfs           /var/chroot/sid-ia32/sys        sysfs   defaults        0      0

And the backtrace:
Program received signal SIGSEGV, Segmentation fault.
0x0000002a97613200 in gnome_vfs_volume_get_icon ()
   from /usr/lib/libgnomevfs-2.so.0
(gdb) bt

+ Trace 56429

I tried three different themes (Simple, Glider and "default") and this is
reproducible with all of them. Someone else corroborated my results on the
Debian-AMD64 mailing list.