BETA 14.04 -- thunar crashed with SIGSEGV in g_slice_free1()

Bug #1292054 reported by codeslinger
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
thunar (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

UbuntuStudio 64 bit, 14.04 BETA 1 (Alpha) Feb 24 + Updates

mount and unmount external usb disks several times
and then close thunar

I'm guessing it's trying to free an already freeed resource

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: thunar 1.6.3-1ubuntu3
ProcVersionSignature: Ubuntu 3.13.0-17.37-lowlatency 3.13.6
Uname: Linux 3.13.0-17-lowlatency x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Mar 13 08:10:13 2014
ExecutablePath: /usr/bin/thunar
InstallationDate: Installed on 2014-03-10 (3 days ago)
InstallationMedia: Ubuntu-Studio 14.04 "Trusty Tahr" - Alpha amd64 (20140224)
ProcCmdline: Thunar --sm-client-id 280802b9d-b4a0-4265-a5e7-3d38e255cdad --daemon
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f9d8aa60bc5: mov 0x8(%rdx),%rax
 PC (0x7f9d8aa60bc5) ok
 source "0x8(%rdx)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: thunar
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_slice_free1 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_type_free_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_cclosure_marshal_VOID__OBJECTv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: thunar crashed with SIGSEGV in g_slice_free1()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
codeslinger (codeslinger) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0x00007f9d8aa60bc5 in ?? ()
 No symbol table info available.
 #1 0x0000000000000000 in ?? ()
 No symbol table info available.
StacktraceTop:
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
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
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.