https://bugs.kde.org/show_bug.cgi?id=496057
--- Comment #11 from Fabian Vogt <fab...@ritter-vogt.de> --- (In reply to Andrea Ippolito from comment #10) > (In reply to Fabian Vogt from comment #9) > > (In reply to David S from comment #8) > > > (In reply to Fabian Vogt from comment #4) > > > > It's a regression caused by a qtdeclarative patch which fixes > > > > https://bugs.kde.org/show_bug.cgi?id=494804. > > > > > > > > Solution is to apply > > > > https://codereview.qt-project.org/c/qt/qtdeclarative/+/603331 instead > > > > of the > > > > previous https://codereview.qt-project.org/c/qt/qtdeclarative/+/601299 > > > > > > Just requesting some quick clarification, as there are a lot of reports > > > concerning this issue. Will this fix be pushed automatically in the coming > > > days/weeks or is manual action required to resolve this for everyone > > > affected? Thanks so much > > > > For Tumbleweed it'll be part of the next updates. > > Hi Fabian, I'm exactly on Tumbleweed, did an update this morning to snapshot > 20241113 and can no longer reproduce, which is great. > > I wonder however which package contained the fix - I don't seem to recall > any qt updates, it was really just build numbers bumped, IIRC. > > Could you please point out the package(s) that included the fix? Thanks :) libQt6Qml* -- You are receiving this mail because: You are watching all bug changes.
