[Bug 1403758] Re: Unity8 shows black screen with Qt 5.4.0
the binutils issues is fixed upstream. closing the binutils task. ** Changed in: binutils (Ubuntu) Status: Incomplete => Fix Released -- 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/binutils/+bug/1403758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1403758] Re: Unity8 shows black screen with Qt 5.4.0
** Bug watch added: Sourceware.org Bugzilla #16715 http://sourceware.org/bugzilla/show_bug.cgi?id=16715 ** Also affects: unity8 via http://sourceware.org/bugzilla/show_bug.cgi?id=16715 Importance: Unknown Status: Unknown ** Project changed: unity8 => binutils -- 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/binutils/+bug/1403758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1403758] Re: Unity8 shows black screen with Qt 5.4.0
Just to collect information in this bug, the fPIC requirement and fPIE banning in Qt now is because of this: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65886 This bug originally however is about a problem that shows up when that related Bsymbolic option is enabled on armhf too. This needed forcing but we forced it at one point since it was believed the toolchain bug was fixed. However, for now it remains disabled on non-x86 (the default of Qt upstream) because of the persisting bug, but it may be re-enabled later if the bug is resolved. The toolchain bug (fPIC + Bsymbolic misbehaving on arm) is last described at https://bugreports.qt.io/browse/QTBUG-47350 ** Bug watch added: GCC Bugzilla #65886 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65886 -- 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/binutils/+bug/1403758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1403758] Re: Unity8 shows black screen with Qt 5.4.0
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
[Bug 1403758] Re: Unity8 shows black screen with Qt 5.4.0
Just omitting "-reduce-relocations" doesn't change anything. For reference, http://paste.ubuntu.com/11431050/ lists the changes that I tried first - enabling the four commented out patches, modifying the enable_pie.patch accordingly which is actually also from upstream even though listed as being Ubuntu specific, and adding the gcc5.patch. -- 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
[Bug 1403758] Re: Unity8 shows black screen with Qt 5.4.0
With some more building, it seems compiling qtbase with GCC5 does not help in enabling the upstream (now default in Qt 5.5 & 5.4.2) patches, bringing back the -Bsymbolic for armhf and using the -reduce-relocations option. The symptoms are similar with this qtbase compiled with GCC5. I've saved the compilation at https://launchpad.net/~timo- jyrinki/+archive/ubuntu/qt-reduce-relocations and attaching unity8.log (with "Cannot assign object to list"). ** Attachment added: "unity8.log" https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1403758/+attachment/4406467/+files/unity8.log -- 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
[Bug 1403758] Re: Unity8 shows black screen with Qt 5.4.0
** 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 ** Also affects: gcc-defaults (Ubuntu) Importance: Undecided Status: New -- 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
[Bug 1403758] Re: Unity8 shows black screen with Qt 5.4.0
This still happens on current wily. Using the -reduce-relocations option plus opting to use it on arm (upstream still carries a patch that disables symbolic function binding on non-x86) causes the Unity 8 to just show black screen. ** Also affects: binutils (Ubuntu) Importance: Undecided Status: New -- 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
[Bug 1403758] Re: Unity8 shows black screen with Qt 5.4.0
This bug was fixed in the package qtbase-opensource-src - 5.4.0+dfsg- 4ubuntu2 --- qtbase-opensource-src (5.4.0+dfsg-4ubuntu2) vivid; urgency=medium [ Timo Jyrinki ] * New upstream release. * debian/patches/qimage_conversions.cpp-Fix-little-endian-build.patch: - Fix PowerPC build (LP: #1400244) * Remove patches: - debian/patches/Always-lock-the-DBus-dispatcher-before-dbus_connecti.patch - debian/patches/Don-t-always-chmod-the-XDG_RUNTIME_DIR.patch - debian/patches/Fix-crash-in-QNetworkAccessCacheBackend-closeDownstr.patch - debian/patches/Partially-revert-Fix-a-deadlock-introduced-by-the-ra.patch - debian/patches/QDBusConnection-Merge-the-dispatch-and-the-watch-and.patch - debian/patches/Report-the-system-error-on-why-chmod-2-failed-in-XDG.patch - debian/patches/Reset-QNAM-s-NetworkConfiguration-when-state-changes.patch - debian/patches/Support-dual-sim-in-QtBearer-s-networkmanager-backen.patch - debian/patches/Use-a-property-cache-to-cut-down-on-blocking-calls.patch - debian/patches/dbus_correct_signal_name_disconnect.patch - debian/patches/fix_bug_in_internal_comparison_operator.patch - debian/patches/fix_sparc_atomics.patch - debian/patches/prefer_qpa_for_systemtrayicon.patch - debian/patches/update-QtBearer-NetworkManager-backend-API.patch * Include the networkmanager backend changes from 5.4.1 * Bump ABI version to 5.4.0 * debian/patches/Resolve-GLES3-functions-from-the-shared-lib.patch - Fix usage on OpenGL ES2 platforms (LP: #1403511) * Sync with Debian 5.4.0+dfsg-4 * debian/patches/enable-tests.patch: - Refresh and enable for 5.4.0 (LP: #1403582) - Disable the tests for new QStorageInfo class which partially fail - Disable some widgets tests that fail (desktop only) - Disable one qlogging test * Drop reduce-relocations option from configure, since it causes black screen for Unity8 on armhf because of linking problems. Comment out the related revert of earlier upstream commit. (LP: #1403758) * debian/patches/Add-C++11-if-available-for-QVariant-autotest.patch - Fix tst_qvariant (LP: #1408273) [ Łukasz 'sil2100' Zemczak ] * debian/patches/enable_pie.patch: - Add fix for QObject::connect failing on ARM qtbase-opensource-src (5.4.0+dfsg-4) experimental; urgency=medium * debian/patches/bsd_statfs.diff: Third attempt to fix the build failure on kfreebsd. * Update symbols files for mips. qtbase-opensource-src (5.4.0+dfsg-3) experimental; urgency=medium * More debian/copyright updates. * Do not ship htmlinfo example which contains non-free HTML pages. * Drop remove_icon_from_example.patch and remove_google_adsense.patch, no longer needed with the above change. * Update symbols files with buildds’ logs. * debian/patches/bsd_statfs.diff: Second attempt to fix the build failure. qtbase-opensource-src (5.4.0+dfsg-2) experimental; urgency=medium * Add a patch to fix qstorageinfo_unix.cpp build on kFreeBSD. * Add a patch to fix qimage_conversions.cpp build on big endian systems. * Update symbols files with buildds’ logs. qtbase-opensource-src (5.4.0+dfsg-1) experimental; urgency=medium [ Dmitry Shachnev ] * New upstream release. * Drop fix_bug_in_internal_comparison_operator.patch, applied upstream. * Drop fix_sparc_atomics.patch, applied upstream. * Update .install files. * Bump ABI version to 5.4.0. * Update debian/copyright to reflect LGPLv3 addition. * Update .symbols files for new release. * Bump Standards-Version to 3.9.6, no changes needed. [ Timo Jyrinki ] * Bump ABI also in the lintian overrides. -- Timo JyrinkiFri, 13 Feb 2015 11:38:11 + ** Changed in: qtbase-opensource-src (Ubuntu) Status: Fix Committed => Fix Released -- 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/qtbase-opensource-src/+bug/1403758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1403758] Re: Unity8 shows black screen with Qt 5.4.0
** Changed in: qtbase-opensource-src (Ubuntu) Status: Confirmed => Fix Committed -- 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/qtbase-opensource-src/+bug/1403758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1403758] Re: Unity8 shows black screen with Qt 5.4.0
** Changed in: qtbase-opensource-src (Ubuntu) Status: Fix Committed => Confirmed -- 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/qtbase-opensource-src/+bug/1403758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1403758] Re: Unity8 shows black screen with Qt 5.4.0
** Changed in: unity8 (Ubuntu) Status: In Progress => Fix Released -- 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/qtbase-opensource-src/+bug/1403758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1403758] Re: Unity8 shows black screen with Qt 5.4.0
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New => Invalid -- 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/qtbase-opensource-src/+bug/1403758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1403758] Re: Unity8 shows black screen with Qt 5.4.0
** Branch linked: lp:~kubuntu-packagers/kubuntu-packaging/qtbase- opensource-src -- 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/qtbase-opensource-src/+bug/1403758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1403758] Re: Unity8 shows black screen with Qt 5.4.0
** Changed in: qtbase-opensource-src (Ubuntu) Status: New => Fix Committed -- 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/qtbase-opensource-src/+bug/1403758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1403758] Re: Unity8 shows black screen with Qt 5.4.0
After reverting the patch we have in qtbase that enables Bsymbolic /reduce-relocations for arm, it is back to working. So this needs someone that understands compiler/linker stuff to have a look. If we want to keep that patch in. Or remove the use of reduce- relocations in arm ** Also affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New -- 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/qtbase-opensource-src/+bug/1403758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1403758] Re: Unity8 shows black screen with Qt 5.4.0
** Changed in: unity8 (Ubuntu) Status: New => In Progress ** Changed in: unity8 (Ubuntu) Importance: Undecided => High ** Changed in: unity8 (Ubuntu) Assignee: (unassigned) => Albert Astals Cid (aacid) -- 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/ubuntu-ui-toolkit/+bug/1403758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1403758] Re: Unity8 shows black screen with Qt 5.4.0
Trying to represent the meaningful parts of the rest of the discussion
below.
<+tronical> tsdgeos: in QQmlEnginePrivate::registerBaseTypes can you insert a
qDebug() << "QObject::staticMetaObject is at" <<
&QObject::staticMetaObject; ?
<+tronical> tsdgeos: if we get the wrong address there, then maybe we have a
miscompilation of QtQml somehow
< tsdgeos> tronical: yeah it's wrong there
<+tronical> tsdgeos: ok, that means there's something wrong with libQt5Qml.so
< tsdgeos> removing -O2 didn't help
<+tronical> ok, that dump looks sane though
<+tronical> in particular QObject::staticMetaObject is referenced through a
R_ARM_GOT32 relocation
<+tronical> can you paste the output of objdump -TRDC /path/to/unity8 ?
< tsdgeos> yes
< tsdgeos> tronical: http://paste.ubuntu.com/9570566/
<+tronical> aha!!
<+tronical> this one has indeed a copy relocation to QObject::staticMetaObject,
which it shouldn't have if it's compiled with -fPIE I think
(... -fPIE is in use ...)
<+tronical> tsdgeos: _some_ source code in the unity8 sources references
QObject::staticMetaObject
<+tronical> tsdgeos: in that .o file the reference to QObject::staticMetaObject
should be through the procedure linkage table, but in your case it must be an
absolute reference/relocation, which will cause the linker in turn to create a
so-called copy relocation for unity8 as binary. I think it shouldn't have that
< tsdgeos> builddir/tests/mocks/Unity/Indicators/moc_sharedunitymenumodel.cpp:
{ &QObject::staticMetaObject, qt_meta_stringdata_SharedUnityMenuModel.data,
<+tronical> oh, that's just a test
<+tronical> still, ok, suppose it were valid, then the other question is why
when loading the plugin that has QSortFilterProxyModelQML the reference to
QObject::staticMetaObject isn't changed to point to the copy relocation
<+tronical> tsdgeos: could you try running your app with
LD_DEBUG=bindings,symbols and collect the output? it's going to be a lot, so
you could email it if it's too big for a paste
< tsdgeos> sent
<+tronical> tsdgeos: the ld output looks ok but I don't understand yet why the
one file that has the QSortFilterProxyModelQML isn't relocated correctly
<+tronical> tsdgeos: that comes from libunity8-private.so, right?
<+tronical> tsdgeos: I have to leave. let's look at this early next year :)
--
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/ubuntu-ui-toolkit/+bug/1403758/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1403758] Re: Unity8 shows black screen with Qt 5.4.0
Second bug (i.e. not starting in the desktop) should be fixed by https://code.launchpad.net/~aacid/unity8/unitySortFilterProxyQML/+merge/245198 First bug still under investigation as Timo reports ↑↑ ** Branch linked: lp:~aacid/unity8/unitySortFilterProxyQML -- 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/ubuntu-ui-toolkit/+bug/1403758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1403758] Re: Unity8 shows black screen with Qt 5.4.0
Long discussions about #qt-labs, mostly between tsdgeos and tronical, about various things. Summarizing: * <+tronical> tsdgeos: so I think something is wrong with the unit8 binary, my _guess_ is that it isn't built with -fPIC -> it is built with -fPIC (and -fPIE, also asked about, "ok, that looks good") * <+tronical> oh wait, there used to be a gcc ARM bug with copy relocations that affected this <+tronical> tsdgeos: could it be that qtbase 5.3 was built with -reduce-relocations and now it isn't anymore? -> no, both 5.3 and 5.4 built _with_ -reduce-relocations * binutils has had bugs, Ubuntu has the version with fixes * -Bsymbolic-functions is system wide default in Ubuntu -> "well, it explains where that comes from. it doesn't explain why the relocation in unit8 resolved to the wrong address" * <+tronical> peppe, Mirv, tsdgeos: I realize that this is unrelated to -Bsymbolic-functions because this isn't about functions but a global symbol/variable * <+tronical> peppe, Mirv, tsdgeos: this particular problem is new and different. QObject::staticMetaObject is a global symbol and here it resolves to two different addresses * <+tronical> tsdgeos: still there? I have an idea how we may be able to find out where that bad pointer is coming from (it may not necessarily by the unity8 binary) ...to be continued. -- 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/ubuntu-ui-toolkit/+bug/1403758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1403758] Re: Unity8 shows black screen with Qt 5.4.0
So second bug is https://bugreports.qt-project.org/browse/QTBUG-43463 but tbh I can see them marking this just as a won't fix. -- 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/ubuntu-ui-toolkit/+bug/1403758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1403758] Re: Unity8 shows black screen with Qt 5.4.0
Oh, the SDK has a QSortFilterProxyModelQML too? Now I see why are we getting this error now, we have one in Unity8 too and that's why it is getting confused. It is a regression against Qt 5.3 but i'm not sure it's totally QMLs fault to be honest :D -- 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/ubuntu-ui-toolkit/+bug/1403758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1403758] Re: Unity8 shows black screen with Qt 5.4.0
Checking how the type is exported - and all related types to that one - I see a potential bug in UITK. The way is exported to 1.1 version is wrong: qmlRegisterType(uri, 1, 1, "SortFilterModel"); And it should be qmlRegisterType(uri, 1, 1, "SortFilterModel") More, as the type is supposed to be used only with version 1.1 and above, all properties/slots/signals would need to be revisioned correctly. -- 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/ubuntu-ui-toolkit/+bug/1403758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1403758] Re: Unity8 shows black screen with Qt 5.4.0
** Also affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New -- 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/ubuntu-ui-toolkit/+bug/1403758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1403758] Re: Unity8 shows black screen with Qt 5.4.0
I've been investigating this today and there's at leat two separate
issues:
**Only** on the phone you get the log Timo attaches (or something along
the lines). That is caused by QQmlPropertyValidator::canCoerce failing.
I've talked to Simon Haussmann from Qt Company and the situation we have
(two QQmlPropertyCache with different pointer but same QMetaObject
pointer) is technically impossible, yet we're having it, if o change
that function to do
while (fromMo && toMo) {
if (fromMo->metaObject() && toMo->metaObject() &&
fromMo->metaObject()->className() == toMo->metaObject()->className())
return true;
fromMo = fromMo->parent();
}
instead of the original loop comparing toMo and fromMo i can workaround
the bug (but this is just a hacky) and get to the next bug
On the desktop (or on the phone after workarounding the first issue), you will
get errors saying
"Unable to assign QSortFilterProxyModelQML to QSortFilterProxyModelQML"
These errors seem to be caused somehow by Ubuntu.Components since if i
un-import it, they go away. You can also workaround them by changing the code
from
property SortFilterProxyModel categories: categoryFilter
to
property var categories: categoryFilter
Which you could even argue it's better code in some cases, but still we
need to investigate why it's happening.
In summary, there's two bugs:
Bug #1 only happen on the phone (probably because of ARM)
Bug #2 is triggered by importing Ubuntu.Components
Both need investigation. I'll continue tomorrow if noone beats me to it
:D
--
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/unity8/+bug/1403758/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
