Bug#843512: Bug#843511: libqt5widgets5: Some Qt applications segfault on startup

[Alf Gaida]

Control: severity -1 normal
> However, with no additional dependency being added, this means Qt 5.7
> will move to testing before the new lxqt-qtplugin does, breaking every
> LXQt out there -- correct?
May be, but both packages will migrate in the same cycle or a cycle 
later. So it will eventually break some systems - and these systems can 
be repaired a) with purging lxqt-plugins b) waiting c) take 
lxqt-qtplugins from sid for the time being.


We are aware of the possible breaks, but we will find a solution in Qt 
upstream or Qt packaging before the stable release to picking up the 
qt-abi dependency correctly.

Bug#843512: Bug#843511: libqt5widgets5: Some Qt applications segfault on startup

[Dmitry Shachnev]

Hi Ralf,

On Mon, Nov 07, 2016 at 10:55:19AM +0100, Ralf Jung wrote:
> Hi again,
>
> I managed to fix the crashes by re-building lxqt-qtplugin against
> current unstable.  The bug this clearly is in lxqt-plugin, reported as
> #843512.  Still, Qt 5.7 should probably not transition to testing
> without a new version of lxqt-plugin.

Emilio has scheduled a lxqt-plugin rebuild now, so I am closing this bug.

I still hope to be able to refactor the Qt side of this so that platform
plugins do not need to link against the private static library, but this
is not a trivial issue.

See discussions at [1] (LXQt specific) and [2] (Qt in general) for details.

[1]: https://github.com/lxde/lxqt/issues/1082
[2]: http://lists.qt-project.org/pipermail/development/2016-October/027520.html

--
Dmitry Shachnev


signature.asc
Description: PGP signature