...one more reason to not revert the migration from Qt4 to Qt5 in 2.2.0.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804513
Title:
Cosmic: Mixxx 2.1.3 is not stable with Qt5
To manage notificat
Fedora used the default build settings which defaults to speex for
resampling although libsamplerate would be available.
PR: https://src.fedoraproject.org/rpms/rubberband/pull-request/1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Version 2.2.4 was tagged much earlier but then not released officially
due to internal build server issues. Nothing to worry about.
The issue might depend on the exact Qt version, the build settings used
by Arch, and how Mixxx is started (i.e. with "-platform xcb" on
Wayland?). I have never experi
PKGBUILD: Why is Mixxx built with "perftools=1 perftools_profiler=1"? We
don't use those options neither for CI builds nor for release builds.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789059
Tit
https://github.com/mixxxdj/mixxx/blob/dc1b9a1e64ac48e9b926e2afd452a6651a20081d/build/features.py#L495
I have never used it myself and am unsure about the consequences or
side-effects. In the best case it results in a minor performance
regression.
Using a local build with debug infos would hopeful
tcmalloc could even be faster than the system allocator. But as already
mentioned this is not used in any of the official builds.
Please first do a local build with the original Arch settings and try to
reproduce the deadlock with a full stacktrace. Then rebuild without
these options.
--
You rec
Since this deadlock is probably not related to the original issue that
has already been fixed we should create a new issue. Otherwise tracking
becomes difficult.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
The hang on exit while closing the sound devices is unrelated. Probably
not a deadlock, only a slow I/O operation and hardware interaction. Hard
to trace without the actual device setup at hand.
Now we know that the deadlock is originating from WOverview.
Do you still experience any deadlocks aft
Why not simply increasing the minimum required version from 1.8.0 to
2.0.0?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1577042
Title:
SIGSEGV in SoundTouch 1.9.2
To manage notifications about th
Marked as 'Invalid', because CachingReader has been fixed in 2.1 with
the introduction of the new SoundSource API. Should be fixed now.
** Changed in: mixxx
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
10 matches
Mail list logo