https://bugs.kde.org/show_bug.cgi?id=425188
--- Comment #9 from Albert Astals Cid <aa...@kde.org> --- (In reply to David Hurka from comment #8) > Another idea: Can this be an issue of broken ABI? Like when Qt Widgets was > compiled against a different minor release of Qt Gui than our users are > using, and Qt Gui broke their ABI in this minor release. So that something > in Qt Widgets reads from a Qt Gui object with a slight address offset, so it > gets this weird enum value instead of the correct pointer? Given how much people have this QScroller crash, doesn't seem reasonable to me ot to expect they all have broken systems. -- You are receiving this mail because: You are the assignee for the bug.
