Ubuntu
nautilus package

nautilus crashed with SIGSEGV in g_type_check_instance_is_a()

Bug #712155 reported by UndiFineD on 2011-02-02

10

This bug affects 1 person

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

Bug Description

Binary package hint: nautilus

crashed on update

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: nautilus 1:2.32.0-0ubuntu1.3
ProcVersionSignature: Ubuntu 2.6.35-25.44-generic-pae 2.6.35.10
Uname: Linux 2.6.35-25-generic-pae i686
Architecture: i386
Date: Wed Feb 2 20:39:17 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
ProcCmdline: nautilus --sm-client-id 10b2ec9a4e91bb7b1b128369828447786700000069330057 --sm-client-state-file /home/keimpe/.config/session-state/nautilus-1295795473.desktop
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x3af240 <g_type_check_instance_is_a+128>: testb $0x4,0xe(%edx)
PC (0x003af240) ok
source "$0x4" ok
destination "0xe(%edx)" (0x00000532) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
g_type_check_instance_is_a () from /usr/lib/libgobject-2.0.so.0
?? () from /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so
g_cclosure_marshal_VOID__PARAM () from /usr/lib/libgobject-2.0.so.0
g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
?? () from /usr/lib/libgobject-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_type_check_instance_is_a()
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse libvirtd lpadmin netdev plugdev sambashare tape video

Tags:

Revision history for this message

UndiFineD (k.dejong) wrote on 2011-02-02:

#1

Dependencies.txt Edit (5.2 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (1.2 KiB, text/plain; charset="utf-8")
GConfNonDefault.txt Edit (486 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (78.7 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (814 bytes, text/plain; charset="utf-8")
Registers.txt Edit (491 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (7.7 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (10.6 KiB, text/plain; charset="utf-8")
XsessionErrors.txt Edit (10.7 KiB, text/plain; charset="utf-8")
usr_lib_nautilus.txt Edit (591 bytes, text/plain; charset="utf-8")

Revision history for this message

UndiFineD (k.dejong) wrote on 2011-02-02:

#2

dpkg.log Edit (87.0 KiB, text/plain)

installation log

visibility:

private → public

Revision history for this message

Apport retracing service (apport) wrote on 2011-02-02:

#3

StacktraceTop:
check_value_table_I (type_name=0x526 <Address 0x526 out of bounds>,
g_signal_nodes () from /usr/lib/libgobject-2.0.so.0
?? ()

Revision history for this message

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

#4

Stacktrace.txt Edit (316 bytes, text/plain)

Revision history for this message

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

#5

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

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

Revision history for this message

Pedro Villavicencio (pedro) wrote on 2011-09-08:

#6

Thank you for taking the time to report this bug and helping to make Ubuntu better. Is the issue reproducible with Nautilus 3.1.90 or newer? There's no recent comments on this report indicating that, could you please test and comment back?. Thanks again and we appreciate your help.

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

Revision history for this message

UndiFineD (k.dejong) wrote on 2011-09-09:

#7

updated today, seem to be in order now
nautilus 3.1.90

Fabio Marconi (fabiomarconi) on 2011-10-27

Changed in nautilus (Ubuntu):
status:	Incomplete → Fix Released

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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