We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reported by: foss-4 Date: 2019-05-07T10:03:53Z Status: Fix Released Importance: Critical Launchpad Issue: lp1828019
100% reproducible. crash started around mid end april 2019.
first reported here: https://mixxx.zulipchat.com/#narrow/stream/109171-development/topic/2.2E3.20planning/near/164813816 (has crash log for 30 days)
then confirmed here #2101 (comment) and here https://mixxx.zulipchat.com/#narrow/stream/109171-development/topic/2.2E3.20planning/near/165017109
setting 2.2.2 milestone as per #2101 and confirmed as three independent tester confirmed the issue.
follow-up pr targeted to 2.3.0: #2102
The text was updated successfully, but these errors were encountered:
Issue closed with status Fix Released.
Sorry, something went wrong.
No branches or pull requests
Reported by: foss-4
Date: 2019-05-07T10:03:53Z
Status: Fix Released
Importance: Critical
Launchpad Issue: lp1828019
100% reproducible. crash started around mid end april 2019.
first reported here: https://mixxx.zulipchat.com/#narrow/stream/109171-development/topic/2.2E3.20planning/near/164813816 (has crash log for 30 days)
then confirmed here #2101 (comment) and here https://mixxx.zulipchat.com/#narrow/stream/109171-development/topic/2.2E3.20planning/near/165017109
setting 2.2.2 milestone as per #2101
and confirmed as three independent tester confirmed the issue.
follow-up pr targeted to 2.3.0: #2102
The text was updated successfully, but these errors were encountered: