Ubuntu
nautilus package

nautilus crashed with SIGSEGV in g_closure_invoke()

Bug #860792 reported by Mohd Imran Jamadar on 2011-09-27

This bug report is a duplicate of: Bug #795708: nautilus crashed with SIGSEGV in nautilus_window_slot_get_current_uri(). Edit Remove

14

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	nautilus (Ubuntu)	Confirmed	Medium	Unassigned

Bug Description

I had a home folder window open and it crashed after i tried to close it down by using the X window close button.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: nautilus 1:3.2.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
Date: Tue Sep 27 22:09:45 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
ProcCmdline: nautilus -n
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x486534: mov 0xa8(%rdi),%rax
PC (0x00486534) ok
source "0xa8(%rdi)" (0x000000a8) not located in a known VMA region (needed readable region)!
destination "%rax" 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
?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

Mohd Imran Jamadar (imranmohd72) wrote on 2011-09-27:

#1

Dependencies.txt Edit (4.7 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (541 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (76.9 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (795 bytes, text/plain; charset="utf-8")
Registers.txt Edit (614 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (8.8 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (10.6 KiB, text/plain; charset="utf-8")
XsessionErrors.txt Edit (7.3 KiB, text/plain; charset="utf-8")
usr_lib_nautilus.txt Edit (295 bytes, text/plain; charset="utf-8")

visibility:

private → public

Revision history for this message

Apport retracing service (apport) wrote on 2011-09-27:

#2

StacktraceTop:
nautilus_window_slot_get_current_uri (slot=0x0) at nautilus-window-slot.c:646
update_places (sidebar=0xea4080) at nautilus-places-sidebar.c:476
g_closure_invoke (closure=0xe9c3a0, return_value=0x0, n_param_values=1, param_values=0x9da8a0, invocation_hint=<optimized out>) at /build/buildd/glib2.0-2.30.0/./gobject/gclosure.c:774
signal_emit_unlocked_R (node=<optimized out>, detail=0, instance=0xb124c0, emission_return=0x0, instance_and_params=0x9da8a0) at /build/buildd/glib2.0-2.30.0/./gobject/gsignal.c:3272
g_signal_emit_valist (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>, var_args=<optimized out>) at /build/buildd/glib2.0-2.30.0/./gobject/gsignal.c:3003

Revision history for this message

Apport retracing service (apport) wrote on 2011-09-27: Stacktrace.txt

#3

Stacktrace.txt Edit (30.4 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2011-09-27: ThreadStacktrace.txt

#4

ThreadStacktrace.txt Edit (34.7 KiB, text/plain)

Changed in nautilus (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-amd64-retrace

Revision history for this message

Launchpad Janitor (janitor) wrote on 2011-09-27:

#5

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in nautilus (Ubuntu):
status:	New → Confirmed

Revision history for this message

Brian Murray (brian-murray) wrote on 2011-09-29:

#6

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 795708, so it 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.

Report a bug

This report contains Public information

Everyone can see this information.

Duplicate of bug #795708 Remove

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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