thunar crashed with SIGSEGV in thunar_file_compare_by_name()
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
ProcVersionSign
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-
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, no user)
LANG=en_US.UTF-8
LANGUAGE=en_US
XDG_RUNTIME_
SegvAnalysis:
Segfault happened at: 0x7f8e05663cbe <__strcmp_
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_
?? ()
?? () from /lib/x86_
?? () from /lib/x86_
g_sequence_
Title: thunar crashed with SIGSEGV in thunar_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
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.