nautilus crashed with SIGSEGV in g_closure_invoke()

Bug #1032312 reported by Taylor "Ripps" LeMasurier-Wren
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
New
Undecided
Unassigned

Bug Description

Can't even start nautilus now in Quantal, just get this when I try to launch it.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: nautilus 1:3.5.4-0ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-6.6-generic 3.5.0
Uname: Linux 3.5.0-6-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.4-0ubuntu6
Architecture: amd64
Date: Thu Aug 2 12:44:01 2012
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: /usr/bin/nautilus --no-desktop
SegvAnalysis:
 Segfault happened at: 0x4523b4: mov (%rax),%rdi
 PC (0x004523b4) ok
 source "(%rax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to quantal on 2012-01-05 (210 days ago)
UserGroups: adm admin audio cdrom dialout kvm libvirtd lpadmin mythtv plugdev sambashare vboxusers video

Revision history for this message
Taylor "Ripps" LeMasurier-Wren (ripps818) 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 #1032303, 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
tags: removed: need-amd64-retrace
Revision history for this message
Silas Arn (silas89) wrote :

A reboot solved the error with me.

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.