sid KDE broken again - locks up when loading iceweasel
Hi, I suspect that something broke for me as a result of this update
process:
[UPGRADE] libqt5gui5:amd64 5.5.1+dfsg-5 -> 5.5.1+dfsg-6
[UPGRADE] libqt5network5:amd64 5.5.1+dfsg-5 -> 5.5.1+dfsg-6
[UPGRADE] libqt5opengl5:amd64 5.5.1+dfsg-5 -> 5.5.1+dfsg-6
[UPGRADE] libqt5printsupport5:amd64 5.5.1+dfsg-5 -> 5.5.1+dfsg-6
[UPGRADE] libqt5sql5:amd64 5.5.1+dfsg-5 -> 5.5.1+dfsg-6
[UPGRADE] libqt5sql5-sqlite:amd64 5.5.1+dfsg-5 -> 5.5.1+dfsg-6
[UPGRADE] libqt5test5:amd64 5.5.1+dfsg-5 -> 5.5.1+dfsg-6
[UPGRADE] libqt5widgets5:amd64 5.5.1+dfsg-5 -> 5.5.1+dfsg-6
[UPGRADE] libqt5xcbqpa5:amd64 5.5.1+dfsg-5 -> 5.5.1+dfsg-6
[UPGRADE] libqt5xml5:amd64 5.5.1+dfsg-5 -> 5.5.1+dfsg-6
the konsole window left open at log-out was not restored, and iceweasel
would consume about 25 seconds of CPU time then the whole KDE session
would lock up save for the graphical arrow cursor.
stopping kdm would result in the following error:
kactivitymanage[3999]: segfault at 7ff6c35c7cd0 ip 000000302bc14291 sp
00007ffc7b321ff8 error 4 in libQt5Sql.so.5.5.1[302bc00000+3f000]
iceweasel still ran fine in xfce
I downgraded the following packages:
Setting up libqt5core5a:amd64 (5.5.1+dfsg-5) ...
Setting up qtbase5-dbg:amd64 (5.5.1+dfsg-5) ...
Setting up libqt5concurrent5:amd64 (5.5.1+dfsg-5) ...
Setting up libqt5dbus5:amd64 (5.5.1+dfsg-5) ...
Setting up libqt5network5:amd64 (5.5.1+dfsg-5) ...
Setting up libqt5sql5:amd64 (5.5.1+dfsg-5) ...
Setting up libqt5sql5-sqlite:amd64 (5.5.1+dfsg-5) ...
Setting up libqt5test5:amd64 (5.5.1+dfsg-5) ...
Setting up libqt5xml5:amd64 (5.5.1+dfsg-5) ...
Setting up libqt5xcbqpa5:amd64 (5.5.1+dfsg-5) ...
Setting up libqt5gui5:amd64 (5.5.1+dfsg-5) ...
Setting up libqt5widgets5:amd64 (5.5.1+dfsg-5) ...
Setting up libqt5opengl5:amd64 (5.5.1+dfsg-5) ...
Setting up libqt5printsupport5:amd64 (5.5.1+dfsg-5) ...
and although konsole sessions would be restored, launching iceweasel
would still result in a lock-up and shutting kdm would still result in a
segfault in libQt5Sql.so.5.5.1.
Any suggestions for tracking this down further welcome.
Arthur.
Reply to: