| Summary: | GUI rendering bugs with Qt 4.5.1 | ||
|---|---|---|---|
| Product: | [Applications] amarok | Reporter: | Mathias Panzenböck <grosser.meister.morti> |
| Component: | general | Assignee: | Amarok Developers <amarok-bugs-dist> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | normal | CC: | fedora, ingmar, jreznik, rdieter, than |
| Priority: | HI | ||
| Version: | 2.1-SVN | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Attachments: |
bugs in the look of amaroks gui
bugs in the look of amaroks gui with red markings |
||
|
Description
Mathias Panzenböck
2009-04-24 01:49:53 UTC
Created attachment 33046 [details]
bugs in the look of amaroks gui
Created attachment 33047 [details]
bugs in the look of amaroks gui with red markings
Oh, I use: Fedora 10, KDE 4.2.2, Qt 4.5.1, nvidia official drivers 180.44 This is certainly not an Amarok bug, but I'm wondering if Qt 4.5.1 is responsible (unlikely i think). My guess is that it's a system config problem. What configuration could be the problem? I didn't change any configuration. Amarok started to look like that after svn up. I think the Qt update from 4.5.0 to 4.5.1 happened at the same time, but I'm not sure about this. Confirming based on reports from other users. Seems to be a Qt 4.5.1 thing. Question is how we can work around it :) A KDE developer just said this: 09:00 < nixternal> markey: seems they are using KDE 4.2.2 with Qt 4.5.1, which I thought was a no-no 09:01 < nixternal> they should be seeing it in more than just Amarok...I haven't had it in Amarok yet, but I did in Kate, Konqueror, and...can't remember the other So this creates two new questions: 1) Does this happen with KDE trunk as well? You're not meant to use Qt 4.5.1 with KDE 4.2.2. 2) Does it happen in other KDE applications as well? Just found this blog about Qt 4.5.1 with KDE 4.2.2 problems - we're definitely not the only application affected by it: http://rdieter.livejournal.com/13559.html Could this be related to bug #184714 ? Qt 4.5.1 is supposed to be forward- and backward compatible so maybe it's something that never got resolved in the first place? Just to be clear, I'm not trying to make a point here. I'm just thinking out loud. :) Well, we just had a guy from QtSoftware in our #amarok IRC channel. Apparently he looked at the issue, and when he was finished, he said this: 12:47 < darktears> markey: i got it, fixed Unfortunately he left directly after saying that. So I don't know if he meant "fixed it in Qt", or "fixed it in Amarok" :) At any rate, we haven't received a patch yet. If you see the guy on IRC, please ask him what he meant. His hostmask was darktears [n=darktear@kde/developer/menard]. it's a svg rendering regression in qt-4.5.1 and is fixed in qt-copied (In reply to comment #10) > Unfortunately he left directly after saying that. So I don't know if he meant > "fixed it in Qt", or "fixed it in Amarok" :) The former, see below > At any rate, we haven't received a patch yet. If you see the guy on IRC, please > ask him what he meant. His hostmask was darktears > [n=darktear@kde/developer/menard]. http://websvn.kde.org:80/trunk/qt-copy/patches/0279-svg-rendering-regression.diff?view=log Thanks for clearing this up :) Closing the report then. 4.5.1 users should downgrade, or wait for 4.5.2, or use qt-copy from KDE SVN. |