I have prepared a git branch to place 2.0.2 into xenial
https://code.launchpad.net/~juju-qa/ubuntu/+source/juju-core/+git/juju-core/+ref/xenial-2.0.2
This branch imported juju 2.0.2 and updated d/copyright and d/changelog.
Note that I see a warning that there are no translations for the
On Linux Mint Serena 18.1 (based on Xenial 16.04.1)
When the unmount does not happen, I can see this kind of lines in my syslog:
(...) umount.ecryptfs: Failed to find key with sig [deadbeefdeadbeef]:
Required key not available
** Also affects: ecryptfs
Importance: Undecided
Status: New
Sorry, the info was already provided by OP. For some reason I failed to
read that lines :-(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1595469
Title:
Logout umounts encrypted home only every
Hello NKStudio, or anyone else affected,
Accepted virtualbox-ext-pack into yakkety-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/virtualbox-ext-pack/5.1.6-2ubuntu1 in a few hours, and then in the
-proposed repository.
Please help us by testing
Hello NKStudio, or anyone else affected,
Accepted virtualbox-ext-pack into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/virtualbox-ext-pack/5.0.24-0ubuntu1.16.04.2 in a few hours, and then in
the -proposed repository.
Please help us by
@LocutusOfBorg - Your description would have been much more helpful if
you had actually referenced 5.1.6 (the one you changed) instead of
5.0.24 (the one in the description).
** Tags added: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
The "broken widget rendering" is a manifestation of how GTK3 handles
HiDPI. GTK3 doesn't natively scale at 1/8 increments, so Unity's
scaling is working around that by messing with the size of text and
widgets.
To give you an idea, I'm attaching a screenshot of the same window as
rendered at 1x
I guess you meant the updated Ubuntu package based on
freeimage/3.17.0+ds1-4, right? When is it going to be available?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1614266
Title:
Freeimage library
tests ran: 5, failed: 1;
http://kernel.ubuntu.com/testing/4.4.0-57.78-lowlatency/onza__4.4.0-57.78__2016-12-15_14-02-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1648867
tests ran: 33, failed: 5;
http://kernel.ubuntu.com/testing/3.19.0-78.86-generic/dwalin__3.19.0-78.86__2016-12-15_17-10-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1647787
I appreciate the effort in providing a solution to this problem.
But, as I came to know, the "make link" is not really missing from
Nautilus, but just disable by default.
All it takes is getting into Nautilus Preferences > Behavior (tab) and
check the box for "Link Creation". After that,
Thanks for uploading the fix for this bug report to -proposed. However,
when reviewing the package in -proposed and the details of this bug
report I noticed that the bug description is missing information
required for the SRU process. You can find full details at
tests ran: 35, failed: 5;
http://kernel.ubuntu.com/testing/4.4.0-57.78-lowlatency/onibi__4.4.0-57.78__2016-12-15_13-37-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1648867
I have prepared a git branch to place 2.0.2 into yakkety
https://code.launchpad.net/~juju-qa/ubuntu/+source/juju-core/+git/juju-core/+ref/yakkety-2.0.2
This branch imported juju 2.0.2 and updated d/copyright and d/changelog.
** Patch added: "debdiff of juju-core_2.0.0-0ubuntu0.16.10.3.dsc
Hello Carlos, or anyone else affected,
Accepted usb-modeswitch into yakkety-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/usb-
modeswitch/2.2.5+repack0-1ubuntu1.1 in a few hours, and then in the
-proposed repository.
Please help us by testing this
Hello zeine77, or anyone else affected,
Accepted virt-manager into yakkety-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/virt-
manager/1:1.3.2-3ubuntu3.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Reading this changelog as an SRU team member I find it really unhelpful
if not confusing.
+ * Cherry-pick commit 10a62408 from Debian unstable to resolve
+incompatibility with systemd (>= 230-1~) (LP: #1639607).
Using the words "cherry-pick" and then dropping a patch:
+++
** Changed in: ubuntu-z-systems
Importance: Medium => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1650300
Title:
ubuntu-installer/partman does not properly detect partitions on FBA
Yawn.
Bug opened in June and we're now December !
I cannot comprehend why it takes Ubuntu such an inordinate amount of
time to get a bug fixed that was already fixed in the underlying release
!
16.04 has been such a bug-ridden release, just rushed out with little
QA. I'm getting rid of Ubuntu
--- Comment From vmor...@us.ibm.com 2016-12-15 12:23 EDT---
An observation:
Having Cinder and Nova-compute on the same host, and using LVM and iSCSI
backends might be causing some race conditions in multipath.
The syslog is littered with messages like this:
Nov 23 03:17:47 ub01
This ticket is a replacement to LP 1578232 which was a bit screwed up
...
** Package changed: linux (Ubuntu) => parted (Ubuntu)
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Importance: Undecided => Medium
** Changed in:
** Changed in: parted (Ubuntu)
Importance: Undecided => High
** Changed in: parted (Ubuntu)
Assignee: Skipper Bug Screeners (skipper-screen-team) => Dimitri John
Ledkov (xnox)
** Changed in: parted (Ubuntu)
Milestone: None => ubuntu-17.01
--
You received this bug notification
tests ran: 16, failed: 3;
http://kernel.ubuntu.com/testing/3.19.0-78.86-generic/modoc__3.19.0-78.86__2016-12-15_17-09-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1647787
This issue was fixed in the openstack/nova 15.0.0.0b2 development
milestone.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/832507
Title:
console.log grows indefinitely
To manage notifications
This issue was fixed in the openstack/nova 15.0.0.0b2 development
milestone.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1639239
Title:
ValueError for Invalid InitiatorConnector in s390
To
Public bug reported:
Steps to reproduce:
1. In Nautilus, navigate to a folder containing some XML file
2. Right-click on a .xml file
3. Click or hover on "open with"
Expected: in the list of applications in the submenu, Gedit should be listed
once and only once
Observed: it is listed twice.
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
Hello Tommy, or anyone else affected,
Accepted pcs into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/pcs/0.9.149-1ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Tommy, or anyone else affected,
Accepted pcs into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/pcs/0.9.149-1ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Description changed:
- 1.10.2 was released a week ago.
+ 1.10.2 was released back in October.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1636593
Title:
Please update nginx for Xenial,
Hello Jonathan, or anyone else affected,
Accepted pcs into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/pcs/0.9.149-1ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Jonathan, or anyone else affected,
Accepted pcs into yakkety-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/pcs/0.9.153-2ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Description changed:
Only with a workaround I can install Ubuntu 32-bit on a UEFI machine:
- First install Ubuntu 64-bit on a temporary partition.
- Then install Ubuntu 32-bit with ubiquity -b
- Start Ubuntu 64-bit and run update-grub.
- Start Ubuntu 32-bit.
To make Ubuntu
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
Bugs, which is
Public bug reported:
Please add file system efivarfs to 32-bit Linux kernel, so on EFI machine
following command could be executed:
sudo mount -t efivarfs efivarfs /sys/firmware/efi/efivars
See also: bug 1648278
** Affects: linux-lts-xenial (Ubuntu)
Importance: Undecided
Status:
Public bug reported:
>From https://bugs.launchpad.net/ubuntu/+source/ubuntu-
docs/+bug/1573025/comments/5
> Screenshots add to the maintenance burden, and the desktop guide only
contains a few screenshots. We simply don't have the resources to
include screenshots everywhere.
This is very
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1606600
Title:
dpkg-reconfigure unattended-upgrades results in
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 Falk, or anyone else affected,
Accepted swift into yakkety-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/swift/2.10.0-0ubuntu1.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Falk, or anyone else affected,
Accepted swift into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/swift/2.7.0-0ubuntu2.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
*** This bug is a duplicate of bug 1635280 ***
https://bugs.launchpad.net/bugs/1635280
** This bug has been marked a duplicate of bug 1635280
[ BUG 541595 IS BACK ] package is already installed and configured
--
You received this bug notification because you are a member of Ubuntu
Bugs,
*** This bug is a duplicate of bug 1635280 ***
https://bugs.launchpad.net/bugs/1635280
** This bug has been marked a duplicate of bug 1635280
[ BUG 541595 IS BACK ] package is already installed and configured
--
You received this bug notification because you are a member of Ubuntu
Bugs,
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
*** This bug is a duplicate of bug 1635280 ***
https://bugs.launchpad.net/bugs/1635280
** This bug is no longer a duplicate of bug 1649438
package libbrlapi0.6:amd64 5.3.1-2ubuntu2.1 failed to install/upgrade:
package libbrlapi0.6:amd64 is already installed and configured
** This bug has
Public bug reported:
Installer crashes after clicking Continue on Prepare page.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: ubiquity 16.10.14
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: amd64
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1650336
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a
Public bug reported:
On (K)ubuntu 16.04.01 (Xenial) Upgrading to kernel 4.4.0-57 the kernel
crash on boot when in /etc/fstab a nfsv4 entry is active
When comment the line or set to noauto the kernel boot with no error and
mounting the nfs shares (after uncomment ) is also possible without
error
i am not an ubuntu maintainer, i only take care of the debian side of
things - you'll have to find some Ubuntu person to followup here...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1594222
Title:
This is madness. A lot of sites are cut, like amazon, and others. I
tried the version 55 from staging but it doesn't work properly yet
(sites like amazon and youtube and up in "aw snap!"). Anyone knows when
to expect a fix?
--
You received this bug notification because you are a member of Ubuntu
** Changed in: keepalived (Ubuntu)
Assignee: Nish Aravamudan (nacc) => (unassigned)
** Changed in: keepalived (Ubuntu Xenial)
Assignee: Nish Aravamudan (nacc) => (unassigned)
** Changed in: keepalived (Ubuntu Yakkety)
Assignee: Nish Aravamudan (nacc) => (unassigned)
--
You
Public bug reported:
.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: jayatana 2.7-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-51.72-generic 4.4.30
Uname: Linux 4.4.0-51-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
AptOrdering:
spotify-client: Install
jayatana: Configure
** Changed in: kernel-sru-workflow/security-signoff
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/1649361
Title:
linux-hwe-edge: 4.8.0-32.34~16.04.1 -proposed
tests ran: 19, failed: 4;
http://kernel.ubuntu.com/testing/3.19.0-78.86-generic/modoc__3.19.0-78.86__2016-12-15_16-01-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1647787
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/certification-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in:
@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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1650022
Title:
We need a "close" action for killing an app in a trust prompt
To
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: unity (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/1634335
Title:
1
The following packages ended up in the wrong component in the -proposed
pocket:
linux-hwe-edge 4.8.0-32.34~16.04.1 - is in main instead of universe
block-modules-4.8.0-32-generic-di 4.8.0-32.34~16.04.1 - is in main instead of
universe
block-modules-4.8.0-32-generic-di 4.8.0-32.34~16.04.1 - is in
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/certification-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in:
We'll update NGINX in Zesty, but I'm marking Won't Fix for Xenial and
Yakkety at this time. I'm not willing to push uploads at this time to
Xenial or Yakkety without clearing it with the Server and SRU teams, and
a much higher priority is to get Zesty complete.
We'll be uploading 1.10.2 shortly
Public bug reported:
during the installation of grub error occured saying grub could not be
installed
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.63.2 [modified:
lib/partman/automatically_partition/question]
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname:
This bug was fixed in the package libspectre - 0.2.7-2ubuntu1.2
---
libspectre (0.2.7-2ubuntu1.2) trusty; urgency=medium
* Replace fix-document-rotation.patch with new version from 0.2.8.
This fixes a regression introduced in 0.2.7-2ubuntu1.1 where some
eps files are mostly
The verification of the Stable Release Update for libspectre has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
...because of it I now got 6 'pending' payments in my Ubuntu one
account. Any chance to revoke them?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1647850
Title:
Paypal page hide behing Loading box
Ok,
your kernel 4.4.0.54.75... boots and works with no permission error :)
For the kernel crash i will create a new bug report.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649292
Title:
NFS
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
@Daniele, no, that's not it. Google Chrome and Chromium behave
differently, on same version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641380
Title:
chromium-browser:
This bug was fixed in the package keepalived - 1:1.2.23-1ubuntu0.1
---
keepalived (1:1.2.23-1ubuntu0.1) yakkety; urgency=medium
* debian/patches/fix_message_truncation_with_large_pagesizes.patch:
Resolve "Netlink: error: message truncated" messages. Thanks to
David Wilder
** 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
And for uboot:
ubuntu@ubuntu:~$ dpkg -l | grep u-boot
ii u-boot-rpi:armhf 2016.01+dfsg1-2ubuntu2 armhf
A boot loader for Raspberry PI systems
ii u-boot-tools 2016.01+dfsg1-2ubuntu2 armhf
companion tools for Das U-Boot
** 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
Bugs, which is subscribed to Ubuntu.
The verification of the Stable Release Update for keepalived has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
@arges
Looks like the yakkety SRU has been forgotten.
** Tags removed: verification-needed
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1634304
Title:
Public bug reported:
In Ubuntu 16.10, the "Make Link" command is missing from the right click
Nautilus menu.
Please attribute this bug to the correct module, gedit was used to
trigger the ubuntu-bug process.
Thanks.
more info at: https://answers.launchpad.net/ubuntu/+question/404047
Is here still a problem left with upstream QEMU?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/897750
Title:
libvirt/kvm problem with disk
Sorry, didn't update the bug report. It is already fixed:
https://review.openstack.org/#/c/335421/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1583524
Title:
nova-lxd doesn't create the VLAN
tests ran: 33, failed: 5;
http://kernel.ubuntu.com/testing/3.19.0-78.86~14.04.1-generic/dwalin__3.19.0-78.86~14.04.1__2016-12-15_15-09-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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
.
I have the same problem, but the original cause seems to be an
IndexError in decompressor.py. Also, half a GB of temporary files is
left behind. Attaching a session demonstrating all this:
** Attachment added: "Session showing problem"
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
I have prepared a git branch to place 2.0.2 into zesty
https://code.launchpad.net/~juju-qa/ubuntu/+source/juju-core/+git/juju-core/+ref/zesty-2.0.2
This branch imported juju 2.0.2 and updated d/copyright and d/changelog.
I had some misadventure with gbp import-orig because the ubuntu repo
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 does not sound like a QEMU bug, so let's remove it from the QEMU
bug tracker
** No longer affects: qemu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/712416
Title:
kvm_intel kernel module
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
.
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
.
301 - 400 of 644 matches
Mail list logo