The general problem is that the new kernel comes back at each upgrade of
the ubuntu kernel, and a custom one needs installation for each. But yes
bug #1630906 is still open.
Qt 5.7.1 and 5.6.3 (in March or so) will eventually have upstream fixes
that hopefully work fully unlike the cherry-picks
Likely not UITK problem anymore, all known Qt 5.6 issues fixed.
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
Synced and building up to qtdeclarative now. I agree though upgrading to
5.7.1 final would be wise at least for the qtbase and qtdeclarative. For
others, maybe selectively in order to not fork all packaging from
Debian. It'd be nice to continue to sync the 10+ unchanged modules.
--
You received
Also fixed in vivid's gst0.10, and added gstreamer0.10-opus to vivid
seed.
** Changed in: gst-plugins-bad0.10 (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
I unfortunately won't have time to properly work on this until January,
so help is welcome if you want to populate the PPA earlier. Qtbase is
now done, which is the biggest module, but all others and fixing the
builds of reverse dependencies is pending.
Thanks to my earlier started 5.7.0 work
** Description changed:
Tracking bug.
https://people.canonical.com/~ubuntu-archive/transitions/html/html
/qtbase-abi-5-7-1.html
Debian successfully completed the 5.7 transition.
+
+ Ubuntu PPA to be populated: https://bileto.ubuntu.com/#/ticket/1985
+ More information:
** Changed in: canonical-devices-system-image
Assignee: (unassigned) => Zoltan Balogh (bzoltan)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1616926
Title:
I tested this in bug #1536669 on krillin and Unity 8 desktop on
Chromebook, and it worked fine with the example apps, the QML of which
called:
InputDeviceModel {
id: deviceModel
filter: InputInfo.Keyboard | InputInfo.Mouse | InputInfo.TouchScreen
onCountChanged: {
Note that it's 'appmenu-qt5', not 'app-menu-qt5'. In 16.10, appmenu-qt5
is no longer installed by default as its functionality was replaced by
better upstream implementation (even if still doesn't fix this
particular bug).
For 16.04, a fix in appmenu-qt5 would still be welcome too.
--
You
** Also affects: appmenu-qt5 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: qtbase-opensource-src (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: appmenu-qt5 (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in:
The vivid backport of the plugin seems problematic at this point, it
uses several new core location features from 5.6. Regarding "rtm" as in
"next stable platform", this is already fixed in xenial-overlay.
** Changed in: qtlocation-opensource-src (Ubuntu RTM)
Status: In Progress => Fix
Sorry Devid for the wait, we are definitely very happy to land these
fixes! We need to just decide who/when will land it.
So action items, since I'm away at least next week:
1. Jin will check with Lukasz (sil2100) on whether he could help getting a silo
to land the fixes to vivid OTA. The
Sorry, I missed the reference for the bug report but the fix now landed
in zesty and xenial-overlay.
https://lists.ubuntu.com/archives/zesty-changes/2016-October/50.html
Version 5.6.1+dfsg-3ubuntu7~2:
* debian/patches/Stop-unloading-plugins-in-QPluginLoader-and-QFactory.patch:
-
On staging armhf (the click test app is armhf) it's still pretty much as
described in comment #15. It is possible to get the "edit comnfig" to
hang, and after the fake stale lock file one will need a second start
attempt so that app really starts.
So this is with Qt 5.6.1 which includes all the
** Description changed:
+ Update: These tests actually weren't being executed in Ubuntu before.
+
With the to-be-uploaded new patch version of Qt 5.6.1, the function will
start to fail on i386 and i386 only:
FAIL! : tst_QJSEngine::toFixed() Compared values are not the same
Actual
** Description changed:
With the to-be-uploaded new patch version of Qt 5.6.1, the function will
start to fail on i386 and i386 only:
FAIL! : tst_QJSEngine::toFixed() Compared values are not the same
-Actual (result.toString()) : "12.0"
-Expected (QStringLiteral("12.1")):
Public bug reported:
With the to-be-uploaded new patch version of Qt 5.6.1, the function will
start to fail on i386 and i386 only:
FAIL! : tst_QJSEngine::toFixed() Compared values are not the same
Actual (result.toString()) : "12.0"
Expected (QStringLiteral("12.1")): "12.1"
Loc:
The paste is still going to be kept in Ubuntu's Qt 5.6.2 with the name
"qnam-ubuntu-fix6.patch".
Meanwhile, net-bearer-nm-disconnect-ap-signals7.patch was possible to
drop in 5.6.2 as that one was upstreamed as https://codereview.qt-
project.org/#/c/166147/
--
You received this bug notification
*** This bug is a duplicate of bug 1630765 ***
https://bugs.launchpad.net/bugs/1630765
** This bug has been marked a duplicate of bug 1630765
webbrowser-app crashed with SIGSEGV in
QNetworkConfiguration::~QNetworkConfiguration()
--
You received this bug notification because you are a
The 2054 ticket is in QA's hands right now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1630765
Title:
webbrowser-app crashed with SIGSEGV in
It sounded to me the old value would be around 41 or so, and the
motivation to increase was a need to have it only slightly bigger?
Meanwhile, the Qt patch is about freeing "2 more bits" so maybe 46 or 47
would work too, unless 48 is the magical "good" value that is wanted to
be had.
--
You
I've now also asked on #ubuntu-kernel if CONFIG_ARM64_VA_BITS=48 is here
to stay for the 4.4 kernel or not, pointing to this bug. It sounds like
no-one is currently considering going back to the 4.2 kernel on the
arm64 builders at least.
Meanwhile I'm collecting rebuilds of
Otherwise "ok" so far regarding rebuilds but unmodified UITK starts to
fail two subtests on arm64: bug #1631941. Those did pass before the
builder kernel update, and it's now not sure where those new failures
come from. But they do happen on both xenial and yakkety:
Public bug reported:
In unmodified trunk, so that may mean bug #1630906 builder problem is
involved but we can't change the kernel ourselves right now.
There is a Qt fix from upstream in silo https://launchpad.net/~ci-train-
ppa-service/+archive/ubuntu/2055/+packages but even with that UITK
Unfortunately the upstream fix seems to, while fixing arm64, cause
segfaults in Unity 8 on armhf and i386:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety-ci-train-ppa-service-2055/yakkety/armhf/u/unity8/20161007_180848@/log.gz
The linux kernel part of this is setting of CONFIG_ARM64_VA_BITS=48.
Also reverting of just that in the 4.4 kernel would work.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtdeclarative-opensource-
src in Ubuntu.
xenial and yakkety needed symbol updates but now they have compiled and
work at least on desktop, and the arm64 build finished so it's likely
the arm64 build issue would be solved now. I've asked QA to look into
it.
--
You received this bug notification because you are a member of Ubuntu
Touch
See bug #1630765 for updates.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1630941
Title:
Crash at shutdown in ~QNetworkConfiguration
Status in
https://bileto.ubuntu.com/#/ticket/2054 contains a patch that Michael
Sheldon reported fixing his bug #1630941, but read the description and
comments of that ticket.
** Also affects: qtbase-opensource-src (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification
*** This bug is a duplicate of bug 1630765 ***
https://bugs.launchpad.net/bugs/1630765
** This bug has been marked a duplicate of bug 1630765
webbrowser-app crashed with SIGSEGV in
QNetworkConfiguration::~QNetworkConfiguration()
--
You received this bug notification because you are a
Albert pointed to https://codereview.qt-project.org/#/c/169892
-> https://bileto.ubuntu.com/#/ticket/2055 (xenial and yakkety currently
building)
I need to stop for today but if someone has time please check if 5.4
backport is possible.
--
You received this bug notification because you are a
Correction to the code url:
http://code.qt.io/cgit/qt/qtdeclarative.git/tree/src/qml/jsruntime/qv4object.cpp?h=5.6.2#n184
(5.6.1 branch doesn't exist over there, but code seems unchanged)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
For completeness, also the other copy-pastes I made:
Thread 1 "qmlplugindump" received signal SIGSEGV, Segmentation fault.
QV4::Object::defineReadonlyProperty (this=this@entry=0x0, name=0x450bf8,
value=...) at jsruntime/qv4object.cpp:184
184 jsruntime/qv4object.cpp: No such file or
I got a temporary access (now revoked) to an arm64 box where I could
reproduce the segfault by running qmlplugindump.
Here's the backtrace:
QV4::Object::defineReadonlyProperty (this=this@entry=0x0, name=0x450bf8,
value=...) at jsruntime/qv4object.cpp:184
184 jsruntime/qv4object.cpp: No such
Public bug reported:
Builders were changed from wily to xenial (4.4) kernel for arm64, and
likely due to this the following kind of errors started happening:
https://launchpadlibrarian.net/288487533/buildlog_ubuntu-yakkety-arm64
.ubuntu-push-qml_0.1+15.10.20150826.1-0ubuntu2_BUILDING.txt.gz
Right, that test case could be tested now on xenial+overlay, even though
it doesn't necessarily reflect what happens in real life use case.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
All the fixes we had picked for https://bileto.ubuntu.com/#/ticket/1411
for backporting 5.4 are in 5.5 and 5.6, but we didn't and don't have a
good test case to prove if they fix our problems or not.
For reference, the patches we tried to pick but decided not to land for
potential risks were:
The full story is that after the commit it was reverted in 5.6
https://codereview.qt-project.org/#/c/147886/ with a comment "It's too risky
for 5.6, we should let it cook in dev for a while
and backport when ready.", but then also that revert got merged to dev so as
far as I can see upstream
Public bug reported:
See for example:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-vivid-ci-train-ppa-
service-2035/vivid/amd64/u/unity8/20161003_212514@/log.gz
--
QWARN :
** Changed in: qtbase-opensource-src (Ubuntu)
Importance: Undecided => Critical
** Changed in: canonical-devices-system-image
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
apport-collected info from earlier time for the machine can be seen at
bug #1609745.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1627502
Title:
GTK3 crash in various
** Changed in: canonical-devices-system-image
Assignee: (unassigned) => Zoltan Balogh (bzoltan)
** Changed in: canonical-devices-system-image
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
All code is the same regardless of archs, but the commit mentioned there
is Mac specific so those code paths are not used on Linux.
Another idea would be, if you don't mind adding and removing PPAs and
possibly needing to start over with your rootfs (if something goes badly
wrong), to try stable
Managed also to gdb into the python process before apport-collect
crashed, looks similar: http://pastebin.ubuntu.com/23268999/
On the plus side, since I pinpointed it now to GTK3, I was able to
install lightdm-kde-greeter to get non-GTK3 greeter for lightdm, and I
can now log in to Unity 8 (which
Anyway, there are multiple gtk related applications crashing so probably
not related to lightdm directly. For example the apport-collect that
crashes at some point, or if I open menus in GNOME Terminal or create a
new tab.
Zero problems using Qt/KDE apps however.
I agree this is pretty
Oh, right, I needed to attach to the gnome-terminal.server to get a
backtrace. Here it is, and there seems to be indeed a crash in GTK+3 for
me.
** Attachment added: "gtk3-crash-backtrace.txt"
Not other than standard kernel updates in yakkety. It's Intel Braswell
hardware.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1627502
Title:
Black screen, cursor shown,
Reminder the ticket is still waiting for testing before it goes forward.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtmultimedia-opensource-
src in Ubuntu.
https://bugs.launchpad.net/bugs/1510225
Title:
load() of a
(qtubuntu-media was added 3 days ago)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtmultimedia-opensource-
src in Ubuntu.
https://bugs.launchpad.net/bugs/1510225
Title:
load() of a QDeclarativePlaylist does not fully
Now it's really merged.
** Branch linked: lp:~timo-jyrinki/ubuntu-ui-
toolkit/enable_arm64_unittests_trunk
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1580172
Marcus confirmed the new patch also fixes the issue! I will start
landing ticket #2015 now instead. Again autopkgtests will unfortunately
take 1-2 days.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Take that with a grain of salt (it's just one related patch), but please
test if the powerpc QML tests would be passing for your component now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-system-settings-
Unfortunately upstream won't be merging the third patch to 5.6 series,
so it's only in Qt 5.8. It hides the problem instead of fixing the
problem, which is that there is a plugin that doesn't unregister its
objects before unloading.
I've prepared another silo
In yakkety UNAPPROVED queue now.
** Changed in: qtdeclarative-opensource-src (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
Public bug reported:
https://kokeile.op.fi/ (OP/Osuuspankki's new mobile friendly web site)
fails first immediately with the browser.
However: with UA - Mozilla/5.0 (Linux; Android 7.0) AppleWebKit/537.36
(KHTML, like Gecko) Chrome/53.0.2785.124 Mobile Safari/537.36 - it does
give you the mobile
** Description changed:
- If enabling arm64 unit tests, we get:
+ If enabling arm64 unit tests (bug #1580172), we get:
FAIL! : tst_UCSwipeArea::givesUpWhenLosesTouch() Received a fatal
error.
That can be skipped for now but the test should be re-enabled, hence
this bug.
--
You
** Branch linked: lp:~timo-jyrinki/ubuntu-ui-
toolkit/enable_arm64_unittests
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Assignee: (unassigned) => Timo Jyrinki (timo-jyrinki)
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Status: New => In Progress
** Changed in: ubuntu-ui-toolkit (
builds are fine from UITK perspective, but as arm64 is started
to be used we should be executing and passing the tests too.
https://code.launchpad.net/~timo-jyrinki/ubuntu-ui-
toolkit/enable_arm64_unittests/+merge/292144 can't go in before these
are fixed.
To manage notifications about
Public bug reported:
If enabling arm64 unit tests, we get:
FAIL! : tst_UCSwipeArea::givesUpWhenLosesTouch() Received a fatal
error.
That can be skipped for now but the test should be re-enabled, hence
this bug.
** Affects: ubuntu-ui-toolkit (Ubuntu)
Importance: Undecided
Status:
I've created https://bileto.ubuntu.com/#/ticket/1997 for qtdeclarative
+qtdeclarative-gles.
** Changed in: qtdeclarative-opensource-src (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
** Also affects: qtdeclarative-opensource-src (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1613670
I've pushed now also updated gles packages to the PPA. After that, I'll
start the autopkgtests which will take 1-2 days to finish.
I've also asked if upstream could consider the third patch for their 5.6
LTS series, as it's not currently there and it would always be better if
they also carry the
** Tags added: qt5.6
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntuone-credentials in
Ubuntu.
https://bugs.launchpad.net/bugs/1620338
Title:
Ubuntu One account page is blank
Status in Canonical System Image:
In
** Description changed:
My yakkety installation is now for some reason in shape that lightdm
only starts with a black screen, although mouse cursor is shown and
movable and "wifi networks available" popup is shown at the top right
corner.
+
+ After some while this disappears and the
Public bug reported:
My yakkety installation is now for some reason in shape that lightdm
only starts with a black screen, although mouse cursor is shown and
movable and "wifi networks available" popup is shown at the top right
corner.
I've tried reinstalling and everything I can think of, but I
https://codereview.qt-project.org/#/c/140750/ (Stop unloading plugins in
QPluginLoader and QFactoryLoader) mentioned in a comment was still
missing from our build.
It's now building (ubuntu6~2 and ubuntu6~xenialoverlay1~2). Let's test
all three patches once the builds are completed.
--
You
I'd go for disabling yakkety arm64 and ppc64el, to disable the minimum
required. This is usually the case that's wanted. That way we'd catch
any further regressions while Ubuntu keeps on changing.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
I think disabling the tests on xenial is a bad idea since they seem to
pass most of the time (every time I tried), while they never pass on
yakkety. Since xenial + Qt 5.6 is the next stable platform and the tests
pass there (possibly with some flakiness still), there's value to keep
them enabled.
** Changed in: qtbase-opensource-src (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1625930
Title:
thumbnailer
...and qtchooser error isn't very helpful - it doesn't find qdoc
executable for Qt 5, so automatically falls back to searching for Qt 4's
version an doesn't find that either.
** Package changed: qtchooser (Ubuntu) => unity-action-api (Ubuntu)
** Summary changed:
- qdoc doesn't work, causes
That's packages that have outdated build dependencies. Upstream moved
qdoc package from qtbase5-dev-tools to qttools5-dev-tools.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtchooser in Ubuntu.
Built and soon testable (as soon as LP publishes the binaries to be
available) from https://requests.ci-train.ubuntu.com/#/ticket/1972. Use
phablet-tools-bileto's bileto tool for example to upgrade a device, or
just apt-add-repository on desktop where no apt pinning is required.
--
You received
It does not seem to help building with those two additional QDBus
patches (qtbase 5.6.1+dfsg-3ubuntu6~1):
https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/1968/+build/10936648/+files/buildlog_ubuntu-
yakkety-ppc64el.thumbnailer_2.4+16.10.20160921-0ubuntu1_BUILDING.txt.gz
Another full
It starts to look like it's not from Qt code exactly, as the those pass
on xenial overlay which has identical Qt versions, but fail on yakkety:
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/1968/+packages
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/1969/+packages
It
Ok I've now finished a rebuild and realized it would not have raised any
flags for me earlier since my test silo only early built only for amd64,
armhf and i386. I've now added arm64 to the mix.
This QDBus problem seems more architecture specific than the others
were.
** Also affects:
Public bug reported:
See bug #1613561.
--
still ftbfs on arm64 and ppc64el, where it built before:
https://launchpad.net/ubuntu/+source/thumbnailer/2.4+16.10.20160825-0ubuntu1
--
For the record, the so far included post-5.6.1 QDBus patches in our packages:
Since this is a MIR bug I've filed bug #1625930 separately.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to thumbnailer in Ubuntu.
https://bugs.launchpad.net/bugs/1613561
Title:
[MIR] thumbnailer
Status in thumbnailer
And I'm sorry, I did do rebuilds of 38 other Qt using packages in our
phone stack in July/August in order to file bugs (like the signon and
telepathy-qt ones), but it seems thumbnailer was indeed not in my
package list before this.
--
You received this bug notification because you are a member
For the record, the so far included post-5.6.1 patches in our packages:
https://codereview.qt-project.org/#/c/167480/
https://codereview.qt-project.org/#/c/170356/
Thiago is the main contact in upstream.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
As with unity-scope-click, you could try out https://requests.ci-
train.ubuntu.com/#/ticket/1960 which has two pending QDBus patches that
are however not yet merged or approved in upstream.
We had also problems with telepathy-qt and signon with QDBus, but two
patches were landed that made QDBus
Qt 5.6 now in yakkety and xenial-overlay with largely re-engineered
QDBus (...with new but different bugs).
** Changed in: qtbase-opensource-src (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
qtsystems-opensource-src
(5.0~git20141206~44f70d99-0ubuntu9~xenialoverlay1~9) xenial;
urgency=medium
* debian/patches/Add-support-for-disabling-enabling-the-screen-saver-.patch:
- Replace former unity-screen.diff with the upstream version of it.
*
ce-src (Ubuntu)
Assignee: (unassigned) => Timo Jyrinki (timo-jyrinki)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1618590
Title:
scoperunne
** Tags added: qt5.6
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1618590
Title:
scoperunner crashed with SIGSEGV in QObject::disconnect()
Status in
Ok then :( If you also double-chcecked your libqt5core5 (etc) are
version 5.6.1+dfsg-3ubuntu6~1
For qtbase, we can continue to follow
http://code.qt.io/cgit/qt/qtbase.git/log/src/dbus?h=5.6 and
https://codereview.qt-
project.org/#/q/owner:%22Thiago+Macieira%22+status:open,n,z for any
patches to
** Also affects: unity-scope-click (Ubuntu)
Importance: Undecided
Status: New
** Changed in: qtbase-opensource-src (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Please test from https://requests.ci-train.ubuntu.com/#/ticket/1960 and
report back - builds are complete now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
Was the fix tested already with a qtbase compilation?
Both it and its pre-requirement https://codereview.qt-
project.org/#/c/157488 are not merged in upstream, so would need to be
merged first. There may be some trouble they are causing since they are
not yet merged.
--
You received this bug
I got this in qemu logging into unity8 session in yakkety.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1436203
Title:
[Dash] unity8-dash crashed with ASSERT:
Public bug reported:
--
FAIL! : GSettings::test_reset() property count
Actual (): 0
Expected (): 1
Loc:
[/«BUILDDIR»/gsettings-qt-0.1+16.04.20160329/tests/tst_GSettings.qml(102)]
(process:7207): GLib-GIO-WARNING **: g_settings_set_value: value for key
'test-enum' in schema
Public bug reported:
---
make[4]: Leaving directory
'/«BUILDDIR»/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4build1/src/Ubuntu/Components/Themes'
Segmentation fault (core dumped)
Makefile.ComponentModule:368: recipe for target
@Dmitry ok thanks for update. I just got the previous qtbase upload
tested and published and can start the next one with these tomorrow.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
qtbase-opensource-src (5.6.1+dfsg-3ubuntu4~xenialoverlay1~6) xenial;
urgency=medium
[ Timo Jyrinki ]
* debian/patches/Make-QDBusConnectionPrivate-relaySignal-be-called-in.patch:
- Antoher DBus fix needed for telephony-service (LP: #1620945)
* debian/patches/Fix-gcc-Wsuggest-override
Unfortunately fixing this would be causing true regressions in at least
ktexteditor and pyqt5:
https://requests.ci-
train.ubuntu.com/static/britney/landing-1920/yakkety/excuses.html
** Changed in: qtbase-opensource-src (Ubuntu)
Assignee: (unassigned) => Timo Jyrinki (timo-jyrinki)
** Changed in: qtbase-opensource-src (Ubuntu)
Status: New => In Progress
** Changed in: qtbase-opensource-src (Ubuntu)
Importance: Undecided => High
--
You received
** Description changed:
+ [ Impact ]
+
+ People in certain timezones have buggy time conversions in all Qt apps.
+
+ [ Test Case ]
+
+ See bug report.
+
+ [ Regression Potential ]
+
+ Should be low, in upstream LTS release and includes unit tests during
+ build time.
+
+ --- original bug
ial)
Status: New => Confirmed
** Changed in: qtbase-opensource-src (Ubuntu)
Assignee: (unassigned) => Timo Jyrinki (timo-jyrinki)
** Changed in: qtbase-opensource-src (Ubuntu Xenial)
Assignee: (unassigned) => Timo Jyrinki (timo-jyrinki)
--
You received this bug notification
Also https://codereview.qt-project.org/#/c/139057/ is needed. Next time,
full debdiff with working and rebased patches please :)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
The patches do not apply to 5.6 as is, although it doesn't look too
complicated failing.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1620173
Title:
Qt5
** Changed in: qtbase-opensource-src (Ubuntu)
Assignee: (unassigned) => Timo Jyrinki (timo-jyrinki)
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
** Changed in: canonical-devices-system-image
Milestone: None => x1
--
You received th
101 - 200 of 1932 matches
Mail list logo
