qtractor crashed with SIGSEGV in __GI___pthread_mutex_lock()

[Joe Linux]

Same story than yesterday when Adding DSSI plugin (installed by défault) -> Qtractor crash but now with a fresh install of Ubuntu Studio 17.10 on my internal HDD.
Qtractor still unusable!

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: qtractor 0.8.3-1
ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
Uname: Linux 4.13.0-16-lowlatency x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: XFCE
Date: Sat Oct 21 20:01:13 2017
ExecutablePath: /usr/bin/qtractor
InstallationDate: Installed on 2017-10-21 (0 days ago)
InstallationMedia: Ubuntu-Studio 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
ProcCmdline: /usr/bin/qtractor
ProcEnviron:
 LANGUAGE=fr_FR
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f2a8fb2c120 <__GI___pthread_mutex_lock>: mov 0x10(%rdi),%edx
 PC (0x7f2a8fb2c120) ok
 source "0x10(%rdi)" (0x20000084f) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: qtractor
StacktraceTop:
 __GI___pthread_mutex_lock (mutex=0x20000083f) at ../nptl/pthread_mutex_lock.c:67
 g_static_rec_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 fluid_settings_setnum () from /usr/lib/x86_64-linux-gnu/libfluidsynth.so.1
 ?? () from /usr/lib/dssi/fluidsynth-dssi.so
 ?? ()
Title: qtractor crashed with SIGSEGV in __GI___pthread_mutex_lock()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

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 #1725504, 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.