thunar crashed with SIGSEGV in g_slice_free1()

Bug #1296335 reported by Thomas Schweikle
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
thunar (Ubuntu)
New
Undecided
Unassigned

Bug Description

After copying to an removable device and removing this device without changing folders before.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: thunar 1.6.3-1ubuntu4
Uname: Linux 3.13.6+ x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CurrentDesktop: XFCE
Date: Sun Mar 23 17:57:29 2014
ExecutablePath: /usr/bin/thunar
InstallationDate: Installed on 2011-10-19 (885 days ago)
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: Thunar --sm-client-id 211ecf712-5fd2-423a-ab79-3255fb2dddca --daemon
SegvAnalysis:
 Segfault happened at: 0x7f2cccf2ebc5: mov 0x8(%rdx),%rax
 PC (0x7f2cccf2ebc5) 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
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
Title: thunar crashed with SIGSEGV in g_slice_free1()
UpgradeStatus: Upgraded to trusty on 2014-02-24 (26 days ago)
UserGroups: adm admin bacula cdrom dialout fax kvm libvirtd lpadmin netdev plugdev pulse pulse-access sambashare users vboxusers

Revision history for this message
Thomas Schweikle (tps) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1203296, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

information type: Private → Public
tags: removed: need-amd64-retrace
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.