nautilus crashed with SIGSEGV in g_closure_invoke()

Bug #645772 reported by Victor Costan
This bug report is a duplicate of:  Bug #625696: Nautilus crash when IM preedit. Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: nautilus

I chose "show in file manager" for a photo in Shotwell. Then I selected all the photos in the folder by clicking Ctrl+A. I was going to right-click on the photos to see their size, but nautilus crashed.

At the time, I had the following "drives" attached:
* USB camera (I just transfered pics off it)
* Nexus One (only for charging) through USB hub that's also connected to my keyboard and mouse

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: nautilus 1:2.31.92-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
NonfreeKernelModules: nvidia wl
Architecture: amd64
CrashCounter: 1
Date: Thu Sep 23 01:38:59 2010
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100906)
ProcCmdline: nautilus
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x4e1ed8: mov 0x2e4(%rax),%edi
 PC (0x004e1ed8) ok
 source "0x2e4(%rax)" (0x000002e4) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? ()
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/libgobject-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_closure_invoke()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Victor Costan (costan) 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 Ubuntu better. This particular crash has already been reported and is a duplicate of bug #641234, 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
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.