nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()

Bug #903237 reported by AnaMaria
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
New
Undecided
Unassigned

Bug Description

Utilizando el Gestor de paquetes Muon y no sé si es un error o un problema de configuraciones. Lo siento

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: nautilus 1:3.2.1-0ubuntu3.1
ProcVersionSignature: Ubuntu 3.0.0-14.23-generic-pae 3.0.9
Uname: Linux 3.0.0-14-generic-pae i686
ApportVersion: 1.23-0ubuntu4
Architecture: i386
CheckboxSubmission: 112a4ad07aa591c00a42c5d6ece3f57a
CheckboxSystem: 331fbefb4b1f6727f4a8261fee7507c9
Date: Mon Dec 12 15:08:59 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
ProcCmdline: nautilus -n
SegvAnalysis:
 Segfault happened at: 0x80cc9a7: mov 0x60(%edx),%eax
 PC (0x080cc9a7) ok
 source "0x60(%edx)" (0x00000060) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? ()
 ?? ()
 g_cclosure_marshal_VOID__VOID () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
UpgradeStatus: Upgraded to oneiric on 2011-10-16 (56 days ago)
UserGroups: adm admin boinc cdrom dialout irc lpadmin mail mysql plugdev sambashare saned shadow ssh ssl-cert staff tty users www-data

Revision history for this message
AnaMaria (analani) 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 #900080, 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-i386-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.