nautilus crashed with SIGABRT in g_assertion_message()

[vlotho]

gilles@gilles-EP31-DS3L:~/Téléchargements/ADM-ASUSTOR$ lsb_release -rd
Description: Ubuntu Utopic Unicorn (development branch)
Release: 14.10
gilles@gilles-EP31-DS3L:~/Téléchargements/ADM-ASUSTOR$ apt-cache policy nautilusnautilus:
  Installé : 1:3.10.1-0ubuntu12
  Candidat : 1:3.10.1-0ubuntu12
 Table de version :
 *** 1:3.10.1-0ubuntu12 0
        500 http://fr.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
        100 /var/lib/dpkg/status

crashed when i have loading files in my own download folder

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: nautilus 1:3.10.1-0ubuntu12
ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0
Uname: Linux 3.15.0-6-generic x86_64
ApportVersion: 2.14.4-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Sun Jul 6 16:42:59 2014
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:

InstallationDate: Installed on 2014-04-05 (91 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326.1)
ProcCmdline: nautilus --new-window
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: nautilus
StacktraceTop:
 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: nautilus crashed with SIGABRT in g_assertion_message()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout 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 #1333606, 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.