nautilus crashed with SIGSEGV in gtk_tree_model_get_valist()

[Martin Schaaf]

I don't know what happened.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: nautilus 1:3.2.1-0ubuntu4.2
ProcVersionSignature: Ubuntu 3.0.0-17.30-generic 3.0.22
Uname: Linux 3.0.0-17-generic x86_64
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
CrashCounter: 1
Date: Tue Apr 17 12:58:51 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: nautilus /media/disk_
ProcEnviron:
 PATH=(custom, user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7ff2963580f8 <gtk_tree_model_get_valist+248>: mov 0x30(%rax),%rdx
 PC (0x7ff2963580f8) ok
 source "0x30(%rax)" (0x00000030) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 gtk_tree_model_get_valist (tree_model=0x1f1a700, iter=0x7fff19cf6a20, var_args=0x7fff19cf68b8) at /build/buildd/gtk+3.0-3.2.0/./gtk/gtktreemodel.c:1768
 gtk_tree_model_get (tree_model=0x1f1a700, iter=0x7fff19cf6a20) at /build/buildd/gtk+3.0-3.2.0/./gtk/gtktreemodel.c:1730
 open_selected_bookmark (sidebar=0x1e28b80, model=0x1f1a700, iter=0x7fff19cf6a20, flags=0) at nautilus-places-sidebar.c:1809
 bookmarks_key_press_event_cb (widget=<optimized out>, event=<optimized out>, sidebar=0x1e28b80) at nautilus-places-sidebar.c:2530
 _gtk_marshal_BOOLEAN__BOXED (closure=0x230af90, return_value=0x7fff19cf6c00, n_param_values=<optimized out>, param_values=0x2066f30, invocation_hint=<optimized out>, marshal_data=<optimized out>) at /build/buildd/gtk+3.0-3.2.0/./gtk/gtkmarshalers.c:85
Title: nautilus crashed with SIGSEGV in gtk_tree_model_get_valist()
UpgradeStatus: Upgraded to oneiric on 2012-01-19 (88 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[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 #830185, 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.