Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 635024 - x11-misc/sddm - segfaults after gcc-6.x upgrade in libqt5qml.so w/o dev-qt/qtdeclarative rebuild
Summary: x11-misc/sddm - segfaults after gcc-6.x upgrade in libqt5qml.so w/o dev-qt/qt...
Status: RESOLVED DUPLICATE of bug 626070
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: LxQt maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-21 21:08 UTC by Michael Gn. Gajda
Modified: 2017-10-23 11:16 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Gn. Gajda 2017-10-21 21:08:39 UTC 
Basically the same issue as found here: https://forums.gentoo.org/viewtopic-p-8065936.html?sid=30b10dc9cd10a2d1804134eac9ca9ac3

When upgrading from GCC-5.4 to GCC-6.4, I also did a whole world-rebuild. And yet, I encountered the following issue:

When starting sddm, it would crash with a segfault:
sddm-greeter[22721]: segfault at 10 ip 00007f08a9a43baa sp 00007ffd880c4ba0 error 6 in libQt5Qml.so.5.7.1[7f08a98b4000+3d2000]

Recompiling xorg, qtopengl, qtcore and various others did not help. Only after I found this thread I was able to fix it by recompiling qtdeclarative.

Not sure what the cause of this is. But it was really annoying to debug and potentially frustrates users after a GCC upgrade.
Comment 1 Michael Gn. Gajda 2017-10-22 18:35:33 UTC 
What confuses me:

This is my merge history (removed some irrelevant matches):

root@draget-lap /h/draget# genlop -l | grep gcc
     [...]
     Tue Oct 17 13:26:47 2017 >>> sys-devel/gcc-6.4.0
     Fri Oct 20 19:32:04 2017 >>> sys-devel/gcc-6.4.0

root@draget-lap /h/draget# genlop -l | grep sddm
     [...]
     Sun Jan 29 22:28:28 2017 >>> x11-misc/sddm-0.14.0-r2
     Sat Oct 21 08:15:14 2017 >>> x11-misc/sddm-0.14.0-r2
     Sat Oct 21 13:57:00 2017 >>> x11-misc/sddm-0.15.0
     Sat Oct 21 20:30:09 2017 >>> x11-misc/sddm-0.15.0
     Sat Oct 21 21:09:59 2017 >>> x11-misc/sddm-0.15.0
     Sat Oct 21 22:19:55 2017 >>> x11-misc/sddm-0.16.0-r1

root@draget-lap /h/draget# genlop -l | grep qtdeclarat
     [...]
     Sun Jul  9 15:26:33 2017 >>> dev-qt/qtdeclarative-5.7.1
     Fri Oct 20 00:00:39 2017 >>> dev-qt/qtdeclarative-5.7.1
     Fri Oct 20 05:43:19 2017 >>> dev-qt/qtdeclarative-4.8.7
     Sat Oct 21 22:53:10 2017 >>> dev-qt/qtdeclarative-5.7.1


So I upgraded to GCC6.4 on tuesday the 17th. Did some tests and other stuff and decided to switch my GCC profile on thursday evening, where I started to recompile my empty world set.

My machine was working through friday and compiled dev-qt/qtdeclarative-5.7.1 before it recompiled sddm-0.15.0. Why recompiling qtdeclarative again after this fixes the issue, is something I do not really understand.
Comment 2 Michael Palimaka (kensington) gentoo-dev 2017-10-23 11:16:08 UTC 
This should be fixed on 5.7.1-r1

*** This bug has been marked as a duplicate of bug 626070 ***