Ubuntu
nautilus package

nautilus crashed with SIGSEGV in gtk_widget_destroy()

Bug #1054737 reported by Peter Witham on 2012-09-22

This bug report is a duplicate of: Bug #1053862: nautilus crashed due to nested update_node() calls. Edit Remove

16

This bug affects 2 people

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

Bug Description

Fresh install of 12.10 and attempting to login using an existing account on Ubuntu One.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4
Uname: Linux 3.5.0-15-generic x86_64
ApportVersion: 2.5.2-0ubuntu4
Architecture: amd64
Date: Sat Sep 22 15:21:38 2012
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:

ProcCmdline: nautilus -n
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f8f8834795e <gtk_widget_destroy+14>: mov (%rbx),%rdx
PC (0x7f8f8834795e) ok
source "(%rbx)" (0x19000000) not located in a known VMA region (needed readable region)!
destination "%rdx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
gtk_widget_destroy () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
Title: nautilus crashed with SIGSEGV in gtk_widget_destroy()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Tags:

Revision history for this message

Peter Witham (peter-witham) wrote on 2012-09-22:

#1

Dependencies.txt Edit (10.4 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (1.2 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (88.5 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (813 bytes, text/plain; charset="utf-8")
Registers.txt Edit (711 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (3.4 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (6.1 KiB, text/plain; charset="utf-8")
XsessionErrors.txt Edit (73.3 KiB, text/plain; charset="utf-8")
usr_lib_nautilus.txt Edit (269 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2012-09-22:

#2

StacktraceTop:
gtk_widget_destroy (widget=0x19000000) at /build/buildd/gtk+3.0-3.5.18/./gtk/gtkwidget.c:3971
update_node (manager=manager@entry=0x24cfe30, node=0x29bff30, in_popup=<optimized out>, in_popup@entry=0, popup_accels=popup_accels@entry=0) at /build/buildd/gtk+3.0-3.5.18/./gtk/gtkuimanager.c:3115
update_node (manager=manager@entry=0x24cfe30, node=0x2546e30, in_popup=in_popup@entry=0, popup_accels=popup_accels@entry=0) at /build/buildd/gtk+3.0-3.5.18/./gtk/gtkuimanager.c:3096
update_node (manager=manager@entry=0x24cfe30, node=0x2546d30, in_popup=in_popup@entry=0, popup_accels=popup_accels@entry=0) at /build/buildd/gtk+3.0-3.5.18/./gtk/gtkuimanager.c:3096
update_node (manager=manager@entry=0x24cfe30, node=0x253be00, in_popup=in_popup@entry=0, popup_accels=popup_accels@entry=0) at /build/buildd/gtk+3.0-3.5.18/./gtk/gtkuimanager.c:3096

Revision history for this message

Apport retracing service (apport) wrote on 2012-09-22: Stacktrace.txt

#3

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

Revision history for this message

Apport retracing service (apport) wrote on 2012-09-22: StacktraceSource.txt

#4

StacktraceSource.txt Edit (9.4 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2012-09-22: ThreadStacktrace.txt

#5

ThreadStacktrace.txt Edit (16.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 2012-09-24:

#6

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

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

Jean-Baptiste Lallement (jibel) on 2012-10-14

visibility:

private → public

Report a bug

This report contains Public information

Everyone can see this information.

Duplicate of bug #1053862 Remove

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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