thunar crashed with SIGSEGV in magazine_chain_pop_head()

Bug #1269344 reported by Sergio Benjamim
32
This bug affects 5 people
Affects Status Importance Assigned to Milestone
thunar (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Just try to open Thunar, and got this error.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: thunar 1.6.3-1ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7
Uname: Linux 3.13.0-2-generic x86_64
ApportVersion: 2.13.1-0ubuntu1
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Jan 15 12:46:44 2014
ExecutablePath: /usr/bin/thunar
InstallationDate: Installed on 2014-01-09 (5 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140109)
ProcCmdline: Thunar --daemon
ProcEnviron:
 LANGUAGE=fr_FR
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fe9df08e017 <g_slice_alloc+167>: mov (%rbx),%rax
 PC (0x7fe9df08e017) ok
 source "(%rbx)" (0x6469732d77656976) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: thunar
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: thunar crashed with SIGSEGV in g_slice_alloc()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Sergio Benjamim (sergio-br2) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 magazine_chain_pop_head (magazine_chunks=0x7fe9e333bf50) at /build/buildd/glib2.0-2.39.2/./glib/gslice.c:543
 thread_memory_magazine1_alloc (tmem=<optimized out>, ix=11) at /build/buildd/glib2.0-2.39.2/./glib/gslice.c:846
 g_slice_alloc (mem_size=mem_size@entry=184) at /build/buildd/glib2.0-2.39.2/./glib/gslice.c:1005
 g_slice_alloc0 (mem_size=mem_size@entry=184) at /build/buildd/glib2.0-2.39.2/./glib/gslice.c:1040
 g_type_create_instance (type=<optimized out>) at /build/buildd/glib2.0-2.39.2/./gobject/gtype.c:1850

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 thunar (Ubuntu):
importance: Undecided → Medium
summary: - thunar crashed with SIGSEGV in g_slice_alloc()
+ thunar crashed with SIGSEGV in magazine_chain_pop_head()
tags: removed: need-amd64-retrace
Revision history for this message
Daniel Letzeisen (dtl131) wrote :

I cannot reproduce in my Xubuntu Trusty VM with fully updated as of 1600 GMT today.

information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in thunar (Ubuntu):
status: New → Confirmed
tags: added: vivid
Revision history for this message
Sean Davis (bluesabre) wrote :

Seems likely to be a one-off crash. Closing this issue out.

Changed in thunar (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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