Description of problem:Mixxx 2.2.0 doesn't work correctly. There is a bug reported on a graphical error that has to do with qt5, but in mixxx 2.2.1 it does not reproduce. The mixxx package should be updated to its latest version. Here the reported bug: https://bugs.launchpad.net/mixxx/+bug/1811350 Version-Release number of selected component (if applicable): Mageia 7 - Mixx 2.2.0 How reproducible: Install mixxx 2.2.0 and work whit it. It can see a graphic bug in the preview column. Steps to Reproduce: 1. Install the application mixxx from the repositories. 2. Run Mixxx and view the preview column. 3. See the graphic bug in the column, constant blinks.
Assigning to the registered maintainer!
Assignee: bugsquad => lists.jjorgeCC: (none) => geiger.david68210
I have pushed mixxx 2.2.1 to updates_testing, please ensure the bug is gone so that we move it to release.
Status: NEW => ASSIGNED
I don't see the package mixxx 2.2.1 in testing and I have activated all testing packages
(In reply to Jose Lp from comment #3) > I don't see the package mixxx 2.2.1 in testing and I have activated all > testing packages It took 4 hours to build, so it maybe was not in the mirrors when you tried? Now it is. I do this to ensure testing media is updated, and then install only audacity : urpmi.update '' urpmi --searchmedia testing audacity
I installed mixxx 2.2.1 from testing repositories. I can confirm that in mixxx 2.2.1 don't appears this bug, so that you can move this package to release repositories. I think that we can close this bug for Mageia 7. Regards!!
(In reply to Jose Manuel López Díaz from comment #5) > I can confirm that in mixxx 2.2.1 don't appears this bug, so that you can > move this package to release repositories. Thanks for testing. > I think that we can close this bug for Mageia 7. Not yet : this will have to be an update, as it is too late to go into release. So keeping it open to go through QA.
CC: (none) => lists.jjorgeAssignee: lists.jjorge => qa-bugs
To QA : this is to push when MGA7 is released. Already tested by end user.
updates_testing will be wiped, so it'll have to be rebuilt and re-tested.
Source RPM: Mixxx => mixxx
Mageia 7 final release comes with version 2.20. What are the plans to upgrade to version 2.2.1?
Suggested Advisory : Mixxx 2.2.0 has several graphical bugs, upstream has released 2.2.1 to fix them. Ref : https://bugs.launchpad.net/mixxx/+bug/1811350 Only one RPM and SRPM : mixxx-2.2.1-1.mga7
eehh?? I am not understand.
(In reply to Jose Manuel López Díaz from comment #11) > eehh?? I am not understand. SOrry, I should have explained : you tested 2.2.1 version from cauldron just when Mageia 7 was being released. As David explained in comment 8, it was too late to include it in Mageia 7. So we have to do now a proper release of 2.2.1 as as update. You can test it, and report here the test result with arch details, just to ensure this new rebuild has no new problems. We have a Quality Assurance team that ensures we don't break production systems when pushing updates : http://madb.mageia.org/tools/updates
(In reply to José Jorge from comment #12) > (In reply to Jose Manuel López Díaz from comment #11) > > eehh?? I am not understand. > > SOrry, I should have explained : you tested 2.2.1 version from cauldron just > when Mageia 7 was being released. As David explained in comment 8, it was > too late to include it in Mageia 7. So we have to do now a proper release of > 2.2.1 as as update. > > You can test it, and report here the test result with arch details, just to > ensure this new rebuild has no new problems. We have a Quality Assurance > team that ensures we don't break production systems when pushing updates : > http://madb.mageia.org/tools/updates But how can I prove it? Where is the rpm? Is it included in any testing repository? Thanks
(In reply to Jose Manuel López Díaz from comment #13) > But how can I prove it? You don't have to. We trust our users ;-) > Where is the rpm? > Is it included in any testing repository? Yes, until the update is validated, you have to update the testing medias, then install from them : urpmi.update '' urpmi --searchmedia testing mixxx
MGA7-32 on IBM Thinkpad R50e No installation issues. Starting mixxx from CLI gives 2 screens full of warnings, but the mix panel comes up OK. I can select a wav file and it plays correctly, and the panel all looks normal to me. OK for me.
CC: (none) => herman.viaeneWhiteboard: (none) => MGA7-32-OK
After the installation was successful, I tested with a session of about 1 hour. All without problems, no graphic bugs, the tracks load well, the interface has no errors, no sound errors. Ok for me.
*** Bug 24928 has been marked as a duplicate of this bug. ***
CC: (none) => chitty_cloud
(In reply to Jose Manuel López Díaz from comment #16) > After the installation was successful, I tested with a session of about 1 > hour. All without problems, no graphic bugs, the tracks load well, the > interface has no errors, no sound errors. Ok for me. I also tested with i586 Intel Classmate, all ok. Jose, is your mixxx 64 bit version?
Sorry, yes, My mixxx is 64 bit version. I tried it in Mageia 7 Plasma 64 Bits.
Whiteboard: MGA7-32-OK => MGA7-32-OK MGA7-64-OK
Advisory uploaded, validating.
Keywords: (none) => advisory, validated_updateCC: (none) => sysadmin-bugs
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2019-0049.html
Resolution: (none) => FIXEDStatus: ASSIGNED => RESOLVED