twinkle doesn't start (stack smashing detected) (Lubuntu 18.04)

[Dima]

The console output:

$ twinkle
QApplication: invalid style override passed, ignoring it.
Language name: "en"
mprotect failed in ExecutableAllocator::makeExecutable: Permission denied
*** stack smashing detected ***: <unknown> terminated
Aborted (core dumped)
$

I've attached a strace output file.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: twinkle 1:1.10.1+dfsg-3
ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
Uname: Linux 4.15.0-47-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: LXDE
Date: Tue Apr 16 15:29:30 2019
EcryptfsInUse: Yes
InstallationDate: Installed on 2018-06-11 (309 days ago)
InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: twinkle
UpgradeStatus: No upgrade log present (probably fresh install)

[Dima (dima2017)]

And I have /home and /tmp mounted with noexec.

Does anyone know how to find <email address hidden> in "Subscribe someone else"?

[Frédéric Brière (fbriere)]

Hi, Twinkle upstream co-maintainer here. If you could, please open an issue on our GitHub tracker[1], along with a backtrace[2]. (The strace attachment was appreciated, but it didn't really help in this case, unfortunately.) Thanks!

[1] https://github.com/LubosD/twinkle/issues
[2] https://github.com/LubosD/twinkle/wiki/Generating-a-backtrace

[Dima (dima2017)]

https://github.com/LubosD/twinkle/issues/157

[Frédéric Brière (fbriere)]

Thank you very much for the backtrace.

It would appear this is actually a bug within Qt (libqt5qml5 from the looks of it). I managed to find a KDE bug[1] with a similar backtrace, and their conclusion was the same (though they pointed to QtQuick as the culprit). In any case, I have reassigned this bug to qtdeclarative-opensource-src.

In the meantime, could you generate another backtrace, this time after installing the libqt5qml5-dbgsym, libqt5widgets5-dbgsym and libqt5core5a-dbgsym packages? This should provide more information to help the Qt team diagnose this bug.

Thanks, and good luck!

[1] https://bugs.kde.org/show_bug.cgi?id=401686

[Dima (dima2017)]

Thank YOU, tremendous super cosmo-heroes.

[Dima (dima2017)]

The previous gdb was with qt 5.9.5+dfsg-0ubuntu2.1 from ubuntu-security. This one is with qt 5.9.5+dfsg-0ubuntu2.3 from proposed updates.

[Dmitry Shachnev (mitya57)]

Hi Dima!

This looks like https://bugreports.qt.io/browse/QTBUG-58508 to me. According to that bug, it is fixed in Qt 5.11, however the change is too large to backport to 5.9.

Exporting QML_DISABLE_DISK_CACHE=1 should help as a workaround — can you try that?

[Dima (dima2017)]

Yes, this does help. Thank you.

[Dmitry Shachnev (mitya57)]

Thanks for confirming, adjusting the bug status accordingly.