El diumenge, 6 de novembre de 2016, a les 0:59:07 CET, Diederik de Haas va escriure: > On zaterdag 5 november 2016 20:25:32 CET Andrey Rahmatullin wrote: > > > If so, that is/was your problem and you'll likely have various qt5 > > > package > > > at version 5.7.1~20161021+dfsg-N. > > > Downgrade those packages to their version in testing and there's a > > > reasonable chance things start working again. See also > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843208#10 > > The current state is that it's highly likely that a bug in qtdeclarative- > opensource-src (source package) version 5.7.1~20161021-4 is the cause for > the issue various people are seeing. > One of the Debian Qt maintainers filed the following bug for it: > https://bugreports.qt.io/browse/QTBUG-56932 > > In Debian the following bugs have been reported which are likely all caused > by this issue: > https://bugs.debian.org/843250 > https://bugs.debian.org/843332 > > and probably more will follow ... > > > I wonder if rebuilding some packages locally is easier than downgrading a > > lot of packages? If yes, which ones? > > No, that will not help you or anyone else, since the problem is in an > (important) part of qt5 5.7.1 itself. > As you (Andrey) already noticed and reported back, downgrading to the > version in testing works and I think that it is the only solution for now. > Aptitudes resolver should be able to help in downgrading all those > packages. > > HTH, > Diederik
I can confirm that as mentioned in Qt bug report reverting the commit c9ffed92a0dee0ae00a9632177ea42f85ea8a48c and rebuilding qtdeclarative- opensource-src fixed all issues. Have a great day, Josep