This seems resolved for now. We're using fPIC, but not -reduce- relocations (-Bsymbolic) on armhf, and with the latest upstream Qt 5.4.2 defaults backported to 5.4.1 everything seems in order, for now at least. This may need to be revisited with Qt 5.5.0 and/or GCC5.
** Description changed: With bug #1403511 taken care of in Qt, apps do not anymore crash with Qt 5.4 and device does not anymore go into reboot loop. However, nothing is visible on the screen. It seems unity8, unity8-dash etc are all running. unity8.log attached - 05/2015 status: - - We require at least -fPIE on arm for QObject::connect to work, but on the other hand -fPIC armhf is broken like described in this bug - - Upstream is moving to require -fPIC while banning -fPIE, which means we should move to -fPIC too and use -reduce-relocations (requires -fPIC from now on) on all archs - Relevant upstream links referring GCC5 as the reason to require -fPIC: http://code.qt.io/cgit/qt/qtbase.git/commit/?id=36d6eb721e7d5997ade75e289d4088dc48678d0d http://code.qt.io/cgit/qt/qtbase.git/commit/?id=3eca75de67b3fd2c890715b30c7899cebc096fe9 ** Changed in: gcc-defaults (Ubuntu) Status: New => Incomplete ** Changed in: binutils (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1403758 Title: Unity8 shows black screen with Qt 5.4.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1403758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
