The OAuth keys for Google are defined in EDS itself (src/modules/ubuntu-
online-accounts/google-*.service.in.in). They were registered by me, but
I gave access to them to the EDS developers themselves (though I suspect
that it was still at the time when Matthew Barnes was the lead developer
- I'm
Thanks Daniel! This indeed looks like a bug on our side. But I'm
surprised that no one else has reported it, so I suspect that somehow
your device got itself into a wrong state.
I need to ask you one more information, and this might be a bit harder
to collect. I'd like you to use "phablet-shell"
** Changed in: systemd (Debian)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to init-system-helpers in
Ubuntu.
https://bugs.launchpad.net/bugs/1575572
Title:
apache2 fails to start
OTA14 does not changed anything here.
I can also upload videos to show the different behaviors on MX4 and Pro5.
If you need any help i can do, let me know.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in
[Expired for lightdm (Ubuntu) because there has been no activity for 60
days.]
** Changed in: lightdm (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
@jbicha, I would make updates to all 3 series quickly to introduce that
fix, but it would be really nice to have an 1.2.4 update because it's
been long waited (without postponing to wait for other series). What do
you think?
--
You received this bug notification because you are a member of
All the listed test cases appear to have been covered and successfully
verified for both xenial and yakkety. We're just waiting for Jason to do
his testing (he said "tomorrow" Friday December 16...). If that gets
done then, the updates should be good to release on Monday (there aren't
usually SRU
Milestoning, since we should try to not drop the ball on this bug; I
will need to revisit the mailing list thread and how exactly we do the
naming for these devices.
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
** Changed in: systemd (Ubuntu)
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 th
The resolvconf portion of this issue has been moved to bug #1649931.
I'm removing resolvconf 1.78ubuntu3 from xenial-proposed and will
replace it with a resolvconf 1.78ubuntu4 with the correct bug ref.
** Changed in: resolvconf (Ubuntu Xenial)
Status: Fix Committed => Invalid
** Changed
Hello Ryan, or anyone else affected,
Accepted resolvconf into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/resolvconf/1.78ubuntu4 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
** Changed in: resolvconf (Ubuntu Yakkety)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
>> For systemd portion, we carry the
>> systemd-networkd-resolvconf-update.service as a delta from Debian
> I'm not sure what you mean here; the systemd package in zesty is currently
> in sync with Debian.
Ok, it appears that post-16.04, systemd-networkd-resolvconf-
update.service is dropped
So vim.gtk3 crashes consistently for all Ubuntu users on Unity desktop?
Is anyone still working on a fix?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1611363
Title:
Invalid for GTK. I have now reproduced the same bug using a pure Mir
demo (which is software rendered in case that's relevant):
$ mir_demo_client_progressbar 20 --desktop_file_hint=unity8
** Changed in: ubuntu
Status: Confirmed => Invalid
** Summary changed:
- [regression] resizing a
Also the bug does not exist in Mir demo servers.
This is just a QtMir/Unity8 bug.
--
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/1649662
Title:
[regression] resizing a some
Confirmed. The bug has now escaped proposed and is in zesty.
** Changed in: canonical-devices-system-image
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gtk+3.0 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
** Summary changed:
- resizing a gtk+3/mir app makes it unusable - pixels get stretched and input
stops working
+ [regression] resizing a gtk+3/mir app makes it unusable - pixels get
stretched and input stops working
--
You received this bug notification because you are a member of Ubuntu
** Tags removed: unity-desktop
** Tags added: unity8-desktop
--
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/1650022
Title:
We need a "close" action for killing an app in a
** Changed in: isc-dhcp (Ubuntu Xenial)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
** Changed in: initramfs-tools (Ubuntu Xenial)
Milestone: None => xenial-updates
** Changed in: initramfs-tools (Ubuntu Xenial)
Assignee: (unassigned) => Mathieu Trudel-Lapierre
On Thu, Dec 15, 2016 at 09:43:48PM -, Ryan Harper wrote:
> I don't disagree (that saying few folks impacted means low).
> This portion was split out from the previous systemd SRU
> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1636912
> in which the changes were classified in the
** Also affects: bamf (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates in Ubuntu.
https://bugs.launchpad.net/bugs/1650419
Title:
package ca-certificates
resolvconf (1.79ubuntu4) zesty; urgency=medium
* debian/resolvconf.service: Add missing Wants=network-pre.target.
-- Martin Pitt Thu, 08 Dec 2016 10:21:12
+0100
resolvconf (1.79ubuntu3) zesty; urgency=medium
* debian/resolvconf.service: resolvconf service must
Hello Ryan, or anyone else affected,
Accepted resolvconf into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/resolvconf/1.78ubuntu3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
On Thu, Dec 15, 2016 at 09:44:32PM -, Ryan Harper wrote:
> On Thu, Dec 15, 2016 at 10:27 PM, Brian Murray wrote:
> > How is this fixed in the development release?
> For systemd portion, we carry the
> systemd-networkd-resolvconf-update.service as a delta from Debian
I'm
** No longer affects: ubuntu-gnome
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1649960
Title:
Apport fails to upload some crash reports
Status in Apport:
New
Status
sorry while upgrading from ubuntu 16.04 LTS to 16.10
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates in Ubuntu.
https://bugs.launchpad.net/bugs/1650419
Title:
package ca-certificates 20160104ubuntu1 failed
Public bug reported:
while upgrading from ubuntu 16.04 LTS to 60.10
ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: ca-certificates 20160104ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture:
On 15/12/16 17:25, Steve Langasek wrote:
> This was a known limitation when the SRU went through, and it was
> allowed because the understood target for snapd on 14.04 was
> server/cloud environments, not desktops. Has that changed?
It's unexpected for me, and will be substantially difficult to
This fix made it into Yakkety and Zesty, but not Xenial. I've uploaded
a fix to the Xenial SRU queue for review by the Ubuntu SRU team.
** Also affects: nano (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: nano (Ubuntu Xenial)
Status: New => In Progress
**
All non-MAAS remote rootfs -based test cases have been verified for
Yakkety now. Everything checks out. I will now do the last test case
remaining which is to do a standard (non-remote root) install and
upgrade to proposed packages to make sure standard installs aren't
broken.
** Description
Final review feedback has been incorporated into initramfs-tools, isc-
dhcp, and open-iscsi, and uploaded to zesty.
** Description changed:
initramfs' configure_networking function uses ipconfig to configure the
network.
ipconfig does not support dhcpv6. See:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: alsa-driver (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
zesty has 12.0.4, and 13.0.2 in proposed, closing
** Summary changed:
- Mesa 12.0.4 - multiple important fixes, stable branch
+ Mesa 12.0.5 - multiple important fixes, stable branch
** Description changed:
[Impact]
- Mesa 12.0.4 is now available as a point release in the stable branch. Mesa
You can run the scope with U1_DEBUG=1 set, and it will spew more debug
info.
I doubt it's threads. We're not using QtDBus here really. The ubuntu-
download-manager code does use it, but we're no longer really using it
in the scope, only the client object gets created on startup, and then
never
** Description changed:
For some reason I often find that if I try to report a .crash (which the
GUI for some reason didn't alert me about) file this will happen (this
happens with all the Apport tools to report a crash, this just so
happens to be the apport-cli example):
-
*** Send
Thank you for taking the time to report this bug and helping to make
Ubuntu better. In an effort to keep an up-to-date list of bugs to work I
have reviewed this report to verify it still requires a fix and it
occurs on a supported version of Ubuntu.
Can you please let us know if this is still
d-i install with proposed enable also passed. As far as I am concerned,
this is verification-done for *Xenial*.
We may still want to wait for Jason DeRose's input on the SRU.
** Description changed:
initramfs' configure_networking function uses ipconfig to configure the
network.
ipconfig
I do not believe there is any path to successfully install snapd on a
14.04 desktop system. Only one of systemd and systemd-shim can own the
systemd dbus services; systemd doesn't implement them in a way that will
work with upstart as pid1, which means we need systemd-shim to own them
so that the
Attached is a debdiff for a SRU for trusty.
** Patch added: "initramfs-tools_0.103ubuntu4.5_0.103ubuntu4.6.debdiff"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1496163/+attachment/4792198/+files/initramfs-tools_0.103ubuntu4.5_0.103ubuntu4.6.debdiff
** Description changed:
This bug was fixed in the package apport - 2.20.4-0ubuntu1
---
apport (2.20.4-0ubuntu1) zesty; urgency=medium
* New upstream release:
- SECURITY FIX: Restrict a report's CrashDB field to literals.
Use ast.literal_eval() instead of the generic eval(), to prevent
Yeah, please see lxc_cgroup_debug_outputs.txt file for all outputs and
lxc config.
** Attachment added: "lxc_cgroup_debug_outputs.txt"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1649582/+attachment/4792203/+files/lxc_cgroup_debug_outputs.txt
--
You received this bug notification
2GB :o)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1649605
Title:
webbrowser crashes are not reported
Status in Canonical System Image:
New
Status in
but i get crash reports for chrome, and chromes om nom noms the RAM
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1649605
Title:
webbrowser crashes are not
** Changed in: snappy
Status: New => Confirmed
** Changed in: snappy
Importance: Undecided => Critical
** Changed in: systemd (Ubuntu)
Importance: Undecided => Critical
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because
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
I’m occasionally seeing that when I run webbrowser-app in a VirtualBox VM.
Never seen it on my work laptop, but that one has 16GB, which is plenty.
How much memory overall does your system have?
** Changed in: webbrowser-app (Ubuntu)
Status: New => Incomplete
--
You received this bug
** Bug watch added: Debian Bug tracker #847440
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847440
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1649931
Title:
On Thu, Dec 15, 2016 at 10:27 PM, Brian Murray wrote:
> How is this fixed in the development release?
>
For systemd portion, we carry the
systemd-networkd-resolvconf-update.service as a delta from Debian
Ryan
--
You received this bug notification because you are a member of
On Thu, Dec 15, 2016 at 10:27 PM, Brian Murray wrote:
> How is this fixed in the development release?
>
There is an upstream resolvconf bug that addresses that package portion:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847440
> Also the having a "Regression
*** This bug is a duplicate of bug 1648842 ***
https://bugs.launchpad.net/bugs/1648842
** This bug has been marked a duplicate of bug 1648842
[Regression] Switching between two windows of the same app using quick swipe
from right edge breaks focus
--
You received this bug notification
How is this fixed in the development release?
Also the having a "Regression Potential" of low just because not a lot
of people use the service is wrong. A bad change could still horribly
impact the users of the software, regardless of how many users there
are.
** Changed in: resolvconf (Ubuntu)
** Changed in: server-papercuts
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/622431
Title:
iptables rules are not saved across reboots
I run into this problem after upgrade from Ubuntu 14.04 to Ubuntu 16.04
All suggested solutions didn't work well for me. But I found another very
simple one.
I found the obsolete file in my home directory:
/home/current_user/.config/autostart/polkit-gnome-authentication-agent-1.desktop
After
Assuming you are using Unity Greeter, please shout out if not correct.
** Package changed: lightdm (Ubuntu) => unity-greeter (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
Hello Jeremy, or anyone else affected,
Accepted evolution-data-server into yakkety-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/evolution-data-server/3.22.3-0ubuntu0.1 in a few hours, and then in the
-proposed repository.
Please help us by
"After installing the update, restart your computer. (Is there a flag
evolution-data-server should set to prompt the user to do this?)"
There is documentation in update-notifier's HOOKS file about this:
Another example is the reboot notification. Packages like the kernel,
glibc, dbus and hal
Public bug reported:
Video failure during mp4 (.avi) reading. Recurrent concern.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
Uname: Linux 4.4.0-53-generic x86_64
.tmp.unity_support_test.0:
ApportVersion:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: modemmanager (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to modemmanager in Ubuntu.
** Changed in: winff (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 cups in Ubuntu.
https://bugs.launchpad.net/bugs/1616548
Title:
Cups causes LibreOffice unittests to
I've done all the non-MAAS test cases on xenial so far except for
completing an installation with proposed enabled (it's a little more
complicated); things are working as expected. I removed the "Booting an
iSCSI remote root via IPv6 (no ip6=, d-i use case)" as it makes no sense
-- d-i will not
** Description changed:
initramfs' configure_networking function uses ipconfig to configure the
network.
ipconfig does not support dhcpv6. See:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164
Related bugs:
* bug 1229458: grub2 needed changes
* bug 1621615: network not
I've accepted a new version of open-iscsi in yakkety, but the SRU tools
barfed on modifying the bug.
** Changed in: open-iscsi (Ubuntu Yakkety)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
The Test Case is rather incomplete for an SRU. Could you add some
information about how the changes will be tested and we will ensure
there are no regressions?
Thanks!
** Changed in: mesa (Ubuntu Yakkety)
Status: Confirmed => Incomplete
--
You received this bug notification because you
** Changed in: gdb (Ubuntu)
Milestone: ubuntu-17.02 => None
** Changed in: gdb (Ubuntu)
Assignee: Matthias Klose (doko) => Taco Screen team (taco-screen-team)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in
Completely broke my 16.04 to 16.10 upgrade. Really bad. Thankfully I
backed the VM up.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gconf in Ubuntu.
https://bugs.launchpad.net/bugs/1551623
Title:
package gconf2
** Patch added: "xenial-dns-before-online-target-lp1649931.debdiff"
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1649931/+attachment/4792126/+files/xenial-dns-before-online-target-lp1649931.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch
** Description changed:
Currently resolvconf and systemd-networkd don't ensure DNS has been
configured before allowing network-online.target to be reached.
This was discussed in https://launchpad.net/bugs/1636912 however it was
not a regression since there aren't any users of networkd
This is blocked by the fact that 4.2.0 is stuck in zesty-proposed.
** Changed in: zeromq3 (Ubuntu Yakkety)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zeromq3 in Ubuntu.
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1650354
Title:
system error on login after a power button reboot becuase
Public bug reported:
i started the update my Lubuntu version to the latest version i waited
for the update to finish while i was doing a few other things.. i had
to get done to not disturb the computer... after the auto-restart .. i
went to the power menu to shut down .. both that and the reboot
Hello Stéphane, or anyone else affected,
Accepted lxc into trusty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/lxc/1.0.9-0ubuntu1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Stéphane, or anyone else affected,
Accepted lxc into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/2.0.6-0ubuntu1~ubuntu16.04.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Changed in: resolvconf (Debian)
Status: New => Fix Committed
--
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/1636912
Title:
systemd-networkd runs too late for
Hello Stéphane, or anyone else affected,
Accepted lxc into yakkety-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/2.0.6-0ubuntu1~ubuntu16.10.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
This bug was fixed in the package vim - 2:8.0.0095-1ubuntu2
---
vim (2:8.0.0095-1ubuntu2) zesty; urgency=medium
* ubuntu-series-support.patch: Drop vivid and wily from supported
list.
-- Adam Conrad Tue, 06 Dec 2016 03:03:48 -0700
** Changed in: vim
Please attach the container config file and show or attache the output
of the following commands:
- grep cgroup /proc/1/mountinfo
- cat /proc/self/cgroup
- ls -al /sys/fs/cgroup
- lxcfs --version
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
The real cause here is we rely on focusOut(In)Event to check for
activeFocus item. but the any check of ActiveFocus (hasActiveFocus or
window->activeFocusItem) inside focusout/in event give incorrect result.
when another item is focused(location bar), window->activeFocusItem()
return null not the
Hello,
I am fighting exactly with the same problem. Is there any workaround?
Thanks
BR
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1606600
Title:
Yes.
$ apt-cache policy libpam-cgfs
libpam-cgfs:
Installed: 2.0.4-0ubuntu1~ubuntu16.04.1
Candidate: 2.0.4-0ubuntu1~ubuntu16.04.1
Version table:
*** 2.0.4-0ubuntu1~ubuntu16.04.1 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
100
@caribou
@rbasak
Let me share the work (since rbasak seems to like the approach) I've
done so far on my above recent proposal :
isc-dhcp-client: dhclient with DDNS functionality enabled
isc-dhcp-client-noddns : dhclient with DDNS functionality disabled
This is a working debdiff, I think
** Also affects: ubuntu-ux
Importance: Undecided
Status: New
--
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/1650022
Title:
We need a "close" action for killing
The attachment "xenial_resolvconf-lp1649931.diff" seems to be a debdiff.
The ubuntu-sponsors team has been subscribed to the bug report so that
they can review and hopefully sponsor the debdiff. If the attachment
isn't a patch, please remove the "patch" flag from the attachment,
remove the
** Patch added: "xenial_resolvconf-lp1649931.diff"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1649931/+attachment/4792030/+files/xenial_resolvconf-lp1649931.diff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Description changed:
Impact
==
Some bugs in evolution-data-server (e-d-s) were causing daily limit errors
for those using Google services with evolution-data-server and apps that use it
(Evolution is a prominent example). Unfortunately, it looks like users using
older versions of
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
Ok, a bit more info, copying from
https://bugzilla.gnome.org/show_bug.cgi?id=771547#c62
--
The internal Google OAuth2 authentication had been introduced in eds 3.20.0
(thus it's pretty new), for which I released eds 3.20.6 with all the yet-known
fixes recently, in a hope that distros which
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
1 - 100 of 167 matches
Mail list logo