Description of problem: qasmixer now (since Monday or Tuesday I think) displays with corrupted images for most gui features; sliders, radio buttons and perhaps others Version-Release number of selected component (if applicable): Mageia supplies qasmixer 0.15-1.mga2. I have also compiled 0.17 of qastools with the same results. Resizing the mixer window causes the corrupted image parts to change and it is sometimes possible to get correct images for, for example, the slider controls. I suspect the cause of the problem may lie in the recently updated Qt4 components, and not in qasmixer itself, but I cannot find a similar issue with any other application currently installed on this computer. How reproducible: permanent feature Steps to Reproduce: 1.Just fire up qasmixer 2.view the mixer controls 3.If they look ok then try resizing the window or moving a control See attached images for examples (using qasmixer 0.17 as it is currently installed - but it looks just like the problem with qasmixer 0.15). If I cannot attach them I can supply them by email - 2 x png @ 32kB each.
Created attachment 1438 [details] control sliders and radio buttons are corrupt
Created attachment 1439 [details] pic shows most sliders are OK and 1 radio button after resize Two attached pictures illustrate what I mean by "corrupt images". When resized to very large, the corruption in the qasmixer control images looks like some of it is text images.
Maybe we should obsolete it by http://sourceforge.net/projects/qastools/ as mentionned on the www ?
CC: (none) => balcaen.john
I'm not sure what you mean. If you mean it should be updated to the current version 0.17 then would agree that would be nice. As the pics above show, however, that will do little to address the corrupt graphics problem. I suspect that as the Qt4 libraries have been updated at least once since I installed qasmixer 0.15 that it is more likely the real problem lies there.
This is quite stunning. Just tried qasmixer after a shed-load of updates tonight and I got this (see attached pic) It is almost beautiful, Whatever is causing it, can we keep it as an option?
Created attachment 1460 [details] Surreal, beautiful perhaps; but wrong
I have had brief access to a Mageia 2 Alpha 3 system cloned from my working system at a time when the QasMixer display was normal. From a very cursory look at the libraries used by this mixer program, the only ones which are obviously related to the drawing of the interface are lib64qtgui4 and lib64qtsvg4. My gut feeling is that it is more likely to be the svg than the gui lib which has introduced the problem. The working version is using Qt 4.7.?? and the artistically advanced, though functionally flawed version is using Qt 4.8.0. Any ideas on how to proceed with this?
Any comment at all would be appreciated, even if it just to shut up and live with it.
Updates tonight from Qt 4.8.0-1mga2 to Qt 4.8.0-2mga2 for all (except lib64qtruby4shared2 for some reason) but no improvement in the svg rendering.
That last comment may have been a little hasty. There has been a change in the way that the rendering problems appear when re-sizing the QasMixer screen. It is much easier to find a size for which the rendering of the controls is acceptable, though this tends to be the case with larger sizes. Radio buttons may still appear scrambled, but control tracks are less likely to disappear when mousing over them.
After several hours of the system being idle while I watched some rugby and washed the car, the QasMixer display behaviour is back to what it was; more often corrupt than not, whatever the size of the display.
Just found this on the QasTools site; Latest news 2012-01-30 QasTools 0.17.1 released Changes: Painting fixed for Qt 4.8 I have just built it on the latest up-to-date Cauldron and it fixes the problem. If QasTools 0.17.1 is packaged for Cauldron instead of QasMixer 0.15, that should do it, I think.
(In reply to comment #12) > Just found this on the QasTools site; > > Latest news 2012-01-30 > QasTools 0.17.1 released > > Changes: > Painting fixed for Qt 4.8 > > I have just built it on the latest up-to-date Cauldron and it fixes the > problem. > > If QasTools 0.17.1 is packaged for Cauldron instead of QasMixer 0.15, that > should do it, I think. added the maintainer. Thanks for the debugging :)
Assignee: bugsquad => pasotti.matteo
Thank you for that. Look forward to the new package. I will presume it is fixed now.
Status: NEW => RESOLVEDResolution: (none) => FIXED
I'm working on the new package (qastools). If needed, I can inform you about the progress using this bug report. Regards
Status: RESOLVED => REOPENEDResolution: FIXED => (none)
qastools 0.17.1 it's now into our repositories (it provides qasmixer, qashctl and qasconfig). Marking this bug as fixed. Regards.
Status: REOPENED => RESOLVEDResolution: (none) => FIXED
I'm very impressed at the turnaround time - well done and thank you