On Wed, Nov 29, 2017 at 12:04 AM Thomas Voß <tho...@airmap.com> wrote:
> On Tue, Nov 28, 2017 at 4:00 PM, Sebastiaan Couwenberg
> <sebas...@xs4all.nl> wrote:
> > On 11/28/2017 09:18 AM, Bas Couwenberg wrote:
> >> On 2017-11-28 09:00, Thomas Voß wrote:
> >>
On Tue, Nov 28, 2017 at 4:00 PM, Sebastiaan Couwenberg
<sebas...@xs4all.nl> wrote:
> On 11/28/2017 09:18 AM, Bas Couwenberg wrote:
>> On 2017-11-28 09:00, Thomas Voß wrote:
>>> we are right now investigating an issue when simplifying geometries
>>> with GDAL, whic
you have plans to update GEOS to 3.6 (we
are happy to use unstable or backports)? If not, do you think it's
feasible to cherry-pick the fix into the current package?
Thanks a lot for your great work,
Thomas
--
Thomas Voß
Technical Systems Architect
AIRMAP
tho...@airmap.com
AIRMAP.COM
We also want the fix in:
https://github.com/grpc/grpc/issues/11195
** Bug watch added: github.com/grpc/grpc/issues #11195
https://github.com/grpc/grpc/issues/11195
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
; urgency=medium
+
+ * Revert patch openssl-1.1.0 (Closes: #1727528)
+
+ -- Thomas Voß <tho...@airmap.com> Wed, 25 Oct 2017 23:36:46 +0200
+
grpc (1.3.2-1) unstable; urgency=medium
[ Pirate Praveen <prav...@onenetbeyond.org> ]
diff -Nru grpc-1.3.2/debian/patches/openssl-1.1.0.diff
Public bug reported:
When trying to build against the grpc packages in Artful, linking fails
with:
/usr/lib/libgrpc.so: undefined reference to `RSA_set0_key'
The package build logs for grpc contain two related warnings:
dpkg-shlibdeps: warning: symbol RSA_set0_key used by
On Sun, Apr 2, 2017 at 9:18 AM, Aleksander Morgado
<aleksan...@aleksander.es> wrote:
> On Sat, Apr 1, 2017 at 10:11 PM, Thomas Voß
> <thomas.voss.boc...@gmail.com> wrote:
>> A simple patch to avoid MBIM modems reporting that they support the location
>> interface.
On Sun, Apr 2, 2017 at 10:37 AM, Aleksander Morgado
<aleksan...@aleksander.es> wrote:
>
> On Sat, Apr 1, 2017 at 10:11 PM, Thomas Voß
> <thomas.voss.boc...@gmail.com> wrote:
> > MBIM does not support 3gpp location data right now. For that,
> > we make
MBIM does not support 3gpp location data right now. For that,
we make sure that the location interface is not reported as
supported by MBIM modems.
---
src/mm-broadband-modem-mbim.c | 12
1 file changed, 12 insertions(+)
diff --git a/src/mm-broadband-modem-mbim.c
A simple patch to avoid MBIM modems reporting that they support the location
interface.
I haven't submitted patches to mailing list in quite a while, so please bear
with me
while I'm learning.
Thanks,
Thomas
Thomas Voß (1):
mbim-modem: disable location interface
src/mm-broadband-modem
** Branch linked: lp:~thomas-voss/location-service/fix-zesty-ftbfs
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1640320
Title:
FTBFS in zesty
Status in location-service
** Branch linked: lp:~thomas-voss/location-service/fix-zesty-ftbfs
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to location-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1640320
Title:
FTBFS in zesty
Status in
** Branch linked: lp:~thomas-voss/location-service/fix-zesty-ftbfs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1640320
Title:
FTBFS in zesty
To manage notifications about this bug go to:
** Branch linked: lp:~thomas-voss/location-service/fix-zesty-ftbfs
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1640320
Title:
FTBFS in zesty
To manage notifications
Thanks for the bug report. I failed to reproduce the issue you are
observing. Could you add the output of 'apt-cache show snap-confine' and
'apt-cache show snapd' to the bug report? Do you have -proposed enabled?
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Tags added: 14.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1675232
Title:
Snapd install fails with "No such file or directory" on 14.04
To manage notifications about this bug go to:
Testing packages for snapd-xdg-open master are in:
https://launchpad.net/~thomas-voss/+archive/ubuntu/trusty
Feedback from testers is very welcome.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: snapd-xdg-open (Ubuntu)
Importance: Undecided => High
** Changed in: snapd-xdg-open (Ubuntu)
Assignee: (unassigned) => Thomas Voß (thomas-voss)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1666122
Title:
package snapd 2.22.2~14.04 failed to install/upgrade: Unterprozess
neues pre-removal-Skript gab den Fehlerwert 5
Hey Max,
as a quick test, would you mind trying to set
TAR_OPTIONS='--format=posix'
in the environment you run spread in?
Thanks,
Thomas
On Thu, Feb 9, 2017 at 6:19 PM, Max Brustkern
wrote:
> I'm attempting to use the spread linode backend with this system
On Thu, Feb 9, 2017 at 2:38 PM, Roberto Mier Escandón
<roberto.escan...@canonical.com> wrote:
> Because this will use nextcloud documents, and they are internal to
> nextcloud snap
>
In that case, content-sharing would help, yes.
> On 09/02/17 14:33, Thomas Voß wrote:
&
; [1] https://github.com/rmescandon/loolwsd-snap
>
> BR.
>
> On 09/02/17 10:32, Thomas Voß wrote:
>> Hey Roberto,
>>
>> On Wed, Feb 8, 2017 at 4:54 PM, Roberto Mier Escandón
>> <roberto.escan...@canonical.com> wrote:
>>> Hey engineers,
>
Hey Roberto,
On Wed, Feb 8, 2017 at 4:54 PM, Roberto Mier Escandón
wrote:
> Hey engineers,
>
> I need some ideas to solve this: I'm trying to snap collaboraoffice
> online but that's not being easy at all. FYI: this is a kind of Google
> Drive stuff so that when
eb 2017, at 09:02, XiaoGuo Liu <xiaoguo@canonical.com> wrote:
>>
>> Hi Thomas,
>>
>> So, an end user needs to manually add the path, right? It is not a little
>> bit straightforward though. I think it would be good to come with detailed
>> instructions.
>
https://bugs.launchpad.net/ubuntu/+source/xorg-server-lts-xenial/+bug/1655724
was released to the updates pocket today.
Cheers,
Thomas
On Thu, Feb 2, 2017 at 8:38 AM, Thomas Voß <thomas.v...@canonical.com> wrote:
> On Thu, Feb 02, 2017 at 12:51:59AM +0100, Joseph Rushton Wakel
I'm assuming that vrruiz added verification-needed accidentally.
Removing it again as the report reads like a success.
** Tags removed: verification-needed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server-lts-xenial in
I'm assuming that vrruiz added verification-needed accidentally.
Removing it again as the report reads like a success.
** Tags removed: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I verified that the package from -proposed enables installation of
snapd/systemd without any issues. Waiting for qa to give a vote, too,
before setting to verification-done.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I verified that the package from -proposed enables installation of
snapd/systemd without any issues. Waiting for qa to give a vote, too,
before setting to verification-done.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server-lts-xenial
I verified that the package from -proposed enables installation of
snapd/systemd without any issues. Waiting for qa to give a vote, too,
before setting to verification-done.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
On Thu, Feb 02, 2017 at 12:51:59AM +0100, Joseph Rushton Wakeling wrote:
> On 31/01/17 14:01, Jamie Bennett wrote:
> > Hi,
> >
> > The team are pleased to announce that, after extensive testing in proposed,
> > snapd is officially available in the Trusty Tahr updates archive [1]. If
> > you are
@Seth: We are deploying a deputy or subordinate systemd not running as
PID 1 on trusty to support snapd. We isolated systemd on trusty away and
minimized its interaction with the system, except for the functionality
required by snapd. That is, upstart is still PID 1 and responsible for
all system
** Changed in: snappy
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/1631270
Title:
running a command for a snap in try mode fails on trusty
To manage
** Changed in: systemd (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: systemd (Ubuntu Trusty)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: systemd (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: systemd (Ubuntu Trusty)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
I managed to reproduce the issue without snapd being involved at all.
Marking as invalid for snapd, bumping priority to "high". Among other
things, this blocks autopkgtests for snapd on trusty.
** Changed in: snapd
Status: Confirmed => Invalid
** Changed in: systemd (Ubuntu)
I managed to reproduce the issue without snapd being involved at all.
Marking as invalid for snapd, bumping priority to "high". Among other
things, this blocks autopkgtests for snapd on trusty.
** Changed in: snapd
Status: Confirmed => Invalid
** Changed in: systemd (Ubuntu)
I managed to reproduce the issue without snapd being involved at all.
Marking as invalid for snapd, bumping priority to "high". Among other
things, this blocks autopkgtests for snapd on trusty.
** Changed in: snapd
Status: Confirmed => Invalid
** Changed in: systemd (Ubuntu)
I did some digging into systemd-tmpfiles and its configuration. In the
trusty case, with systemd *not* running as PID 1, the systemd-tmpfiles
does not strictly need to create /run/nologin to shield state
transitions. For that, I removed creation of the file from trusty's
systemd-tmpfiles
I did some digging into systemd-tmpfiles and its configuration. In the
trusty case, with systemd *not* running as PID 1, the systemd-tmpfiles
does not strictly need to create /run/nologin to shield state
transitions. For that, I removed creation of the file from trusty's
systemd-tmpfiles
** Changed in: snapd
Status: New => Confirmed
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1660573
Title:
"system is booting
** Changed in: snapd
Status: New => Confirmed
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1660573
I can occasionally reproduce the issue with an autopkgtest setup using a
qemu vm. Local spread tests using the qemu backend work fine, though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1660573
I can occasionally reproduce the issue with an autopkgtest setup using a
qemu vm. Local spread tests using the qemu backend work fine, though.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
This bug report against systemd seems relevant:
https://github.com/systemd/systemd/issues/3436
Other distributions are experiencing the issue, too:
https://bugzilla.opensuse.org/show_bug.cgi?id=980324
** Bug watch added: github.com/systemd/systemd/issues #3436
This bug report against systemd seems relevant:
https://github.com/systemd/systemd/issues/3436
Other distributions are experiencing the issue, too:
https://bugzilla.opensuse.org/show_bug.cgi?id=980324
** Bug watch added: github.com/systemd/systemd/issues #3436
This bug report against systemd seems relevant:
https://github.com/systemd/systemd/issues/3436
Other distributions are experiencing the issue, too:
https://bugzilla.opensuse.org/show_bug.cgi?id=980324
** Bug watch added: github.com/systemd/systemd/issues #3436
Please note
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1656382/comments/9.
snapd is installable from trusty-proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1614587
Title:
unable
As discussed on IRC: The service unit fails to start up and the snap is
not installed. Hence you don't see the unit showing up.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1657152
Title:
snapd
@Rolf: No worries, thanks for testing it out :) I would appreciate if
you could update https://bugs.launchpad.net/bugs/1614587 with your
latest findings, too. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Rolf: I fail to reproduce your installation issues after enabling
proposed. snapd installs fine, and cgroup-lite is available from main in
trusty. Would you mind sharing a little more detail about your setup and
the issues you are encountering?
--
You received this bug notification because you
I verified that brightness control keeps on working on my local machines
(Lenovo x220 and x250). I do not have the HW in the bug title available
for testing purposes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I verified that brightness control keeps on working on my local machines
(Lenovo x220 and x250). I do not have the HW in the bug title available
for testing purposes.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
For completeness, you might want to attach syslog and the output of
'sudo journalctl -x'.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1657504
Title:
asciinema 1.3.0 snap is segfaulting on 14.04
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Thomas Voß (thomas-voss)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655302
Title:
[Trusty] systemd startup fails in the prese
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Thomas Voß (thomas-voss)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1655302
Title:
[Trusty] syst
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Thomas Voß (thomas-voss)
** Changed in: systemd (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: systemd (Ubuntu Trusty)
Assignee: (unassigned) => Thomas Voß (thomas-voss)
** Changed in: systemd (Ubun
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Thomas Voß (thomas-voss)
** Changed in: systemd (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: systemd (Ubuntu Trusty)
Assignee: (unassigned) => Thomas Voß (thomas-voss)
** Changed in: systemd (Ubun
Corresponding cgmanager:
cgmanager: could not open cgroup file for 0
cgmanager:victim_under_proxy_cgroup: Could not determine the victim's cgroup
cgmanager:do_move_pid_main: victim's cgroup is not under proxy's (p.uid 0)
--
You received this bug notification because you are a member of Ubuntu
Corresponding cgmanager:
cgmanager: could not open cgroup file for 0
cgmanager:victim_under_proxy_cgroup: Could not determine the victim's cgroup
cgmanager:do_move_pid_main: victim's cgroup is not under proxy's (p.uid 0)
--
You received this bug notification because you are a member of Ubuntu
>From /var/log/upstart/systemd.log:
systemd 204 running in system mode. (+PAM +LIBWRAP +AUDIT +SELINUX +IMA
-SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ)
Detected virtualization 'kvm'.
Inserted module 'autofs4'
Set hostname to .
/etc/mtab is not a symlink or not pointing to /proc/self/mounts. This
>From /var/log/upstart/systemd.log:
systemd 204 running in system mode. (+PAM +LIBWRAP +AUDIT +SELINUX +IMA
-SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ)
Detected virtualization 'kvm'.
Inserted module 'autofs4'
Set hostname to .
/etc/mtab is not a symlink or not pointing to /proc/self/mounts. This
Public bug reported:
In trusty, systemd 204 clashes with cgmanager, with systemd failing to
start up properly. As a consequence, snapd fails to operate properly.
** Affects: systemd (Ubuntu)
Importance: High
Status: New
--
You received this bug notification because you are a
Public bug reported:
In trusty, systemd 204 clashes with cgmanager, with systemd failing to
start up properly. As a consequence, snapd fails to operate properly.
** Affects: systemd (Ubuntu)
Importance: High
Status: New
--
You received this bug notification because you are a
Public bug reported:
In trusty, systemd 204 clashes with cgmanager, with systemd failing to
start up properly. As a consequence, snapd fails to operate properly.
** Affects: systemd (Ubuntu)
Importance: High
Status: New
--
You received this bug notification because you are a
Public bug reported:
When trying to install the latest snapd on a 14.04.5 desktop image, the
installation of systemd (as a dependency of snapd) triggers a whole
bunch of downgrades as systemd-shim is removed and replaced with
systemd.
We have to adjust the packaging such that installation of
Public bug reported:
When trying to install the latest snapd on a 14.04.5 desktop image, the
installation of systemd (as a dependency of snapd) triggers a whole
bunch of downgrades as systemd-shim is removed and replaced with
systemd.
We have to adjust the packaging such that installation of
Public bug reported:
When trying to install the latest snapd on a 14.04.5 desktop image, the
installation of systemd (as a dependency of snapd) triggers a whole
bunch of downgrades as systemd-shim is removed and replaced with
systemd.
We have to adjust the packaging such that installation of
util-linux (2.20.1-5.1ubuntu20.9) trusty; urgency=medium
* mount/lomount.c: Query /dev/loop-control for next free loopback device.
(LP: #1640823)
Date: Tue, 15 Nov 2016 09:52:37 +0100
Changed-By: Thomas Voß <thomas.v...@canonical.com>
Maintainer: Ubuntu Developers <ubuntu-d
Thanks for your detailed feedback, I revisited the patch (please see the
diff here http://paste.ubuntu.com/23522718/). I think (1.) - (3.) are
covered.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for your detailed feedback, I revisited the patch (please see the
diff here http://paste.ubuntu.com/23522718/). I think (1.) - (3.) are
covered.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
util-linux (2.20.1-5.1ubuntu20.8) trusty; urgency=medium
* mount/lomount.c: Query /dev/loop-control for next free loopback device.
(LP: #1640823)
Date: Tue, 15 Nov 2016 09:52:37 +0100
Changed-By: Thomas Voß <thomas.v...@canonical.com>
Maintainer: Ubuntu Developers <ubuntu-d
I just stumbled across an issue when exercising snapd in 14.04 under
qemu. Sideloading the same snap a few times leads to the following error
message:
Oct 25 21:37:21 autopkgtest mount[21178]: mount: could not find any
free loop device
Might be unrelated, but thought that I would just note
I just stumbled across an issue when exercising snapd in 14.04 under
qemu. Sideloading the same snap a few times leads to the following error
message:
Oct 25 21:37:21 autopkgtest mount[21178]: mount: could not find any
free loop device
Might be unrelated, but thought that I would just note
No visible satellites in an indoor scenario is certainly possible.
Do you have SIM cards in your phone? Are you actively connected to an AP?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
No visible satellites in an indoor scenario is certainly possible.
Do you have SIM cards in your phone? Are you actively connected to an AP?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to location-service in
Ubuntu.
No visible satellites in an indoor scenario is certainly possible.
Do you have SIM cards in your phone? Are you actively connected to an AP?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to location-service in Ubuntu.
No visible satellites in an indoor scenario is certainly possible.
Do you have SIM cards in your phone? Are you actively connected to an AP?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630014
Public bug reported:
The upstream kernel has support for the vc4 driver, providing an open-
source drm driver for accessing the pi2 GPU. The respective driver is
currently missing from the ubuntu pi2 kernel.
** Affects: linux-raspi2 (Ubuntu)
Importance: Undecided
Status: New
--
Public bug reported:
When executing snapd's spread test suite, tests/main/try fails with:
+ echo 'Given a buildable snap which access confinement-protected resources in
a known directory'
Given a buildable snap which access confinement-protected resources in a known
directory
+ echo 'When try
The following setup gives me a working shell
> export SNAP_NAME=test-snapd-tools
> /usr/lib/snapd/snap-confine snap.test-snapd-tools.head /bin/bash
with the following /proc/self/mountinfo:
qemu:ubuntu-14.04-64 .../tests/main/try# cat /proc/self/mountinfo
79 48 7:0 / / rw,relatime - squashfs
/usr/bin/test_gps is known to segfault and we should totally remove it.
For "Why not gpsd?": It does not support assisted GPS in the way we need
it, nor does it provide any sort of fusioning of network- and satellite-
based positioning ootb. More to this, the NMEA that is reported back
here does
/usr/bin/test_gps is known to segfault and we should totally remove it.
For "Why not gpsd?": It does not support assisted GPS in the way we need
it, nor does it provide any sort of fusioning of network- and satellite-
based positioning ootb. More to this, the NMEA that is reported back
here does
/usr/bin/test_gps is known to segfault and we should totally remove it.
For "Why not gpsd?": It does not support assisted GPS in the way we need
it, nor does it provide any sort of fusioning of network- and satellite-
based positioning ootb. More to this, the NMEA that is reported back
here does
** Changed in: platform-api (Ubuntu)
Importance: Critical => High
** Changed in: platform-api (Ubuntu)
Assignee: (unassigned) => Thomas Voß (thomas-voss)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: platform-api (Ubuntu)
Importance: Critical => High
** Changed in: platform-api (Ubuntu)
Assignee: (unassigned) => Thomas Voß (thomas-voss)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to us
** Branch linked: lp:~thomas-voss/platform-api/fix-1620553
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1620553
Title:
Haptics engine uses sync dbus calls. Was: "Taps are delayed by
1-2seconds,
** Branch linked: lp:~thomas-voss/platform-api/fix-1620553
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to platform-api in Ubuntu.
https://bugs.launchpad.net/bugs/1620553
Title:
Haptics engine uses sync dbus calls. Was:
On Thu, Sep 1, 2016 at 1:02 PM, Alan Griffiths
wrote:
> When clients toolkits provide hints to place child surfaces using the
> existing functions:
>
> mir_surface_spec_attach_to_foreign_parent();
> mir_connection_create_spec_for_tip();
>
On Tue, Aug 16, 2016 at 9:55 PM, Alexey Yakovenko <waker...@gmail.com> wrote:
> Hi Thomas
>
> Thanks for replying so quickly! Answering inline. :)
>
And sorry for the high latency now, your reply made it to my spam folder *sigh*
> On Tue, Aug 16, 2016 at 8:56 PM,
** Also affects: gmock (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gmock (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtest in Ubuntu.
** Also affects: gmock (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gmock (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1609989
Public bug reported:
Please see https://github.com/google/googletest/issues/705 for details.
The respective issue mentions two possible solution:
[1.] Make sure that commit
https://github.com/google/googletest/commit/b5c81098a8ccc25e313ffca56c911200b3591ea0
is present in the package.
[2.] Apply
Public bug reported:
Please see https://github.com/google/googletest/issues/705 for details.
The respective issue mentions two possible solution:
[1.] Make sure that commit
https://github.com/google/googletest/commit/b5c81098a8ccc25e313ffca56c911200b3591ea0
is present in the package.
[2.] Apply
We've had multiple reports about location detection being broken with
OTA 12 and we are investigating into the issue.
I will post updates on this thread.
Thanks,
Thomas
On Sat, Jul 30, 2016 at 9:21 PM, Frank Prat wrote:
> Hi all
>
> i've got the same problem on my Meizu pro
On Jul 20, 2016 4:15 PM, "Alan Bell" wrote:
>
> On 15/07/16 14:56, Alberto Mardegan wrote:
>>
>> On 07/15/2016 12:41 PM, Sam Bull wrote:
>>>
>>> The first thing I'd like to see changed, is that the accuracy of
>>> the location should consider the time that has passed since
@Mardy: Any help is welcome :) I think we want to first drop providing
the initial estimate altogether to get this bug fixed asap. We can then
go ahead and investigate whether we want to expose the last known
location to applications.
@Alan: I think it's still an estimate and we should provide
@Mardy: Any help is welcome :) I think we want to first drop providing
the initial estimate altogether to get this bug fixed asap. We can then
go ahead and investigate whether we want to expose the last known
location to applications.
@Alan: I think it's still an estimate and we should provide
@Mardy: Any help is welcome :) I think we want to first drop providing
the initial estimate altogether to get this bug fixed asap. We can then
go ahead and investigate whether we want to expose the last known
location to applications.
@Alan: I think it's still an estimate and we should provide
On Sat, Jul 16, 2016 at 8:25 PM, รัชนันท์ ศรีรัตนเมธ
wrote:
> Hello,
>
> I port Ubuntu Touch to LG L90 Dual which has 1 GB of memory. This means I
> also suffer from all problems about memory people have with BQ Aquaris 4.5.
> Being somewhat experienced with the system, I
1 - 100 of 1312 matches
Mail list logo