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
Titl
** 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 thi
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 forci
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:
Wit
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 U
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
** 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:
+ -
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
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
** 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 manag
** 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 manag
** 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 notification
** 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
** 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 notif
** 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 noti
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: qt
** 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,
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
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
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
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 sho
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 y
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
** 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 manag
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
25 matches
Mail list logo
