https://bugs.kde.org/show_bug.cgi?id=487895
--- Comment #52 from TraceyC <[email protected]> --- (In reply to Deinorius from comment #51) > Just wanted to ask if you might need any additional information for > resolving this issue. > > Btw. I'm confused about the status "resolved upstream". Does this just mean, > that this bug was moved to Qt upstream? Because it's not resolved there. I understand how the "resolved" status can be confusing. The status of the bug, as you mention, is that it's still open in the Qt tracker. What the resolved status in the KDE tracker means is that for KDE, this report is resolved. The problem lies upstream with Qt, and needs to be worked on and fixed by the Qt folks. There's nothing more KDE needs for this at this point. Please follow the Qt report for updates. -- You are receiving this mail because: You are watching all bug changes.
