nautilus crashed with SIGSEGV in gtk_tree_model_get_valist()

Bug #927787 reported by Cristian Aravena Romero
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
New
Undecided
Unassigned

Bug Description

I'm working with compiz and crash.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: nautilus 1:3.2.1-0ubuntu3.2
ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17
Uname: Linux 3.0.0-16-generic x86_64
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Mon Feb 6 15:32:57 2012
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110531.1)
ProcCmdline: nautilus -n
SegvAnalysis:
 Segfault happened at: 0x7ff47937e0f8 <gtk_tree_model_get_valist+248>: mov 0x30(%rax),%rdx
 PC (0x7ff47937e0f8) 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=0x1a0ce00, iter=0x7fff9d224de0, var_args=0x7fff9d224c78) at /build/buildd/gtk+3.0-3.2.0/./gtk/gtktreemodel.c:1768
 gtk_tree_model_get (tree_model=0x1a0ce00, iter=0x7fff9d224de0) at /build/buildd/gtk+3.0-3.2.0/./gtk/gtktreemodel.c:1730
 ?? ()
 ?? ()
 _gtk_marshal_BOOLEAN__BOXED (closure=0x1a392d0, return_value=0x7fff9d224fc0, n_param_values=<optimized out>, param_values=0x2c3fc60, 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 2011-10-04 (125 days ago)
UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Cristian Aravena Romero (caravena) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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.

visibility: private → public
visibility: private → public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.