thunar crashed with SIGSEGV in thunar_file_compare_by_name()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
thunar (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Crash on renaming file:
haproxy.
File copied in to new file-name, but old version not deleted
ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: thunar 1.6.10-1
ProcVersionSign
Uname: Linux 4.2.0-16-generic x86_64
ApportVersion: 2.19.1-0ubuntu2
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Oct 20 14:24:01 2015
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/thunar
InstallationDate: Installed on 2015-10-15 (4 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
ProcCmdline: Thunar --sm-client-id 2486813e3-
SegvAnalysis:
Segfault happened at: 0x7f385b632cbe <__strcmp_
PC (0x7f385b632cbe) 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
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.