nautilus crashed with SIGABRT in g_option_context_parse()

[Vladimir Scherbaev]

Binary package hint: nautilus

Description: Ubuntu Natty (development branch)
Release: 11.04
nautilus:
  Установлен: 1:2.32.2.1-0ubuntu13
  Кандидат: 1:2.32.2.1-0ubuntu13
  Таблица версий:
 *** 1:2.32.2.1-0ubuntu13 0
        500 http://archive.ubuntu.com/ubuntu/ natty/main i386 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: nautilus 1:2.32.2.1-0ubuntu13
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
CrashCounter: 1
Date: Thu Apr 7 12:52:38 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcCmdline: nautilus
ProcEnviron:
 LANGUAGE=ru_RU:ru:en_GB:en
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: nautilus
StacktraceTop:
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 g_option_context_parse (context=0x8fbf1e8, argc=0xbfd3ed40, argv=0xbfd3ed44, error=0xbfd3ecfc) at /build/buildd/glib2.0-2.28.5/./glib/goption.c:1727
 ?? ()
 __libc_start_main () from /lib/i386-linux-gnu/libc.so.6
 ?? ()
Title: nautilus crashed with SIGABRT in g_option_context_parse()
UpgradeStatus: Upgraded to natty on 2011-04-09 (2 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (<unknown>:1622): dee-WARNING **: Transaction from :1.76 is in the past. Ignoring transaction.
 (<unknown>:1622): dee-WARNING **: Transaction from :1.76 is in the past. Ignoring transaction.
 (<unknown>:1622): dee-WARNING **: Transaction from :1.76 is in the past. Ignoring transaction.
 (<unknown>:1622): dee-WARNING **: Transaction from :1.76 is in the past. Ignoring transaction.

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #752746, 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.