Arch Linux

I retract my description: it does not really affects "any" Qt5 application, but I reproduced it by building kwalletmanager-git here.

same here, test with bomi{-git}, ark-frameworks-git, kscreengenie-git, konversation-git, etc....

Try binutils-2.25-5 in [testing]

nope,

test whit ark-frameworks-git. not explode, but freeze in launch (not finish run)

with kscreengenie-git:

#0 0x0000000000416c60 in main ()

kscreengenie[13260]: segfault at 8 ip 00007fac73999bac sp 00007fff1bad8e30 error 4 in libQt5Core.so.5.4.1[7fac736db000+4c2000]

this is with GCC 5.1.0. if back (downgrade) to 4.9 all works again

I have confirmed binutils 2.25-5 fixes the testcase in that bug.

A rebuild of choqok appears to work fine. bomi segfaults although appears nothing to do with the linker.

Andrea: can you test this patch: https://codereview.qt-project.org/#/c/111427

https://bugreports.qt.io/browse/QTBUG-45755

That patch was reverted... try this one: https://codereview.qt-project.org/#/c/111787/

Adding Felix - qt5 maintainer.

Upstream commit 36d6eb721e [1] appears to fix the crash and now bomi starts up fine.

I will push new packages in a bit. We might also want to rebuild packages that use Qt5 and are currently in testing/staging.

[1] http://code.qt.io/cgit/qt/qtbase.git/commit/?id=36d6eb721e7d5997ade75e289d4088dc48678d0d

Should be fixed in qt5 5.4.1-6.

nope for me

ark-frameworks freezes in launch and kscreengenie-git get segfault in same point if build with GCC 5.1.0

restarting the kde, i get this

http://sl1pkn07.wtf/paste/view/0b4cd989

but the programs builded with GCC 5.1.0 still not works (ark-frameworks-git and kscreengenie-git)

back to gcc 4.9.x (and rebuild) works again

@arojas ask me if I use Haswell architecture (ucode related), and no, I use Westmere-EP

greetings

Regarding the kscreengenie-git segfault, try again with libkscreen 5.3.0-3. (5.3.0-1 was built with GCC 5 and Qt5 without the patch.)

nope. same segfault (builded with gcc 5.1.0)

kscreengenie[9876]: segfault at 8 ip 00007fa28a2dcbac sp 00007fffc6548000 error 4 in libQt5Core.so.5.4.1[7fa28a01e000+4c2000]

└───╼ yaourt -Qi libkscreen
Nombre : libkscreen
Versión : 5.3.0-3

Indeed, it's still a problem. I've posted my findings in the upstream bug report:

https://bugreports.qt.io/browse/QTBUG-45755?focusedCommentId=281420&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-281420

qt5 5.4.1-7 is now built with -no-use-gold-linker to work around this issue. Qt5 linked with ld.gold from binutils >= 2.25-5 should work fine as well.

Note that Qt upstream insists that the gold linker fix is not sufficient and Qt applications will need to be built with -fPIC when compiled by GCC 5. I'm not sure how true this is since Fedora also used the -no-use-gold-linker workaround, but I'm not going to argue this point anymore on QTBUG-45755. [1]

As it currently stands, Qt 5.4.2 (and our qt5 >= 5.4.1-6 packages) will automatically use -fPIC in qmake builds. Qt 5.4.2 will also error out if -fPIC is not used (our packages don't have that change backported). Finally Qt 5.4.2 might also add -fPIC to CMake builds if my patch gets accepted upstream. [2]

I would advise keeping GCC 5 in testing until Qt 5.4.2 is out so as to avoid building many Qt packages with GCC 5 until the upstream fix is final.

[1] https://bugreports.qt.io/browse/QTBUG-45755
[2] https://codereview.qt-project.org/#/c/112060/

for me, qt 5.4.1-7 fixes my issues with ark-frameworks-git and kscreengenie-git (only test with this packages for the moment) when build with GCC 5

the segfaults are gone

great work!

greetings