nautilus crashed with SIGSEGV in g_slist_insert_sorted_real()

Bug #1282356 reported by Eder Andrés Ávila Niño
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Ocurred when moving and sorting several files within a USB flash memory, specifically dropping selected files onto a just created directory.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: nautilus 1:3.10.1-0ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-10.30-generic 3.13.3
Uname: Linux 3.13.0-10-generic x86_64
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Wed Feb 19 21:08:32 2014
ExecutablePath: /usr/bin/nautilus
GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']"
InstallationDate: Installed on 2014-01-28 (23 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140127.1)
ProcCmdline: nautilus -n
SegvAnalysis:
 Segfault happened at: 0x7ff838568fb7 <g_slice_alloc+167>: mov (%rbx),%rax
 PC (0x7ff838568fb7) ok
 source "(%rbx)" (0x00610d03) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_slice_alloc0 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_type_create_instance () 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_object_newv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_slice_alloc()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo vboxusers

Revision history for this message
Eder Andrés Ávila Niño (ederandresan) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_slist_insert_sorted_real (list=0x1e4ac00, data=0x20, func=0x1e0f610, user_data=0x2) at /build/buildd/glib2.0-2.39.90/./glib/gslist.c:913
 ?? ()
 ?? ()
 g_slist_find_custom (list=0x7ff83858ea09 <g_io_unix_read+41>, data=0x1e48820, func=0x0) at /build/buildd/glib2.0-2.39.90/./glib/gslist.c:746
 g_type_create_instance (type=31754272) at /build/buildd/glib2.0-2.39.90/./gobject/gtype.c:1804

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in nautilus (Ubuntu):
importance: Undecided → Medium
summary: - nautilus crashed with SIGSEGV in g_slice_alloc()
+ nautilus crashed with SIGSEGV in g_slist_insert_sorted_real()
tags: removed: need-amd64-retrace
information type: Private → Public
Revision history for this message
Sebastien Bacher (seb128) wrote :

The bug didn't get activity/new duplicates for some years and the nautilus code saw quite some changes since which probably deprecated the issue so closing it. If it's still a problem in recent Ubuntu/nautilus version please submit a new report

Changed in nautilus (Ubuntu):
status: New → Invalid
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.