> On 2 Aug 2021, at 19:26, Daniel van Vugt <124...@bugs.launchpad.net> wrote:
>
> It might die soon:
>
> https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1840
Fair enough. Only took 14 years. Better late than never… :-)
--
You received this bug notification because you are a member of
The bug that won’t die…
Michi.
> On 2 Aug 2021, at 19:05, Daniel van Vugt <124...@bugs.launchpad.net> wrote:
>
> ** Tags removed: groovy
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/124440
>
> Title:
>
And nearly 13 years later, we are still here.
If I have a core file in the Current directory and another run of the
program encounters a fault, the old core (possibly months old) prevents
the current core file from being written. Outstanding!
--
You received this bug notification because you
This is the wrong project for that bug. The KDE thumbnailer has nothing
to do with this thumbnailer (which does enforce a size limit).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to thumbnailer in Ubuntu.
Public bug reported:
Happened during dist-upgrade from 17.04 to 17.10.
ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17
Uname: Linux 4.10.0-42-generic x86_64
** Changed in: unity-scopes-api (Ubuntu)
Assignee: Michi Henning (michihenning) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-api in
Ubuntu.
https://bugs.launchpad.net/bugs/1326105
Ti
** Changed in: unity-scopes-api (Ubuntu)
Assignee: Michi Henning (michihenning) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-api in
Ubuntu.
https://bugs.launchpad.net/bugs/1545600
Ti
** Changed in: unity-scopes-api (Ubuntu)
Assignee: Michi Henning (michihenning) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-api in
Ubuntu.
https://bugs.launchpad.net/bugs/1540876
Ti
** Changed in: unity-scopes-api (Ubuntu)
Assignee: Michi Henning (michihenning) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-api in
Ubuntu.
https://bugs.launchpad.net/bugs/1302656
Ti
** Changed in: unity-scopes-api (Ubuntu)
Assignee: Michi Henning (michihenning) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-api in
Ubuntu.
https://bugs.launchpad.net/bugs/1469770
Ti
** Changed in: unity-scopes-api (Ubuntu)
Assignee: Michi Henning (michihenning) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1546364
Title:
Li
> Thumbnailer sounds like something that should already be part of other
snaps, not something that is potentially stand-alone...?
If each snap includes its own thumbnailer, each snap will redundantly
store thumbnails (making the idea of a cache much less useful).
Moreover, all the databases for
** Changed in: unity-scopes-api (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-api in
Ubuntu.
https://bugs.launchpad.net/bugs/1360247
Title:
JSON format
** Changed in: unity-scopes-api (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1238979
Title:
[Scopes] Scope result
** Changed in: unity-scopes-api (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-api in
Ubuntu.
https://bugs.launchpad.net/bugs/1446216
Title:
[Dash]
** Changed in: unity-scopes-api (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-api in
Ubuntu.
https://bugs.launchpad.net/bugs/1548718
Title:
Need to
** Changed in: unity-scopes-api (Ubuntu)
Assignee: (unassigned) => Michi Henning (michihenning)
** Changed in: unity-scopes-api (Ubuntu)
Importance: Undecided => Critical
** Changed in: unity-scopes-api (Ubuntu)
Status: New => In Progress
--
You received this bug not
Thanks for that Pete.
>From the build log, I think the issue is simply that gtest changed, and
we need to pull in your cmake fixes. I think we have those in devel
already, but not released yet. I’ll figure it out on Monday :)
Michi.
> On 13 Jan 2017, at 21:09 , Pete Woods
** Changed in: thumbnailer (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to taglib in Ubuntu.
https://bugs.launchpad.net/bugs/1640326
Title:
FTBFS on zesty
Status in
** Changed in: unity-scopes-api (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: unity-scopes-api (Ubuntu RTM)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Summary changed:
- frieza_arm64, staging #99: SD card not mounted
+ SD card not recognized on M10 with ubuntu-touch/staging/ubuntu
** Changed in: mediascanner2 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mediascanner2 in Ubuntu.
https://bugs.launchpad.net/bugs/1649313
Title:
I downloaded the latest image from ubuntu-touch/staging/ubuntu
"OS Build Details" in system settings reports r85, 20161215
Unfortunately, I can't provide the output from system-image-cli because,
since flashing this image, USB is broken. I can no longer get my desktop
to recognize the USB port.
I just tried with OTA-14, and it works fine there too. However, the
first time I inserted the card, it wasn't recognized. It was only after
I ejected and re-inserted it that it was mounted.
This may just be dodgy connectors in the card slot.
I'll also try with image you linked to.
--
You
It could be just that the card slot is dirty or some such. I would also
try a reboot. Possibly, some other low-level piece of machinery got
stuck. At any rate, I don't think this is a mediascanner problem. If the
card isn't mounted, mediascanner can't possibly see it.
--
You received this bug
I tried it with build 191 from ubuntu-touch/rc-proposed/bq-aquaris-pd.en.
After inserting an SD card with a few music and image files, the music scope
shows the tracks, and gallery app shows all the images on the card.
I'm about to try with OTA 14. But I expect to see the same results.
Can you
It looks like click-scope is the only scope that is failing. Queries to
the music scope work just fine, as do queries to remote scopes (via
smartscopesproxy). All these scopes run the exact same code in the
runtime.
I have no idea what exactly is going wrong, but I strongly suspect that
it is in
I've spent pretty much all day trying to track this down. The debug
cycle time with core 16 in a VM doesn't help :-(
What I can see is that crap comes out of the ZmqReceiver when an object
adapter tries to dispatch an incoming request to the scope. The problem
doesn't manifest itself in the same
@dobey: There is in the log: terminate called after throwing an instance
of 'unity::scopes::MiddlewareException'
I don't know where this exception comes from. It would be great to find
out. I believe that, if an exception is thrown (no matter what kind of
exception) from one of the threads we
Michael, the command fails because /run/user/0/dbus-session doesn't exist.
I also looks like I have a different version installed. I see 264 and 277
(besides common) in /root/snap/unity8-session.
I adjusted your command to not set DBUS_SESSION_ADDRESS and explicitly
set LD_LIBRARY_PATH (without
** Also affects: unity-scopes-api (Ubuntu)
Importance: Undecided
Status: New
** Changed in: unity-scopes-api (Ubuntu)
Importance: Undecided => Critical
** Changed in: unity-scopes-api (Ubuntu)
Assignee: (unassigned) => Michi Henning (michihenning)
** Changed in: uni
> "BFB" is "Big Flavorful Button" ;)
Ah, as in "BFG-9000" :-)
> So, from your screenshot it looks like you are hitting case number 2 from my
> previous post. Is
> there a crash report in /var/crash/ for the scoperunner?
/var/crash doesn't exist on a snappy machine. I have no idea where core
There doesn't appear to be a way to be notified of unmount attempts at
the moment. There is an fschange modification about ten years ago
(http://stefan.buettcher.org/cs/fschange/), but that never made it into
the kernel.
It looks like it's impossible for mediascanner to automatically back off
*** This bug is a duplicate of bug 1310186 ***
https://bugs.launchpad.net/bugs/1310186
** This bug has been marked a duplicate of bug 1310186
mediascanner prevents unmounting usb device
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
Sorry, I don't know what a "BFB result" is. It does show "Apps". I've
attached a screenshot.
** Attachment added: "Screenshot from 2016-12-08 14-23-54.png"
The assertion failure appears to be unrelated to the click scope not showing
any results.
What is interesting is that the other scopes seems to work fine, it's only the
click scope that is empty. With the missing applications dir in place, I'm not
seeing any errors at all in the logs, just the
Public bug reported:
We just got this test failure on zesty:
https://jenkins.canonical.com/unity-
api-1/job/build-2-binpkg/arch=armhf,release=zesty/1022/consoleFull
Search for "OnlineAccountClientTest.service_update_callback"
In the log, we see
*** This bug is a duplicate of bug 1643169 ***
https://bugs.launchpad.net/bugs/1643169
See comment #2 here: https://bugs.launchpad.net/ubuntu/+source/unity-
scopes-api/+bug/1643169
** This bug has been marked a duplicate of bug 1643169
package libunity-scopes1.0:amd64
The missing applications dir was coincidental and isn't the root cause of this
problem.
The issue is racy, so I'm seeing different things in the logs each time.
Still digging...
** Branch unlinked: lp:~michihenning/unity-scopes-api/create-
applications-dir
--
You received this bug notification
I'll push a branch to have the registry create the applications dir if
it doesn't exist. That should be good enough for the moment. But the
whole .desktop file generation thing is a hack. As far as we can work
out, this was needed because online accounts refused to work unless
there was a .desktop
I would like to track down what causes the assertion failure in scopes-
api regardless.
DBUS_SESSION_BUS_ADDRESS=`cat /run/user/0/dbus-session | cut -f2- -d=`
HOME=/root/snap/unity8-session/264
SNAP_USER_DATA=/root/snap/unity8-session/264
SNAP_USER_COMMON=/root/snap/unity8-session/common
Looking at /root/snap/unity8-session/common/.cache/upstart/scope-
registry.log, there are lots of messages along the following lines:
scoperegistry: ignoring scope "clickscope": cannot create metadata:
unity::SyscallException: RegistryObject::create_desktop_file: unable to
create desktop file:
I've added Pawel because of the "Invalid departments database" error.
I'm looking at the other errors. I suspect what's happening is that some
of the local socket path names are wrong.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Changed in: thumbnailer (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to taglib in Ubuntu.
https://bugs.launchpad.net/bugs/1640326
Title:
FTBFS on zesty
Status in leveldb
Sorry wrong link for upstream bug. It's here:
https://github.com/google/leveldb/issues/425
** Bug watch added: github.com/google/leveldb/issues #425
https://github.com/google/leveldb/issues/425
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Upstream bug here: https://github.com/Level/leveldown/issues/321
** Bug watch added: github.com/Level/leveldown/issues #321
https://github.com/Level/leveldown/issues/321
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
The builder uses libleveldb 1.19-2, but the zesty archives still have
libleveldb 1.18-5.
After installing 1.19-2 locally, I instantly got the same failure.
** Also affects: leveldb (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
After lots of debugging and tracing, I found the root cause with
valgrind. The interesting thing is that this happens only in the silo.
When I run the same code on my zesty VM, everything is fine. So, what is
different in the silo builders from a vanilla zesty install? (Installed
zesty about two
Almost certainly not related. The test that triggers this is far away
from the core dump. Still worth following up on though.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to taglib in Ubuntu.
I'm seeing this report from valgrind on zesty. On xenial, the test runs
clean. Not sure whether this might be related.
==63566== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 10 from 10)
==63463== Conditional jump or move depends on uninitialised value(s)
==63463==at 0x4C33E26:
I think we can rule out leveldb. It's at revision 1.18-5 in both xenial
and zesty.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to taglib in Ubuntu.
https://bugs.launchpad.net/bugs/1640326
Title:
FTBFS on zesty
Status in
Taglib fix is in the linked branch.
The thumbnailer test dumps core on all architectures on zesty. The fault
keeps moving around, looks like a race condition. We are not using
threads ourselves, so the problem likely is in a something we call into.
Candidates would be QT and (unlikely) leveldb.
I have a fix for the taglib issue that does not require changes to
taglib. (taglib 1.11 added a new API for getting images out of
VorbisComments and broke the behavior (not API) of the existing one.)
Still looking at the other issues.
--
You received this bug notification because you are a
Taglib 1.11 has broken extraction of VorbisComments.
I've opened a bug here: https://github.com/taglib/taglib/issues/770
Looking at the taglib source now to see whether there is an easy fix.
** Changed in: thumbnailer (Ubuntu)
Assignee: (unassigned) => Michi Henning (michihenn
Unfortunately, just suppressing the Qt tests doesn't fix this. It turns
out that, on zesty, the tests for all architectures fail. It looks like
a problem with taglib. Every test that tries to extract artwork from an
ogg video file fails.
There is also a segfault in the thumbnailer test. That
Fix is in a silo: https://bileto.ubuntu.com/#/ticket/2175
--
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/1640326
Title:
FTBFS on zesty
Status in thumbnailer package
Thanks for that, will fix now.
--
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/1640326
Title:
FTBFS on zesty
Status in thumbnailer package in Ubuntu:
New
Bug
Looks like this is caused by packages installed in /usr/local that
conflict with click.
** Changed in: unity-scopes-api (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-api
The connectivity status is something that is *not* set by scopes-api.
Instead, the status is received by scopes-api from whoever makes the
query (typically, the shell) and then passed through to the scope. In
turn, the shell just passes on what it gets from QNetworkAccessManager,
I believe.
We
Thanks for all the detective work!
I suspect that the MiddlewareException in coincidental and caused by an
earlier timeout. But we shouldn't get stuck like this and things should
recover transparently if the network goes away. I'll have a look and see
what's going on.
--
You received this bug
** Changed in: thumbnailer (Ubuntu)
Status: Incomplete => Fix Released
--
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
It's difficult to see how to fix this. External devices are scanned
because people quite often use USB sticks or external drives with their
music collections.
I'm not sure whether it is even possible for mediascanner to find out
that some other arbitrary process has asked for a filesystem to be
** Also affects: canonical-scopes-project
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mediascanner2 in Ubuntu.
https://bugs.launchpad.net/bugs/1445755
Title:
Provide a way to
This is fixed in gallery app, but the photo scope also has this problem.
I'm still seeing loads of album covers when I open the photo scope.
Adding photo scope as affected.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Looks like 1991 has landed now.
--
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 package in Ubuntu:
Incomplete
** Changed in: thumbnailer (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 qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1625930
Title:
thumbnailer
** Changed in: mediascanner2 (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: thumbnailer (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mediascanner2 in Ubuntu.
Changes are in silo 1991.
--
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 package in Ubuntu:
Incomplete
Bug
Tests are disabled for on arm64, ppc64, and ppc64le for yakkety and
xenial. That's where we've seen failures, and we don't particularly care
about these arches at the moment.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Do you have any examples for music players that recognise
.? (I'm not aware of any at this point.)
The existing list of file names exists because they are widely used by
various players, so we are just following established precedent here. We
can look at supporting this, but I'd prefer to do this
** Also affects: mediascanner2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mediascanner2 in Ubuntu.
https://bugs.launchpad.net/bugs/1627252
Title:
Recognize album
I don't think what we are seeing in thumbnailer is the same thing. Your
issue and the telepathy one is related to shutdown. Ours strike all over
the place. But there are definitely problems with Qt 5.6, whatever the
details.
--
You received this bug notification because you are a member of
Hmmm... The xenial failure is highly suspicious because that particular
test has never failed before. I'm quite confident that the failure
exists on xenial too, just doesn't manifest as often.
I did look at the telepathy code changes, and they address a completely
different issue. What we are
You cannot drop an arbitrary jpg file into a music folder and expect it
to be picked up as artwork. This simply doesn't work. The following file
basenames are recognised cover art:
cover
album
albumart
.folder
folder
These base names must have one of the following extensions:
jpeg
jpg
png
Gregory, can you please attach an example of what you think are the
failing files?
We need a directory that shows the problem. It should contain at least
one music track for which you see incorrect online artwork or no
artwork, plus whatever files you think should be used to display the
artwork
** Changed in: thumbnailer (Ubuntu)
Status: Fix Committed => Fix Released
--
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/1528058
Title:
settings not readable
After discussions with mterry and alecu, we decided to disable the
failing tests on xenial and yakkety. The linked branch does this.
I've opened a separate bug to make sure we don't forget to turn those
tests back on:
https://bugs.launchpad.net/ubuntu/+source/thumbnailer/+bug/1626815
** Branch
Public bug reported:
See https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-
src/+bug/1625930
We need to track this problem and re-enable the tests ASAP.
** Affects: thumbnailer (Ubuntu)
Importance: High
Status: New
--
You received this bug notification because you are
** Changed in: thumbnailer (Ubuntu)
Assignee: (unassigned) => Michi Henning (michihenning)
** Changed in: thumbnailer (Ubuntu)
Importance: Undecided => Critical
** Changed in: thumbnailer (Ubuntu)
Status: New => In Progress
--
You received this bug notification be
The failure happens in both yakkity and xenial (because both use Qt
5.6). The failure moves around. In the latest build, we got a failure on
xenial ppc64el (which is a first).
If we disable tests, we have to disable *all* integration tests that use
DBus for *both* xenial and yakkety. We haven't
I decided to kick the build in silo 1968 to see whether the fault would
move. This time, it failed on yakkety on arm64 and ppc64el as before,
but also failed on xenial powerpc. The failure on xenial is in a test
that uses QDBus to talk between client and server. The client fails
because it doesn't
I install a yakkety arm64 chroot on my M10 and built the thumbnailer.
The tests run fine, over and over. I do not see any failures.
dpkg reports:
libc6:arm64 2.24-0ubuntu1
arm64
gcc-66.2.0-3ubuntu15
Another option: it could simply a race that shows up in the train only
because the builders are VMs (I believe) and the underlying hardware
might be loaded more heavily. I'd expect CPU and I/O timings to be
different in the train than on my M10. So, it is still possible that
this is simply a race
Silo 1968 contains a no-change rebuild of the thumbnailer. As expected,
things are again blowing up for arm64 and ppc64el on yakkety.
Interestingly, things worked with xenial, even though the same QDBus is
installed there, as far as I can see.
I don't think the telepathy code changes you linked
So, as best as we can tell, this is caused by an upgrade to Qt.
Specifically, anything that uses QDBus is falling over. We are seeing
similar problems with unity-scope-click here:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-
src/+bug/1618590
Basically, the code works with Qt 5.5,
The tests that are failing are all Qt related. I suspect a problem in Qt
rather than our code. (The thumbnailer code hasn't changed in ages, and
the fact that it fails only on Yakkity suggest a problem with one of our
dependencies.)
8: thumbnailer-service: [23:19:59.671] failure cache: 0
** Changed in: unity-scopes-api (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-api in
Ubuntu.
https://bugs.launchpad.net/bugs/1548718
Title:
Need to update
I didn't even know that there was a failed build. Looking at the build
log, the test failures are almost certainly caused by a flaky builder.
We have seen this sort of thing recently on another project too.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
There is no direct evidence in the log to indicate something spinning.
But it shows that dash.ubuntu.com wasn't responding for much of the
time, as evidenced by the periodic retries. We should check that the
code doesn't do something silly when that happens.
--
You received this bug notification
Well, it's not ftbfs anymore. More pertinently, should I publish now or
wait until after OTA-13?
--
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]
That was fixed quite some time ago, so it should no longer be a problem.
(We are at 0.5.3 now; that's in yakkety, not sure about Vivid and
Xenial.) I never managed to reproduce the problem on arm.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Silo 54 is approved for QA. I was told not to publish this until after
OTA-13. If this needs to go in now, someone let me know please, and I'll
publish it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to thumbnailer in
Lukasz and Pawel have been been working on getting the MIR for this
happening. I'm out of that loop though, so I don't know the details.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to capnproto in Ubuntu.
+1!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mediascanner2 in Ubuntu.
https://bugs.launchpad.net/bugs/1621002
Title:
Mediascanner2 test failure on yakkety/{armhf,arm64,ppc64el} with
latest dbus-cpp
Status in
** Branch linked: lp:~michihenning/unity-scopes-api/shlib-fix
** Changed in: unity-scopes-api (Ubuntu)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-api in
Ubuntu.
** Changed in: unity-scopes-api (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-api in
Ubuntu.
https://bugs.launchpad.net/bugs/1548718
Title:
Need to update micro
** Changed in: unity-scopes-api (Ubuntu)
Assignee: (unassigned) => Michi Henning (michihenning)
** Changed in: unity-scopes-api (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subs
Good catch!
I've seen this in the past due to uninitialised variables. With
optimisation, the compiler gets more aggressive about register re-use,
so a bug can manifest under optimisation when the uninitialised variable
ends up in a register that had a previous value in it. (In debug mode,
the
If this is with boost 1.61, either the problem is still present in boost
or, if the local files were messed up somehow, the exception would
legitimately be raised because the locale definition is broken.
Comment #9 seems to indicate that the problem was fixed after
regenerating the locale. In
The problem is caused by boost, and we are defenseless until we get 1.57
or later into the image. There is an earlier bug about this here:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1303637
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
1 - 100 of 1109 matches
Mail list logo
