thunar crashed with SIGSEGV in thunar_file_compare_by_name()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
thunar (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I renamed a file.
ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: thunar 1.6.10-1
ProcVersionSign
Uname: Linux 4.2.0-27-generic x86_64
NonfreeKernelMo
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: XFCE
Date: Sat Feb 6 14:15:14 2016
ExecutablePath: /usr/bin/thunar
InstallationDate: Installed on 2014-12-04 (428 days ago)
InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
ProcCmdline: Thunar --sm-client-id 23e51042d-
SegvAnalysis:
Segfault happened at: 0x7fc9fa5c6cbe <__strcmp_
PC (0x7fc9fa5c6cbe) 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: Upgraded to wily on 2016-02-05 (1 days ago)
UserGroups: adm audio cdrom dialout dip fuse lpadmin netdev plugdev sambashare scanner sudo video
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.