nautilus crashed with SIGSEGV

Bug #1434491 reported by Francescodario Cuzzocrea on 2015-03-20
26
This bug affects 3 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Medium
Unassigned

Bug Description

this error happened after I have disconnected my usb pendrive

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: nautilus 1:3.14.2-0ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
Uname: Linux 3.19.0-9-generic x86_64
ApportVersion: 2.16.2-0ubuntu3
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Fri Mar 20 11:08:53 2015
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-precise-amd64-20130203-1
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:

InstallationDate: Installed on 2015-03-12 (7 days ago)
InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50
ProcCmdline: nautilus -n
ProcEnviron:
 LANGUAGE=it
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f1d26ebeb43: mov 0x30(%rbx),%rdi
 PC (0x7f1d26ebeb43) ok
 source "0x30(%rbx)" (0x00000030) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: nautilus crashed with SIGSEGV
UpgradeStatus: Upgraded to vivid on 2015-03-12 (7 days ago)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

information type: Private → Public

StacktraceTop:
 free_node (node=0x1757a40) at /build/buildd/gtk+3.0-3.14.9/./gtk/deprecated/gtkuimanager.c:1402
 g_node_traverse_post_order (node=0x1757a40, flags=flags@entry=G_TRAVERSE_ALL, func=func@entry=0x7f1d26ebeb30 <free_node+80>, data=data@entry=0x0) at /build/buildd/glib2.0-2.43.92/./glib/gnode.c:617
 g_node_traverse_post_order (node=0x150a040, flags=flags@entry=G_TRAVERSE_ALL, func=func@entry=0x7f1d26ebeb30 <free_node+80>, data=data@entry=0x0) at /build/buildd/glib2.0-2.43.92/./glib/gnode.c:607
 g_node_traverse_post_order (node=0x1509ca0, flags=flags@entry=G_TRAVERSE_ALL, func=func@entry=0x7f1d26ebeb30 <free_node+80>, data=data@entry=0x0) at /build/buildd/glib2.0-2.43.92/./glib/gnode.c:607
 g_node_traverse_post_order (node=0x1450150, flags=flags@entry=G_TRAVERSE_ALL, func=func@entry=0x7f1d26ebeb30 <free_node+80>, data=data@entry=0x0) at /build/buildd/glib2.0-2.43.92/./glib/gnode.c:607

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

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

Changed in nautilus (Ubuntu):
status: New → Confirmed
George Prowse (torqueing) wrote :

It also happens when just closing nautilus at times

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers