© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
We have two issues, one is a faulty configuration Mixxx knows.
This can be solved by returning to the preferences after the error dialog appears.
A future version may instantly mark the fault fields red that the user is informed before hitting OK.
The other issue are unknown faults that only appear when the config is actually applied. I think we already have a loop returning to the preferences at start up. Maybe we can do similar.
I currently suffer an issue with Pipewire and the Mixxx default using JACK, that Mixxx stalls after pressing OK. I have not yet reported a bug yet, because Pipewire is not official supported with Ubuntu Focal, so it might be my fault. But in any case would is be preferred to have a common timeout solution to cover such issues.