https://bugs.kde.org/show_bug.cgi?id=380219
David Edmundson changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
https://bugs.kde.org/show_bug.cgi?id=380219
--- Comment #12 from David Edmundson ---
https://bugreports.qt.io/browse/QTBUG-61083
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=380219
Marco Martin changed:
What|Removed |Added
CC||notm...@gmail.com
---
https://bugs.kde.org/show_bug.cgi?id=380219
--- Comment #10 from David Edmundson ---
I left a comment on the relevant Qt change asking for some rationale of why
they did this.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=380219
--- Comment #9 from David Edmundson ---
>Qt docs do say "Warning: This function will return 0 if the scene graph has
>not yet been initialized."
That's something different. We're not calling it before a
https://bugs.kde.org/show_bug.cgi?id=380219
Kai Uwe Broulik changed:
What|Removed |Added
CC|
https://bugs.kde.org/show_bug.cgi?id=380219
--- Comment #7 from Andreas Hartmetz ---
Haha, thanks for finding it. That commit does seem dubious in a library that is
supposed to stay binary compatible. If a user really cared, they could check
nullness of the image themselves.
https://bugs.kde.org/show_bug.cgi?id=380219
--- Comment #6 from David Edmundson ---
And knowing that, here's the obvious cause:
commit e6acf80136db9f667d0d4664f6c68065355d6811
Author: Mitch Curtis
Date: Sat May 6 22:32:57 2017 +0200
https://bugs.kde.org/show_bug.cgi?id=380219
David Edmundson changed:
What|Removed |Added
CC|
https://bugs.kde.org/show_bug.cgi?id=380219
--- Comment #4 from Andreas Hartmetz ---
I unsuccefully tried to bisect it in qtdeclarative. The bug does not seem to be
caused or triggered by any change between qtdeclarative v5.9.0-beta4 and
current 5.9, commit
https://bugs.kde.org/show_bug.cgi?id=380219
H.d.V. changed:
What|Removed |Added
CC||josef...@freenet.de
--
You are
https://bugs.kde.org/show_bug.cgi?id=380219
--- Comment #3 from H.d.V. ---
With Qt git head, you have probably mixing 5.9.0 and 5.9.1 Qt libs installed.
(I had the same mistake)
Suggestion: Try rebuild *all* installed dev-qt/*:5 packages.
I have here currently on Gentoo Qt
https://bugs.kde.org/show_bug.cgi?id=380219
Andreas Hartmetz changed:
What|Removed |Added
CC||ahartm...@gmail.com
https://bugs.kde.org/show_bug.cgi?id=380219
--- Comment #1 from Christoph Feck ---
Using Qt 5.9-beta4 here, and do not see a crash. If this is indeed a recent
regression, a git bisect should find the offending commit.
--
You are receiving this mail because:
You are watching all
14 matches
Mail list logo