nautilus crashed with SIGSEGV in g_closure_invoke()

Bug #650431 reported by jan2ary
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

Binary package hint: nautilus

$ lsb_release -rd
Description: Ubuntu maverick (development branch)
Release: 10.10
$ apt-cache policy nautilus
nautilus:
  Installed: 1:2.32.0-0ubuntu1
  Candidate: 1:2.32.0-0ubuntu1
  Version table:
 *** 1:2.32.0-0ubuntu1 0
        500 http://archive.ubuntu.com/ubuntu/ maverick/main amd64 Packages
        100 /var/lib/dpkg/status

the crash has happened when I did umount (click on uparrow near the label of that HDD in Places - left sidepane of nautilus) on external USB HDD

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: nautilus 1:2.32.0-0ubuntu1
Uname: Linux 2.6.36-020636rc5-generic x86_64
Architecture: amd64
Date: Tue Sep 28 19:33:26 2010
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
ProcCmdline: nautilus
ProcEnviron:
 LANGUAGE=en
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x44c5a6: mov (%rax),%r14
 PC (0x0044c5a6) ok
 source "(%rax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%r14" 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 dip lpadmin plugdev sambashare

Revision history for this message
jan2ary (jan2ary) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 g_closure_invoke ()
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist ()
 g_signal_emit () from /usr/lib/libgobject-2.0.so.0

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in nautilus (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you taking the time to report this bug and helping to make Ubuntu better. However, processing the crash report to get detailed information for the developers failed as the retracer did not generate a useful symbolic stack trace.
Please try to obtain a backtrace manually following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

visibility: private → public
Changed in nautilus (Ubuntu):
status: New → Incomplete
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.