thunar crashed with SIGSEGV in thunar_file_compare_by_name()

Bug #1501454 reported by wilbur.harvey
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
thunar (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I was renaming a file, this has happened multiple times.
In this case, the file was very large.

ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: thunar 1.6.10-1
ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1
Uname: Linux 4.2.0-12-generic x86_64
ApportVersion: 2.19-0ubuntu1
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Sep 30 11:32:31 2015
ExecutablePath: /usr/bin/thunar
InstallationDate: Installed on 2014-06-11 (476 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64+mac (20140417)
ProcCmdline: Thunar --sm-client-id 24bc44573-f514-42b3-bf8a-03697ff684f4 --daemon
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 LANGUAGE=en_US
 XDG_RUNTIME_DIR=<set>
SegvAnalysis:
 Segfault happened at: 0x7f8e05663cbe <__strcmp_sse2_unaligned+30>: movdqu (%rsi),%xmm0
 PC (0x7f8e05663cbe) ok
 source "(%rsi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%xmm0" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: thunar
StacktraceTop:
 thunar_file_compare_by_name ()
 ?? ()
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_sequence_insert_sorted_iter () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: thunar crashed with SIGSEGV in thunar_file_compare_by_name()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

Revision history for this message
wilbur.harvey (wilbur-harvey) 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 #1495409, 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
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.