Bug#897150: mixxx: Segmentation Fault

[Matteo F. Vescovi]

Hi!

On Wed, May 9, 2018 at 3:02 PM, Bernhard Übelacker
<bernhardu at mailbox.org> wrote:
> On Sat, 28 Apr 2018 23:25:07 -0500 Casey C <ppcutopia.caseyac at gmail.com>
> wrote:
>
>> -- System Information:
>> Debian Release: buster/sid
>>   APT prefers xenial-updates
>>   APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 'xenial'), (500, 'unstable')
>> Architecture: powerpc (ppc64)
>
> Hello Casey C,
> out of curiosity I tried to reproduce this crash in a QEMU PowerPC VM.
>
> But in a ppc64el installation of Debian buster I could not reproduce
> this crash. (Which also identifies as "Architecture: ppc64el (ppc64le)")
> So probably I tried the wrong architecture.
>
>
> But I have trouble to find a way to install a current Debian powerpc
> installation.
> Also the xenial entries point to some Ubuntu sources?
>
> Therefore you probably can give some more information about how this
> system got installed and where the packages come from.
>
> Also in [1] are some hints how to add the debug symbols if the sources
> you installed Mixxx from support the automatic debug packages.
> And start Mixxx once in a debugger to get a meaningful backtrace of the
> crash that can be added to this report.
>
>
> One other thing to try would be to move your old .mixxx directory to
> start with a clean configuration.
> e.g.: mv ~/.mixxx ~/old.mixxx

I've started working on a fix for this some days ago (given that
probably a new release could add Qt 5.10 support) but faced the fact
that the new upstream release v2.1.0 is FTBFS for some reason and
haven't got time to triage that more.
If interested, see [1].

Cheers.


[1] https://bugs.launchpad.net/mixxx/+bug/1768148

-- 
Matteo F. Vescovi || Debian Developer
GnuPG KeyID: 4096R/0x8062398983B2CF7A