** Tags added: samba
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1697817
Title:
disable smb1 by default
To manage notifications about this bug go to:
tests ran: 6, failed: 1;
http://kernel.ubuntu.com/testing/4.8.0-55.58~16.04.1-generic/hainzel__4.8.0-55.58~16.04.1__2017-06-14_09-50-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Internet suggests that all of India is UTC+5:30, and that Jammu and
Kashmir are on India Standard Time.
https://www.timeanddate.com/worldclock/india/srinagar
So, yes, it appears that the installer is setting the wrong timezone for
India if it's setting it to +5 and not +5:30. I've reached out
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: samba (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/1697817
Title:
Hi @wo0dy,
You can verify the bug on Xenial by installing linux-generic-
hwe-16.04-edge=4.10.0.23.16 which is currently on -proposed pocket. This
kernel also have the fix for this bug.
Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
Ceph vendors a specific version of rocksdb, which in the Ceph 12.0.3
release results in a compilation hang on artful i386 only for one of the
objects; The same code using the Xenial gcc-5 compiler does not have
the same issue.
To reproduce (in a i386 chroot):
apt install
Python3-ldb-dev only exists in Xenial - >=Yakkety it got dropped again.
>=Zesty it is a sync again and it never existed in Debian.
This came in via:
ldb (2:1.1.24-1ubuntu3) xenial; urgency=medium
* Build Python3 bindings.
[...]
-- Matthias Klose Thu, 18 Feb 2016 18:17:39
I can confirm that 4.4.0-66 does NOT crash and that 4.4.0-67 does indeed
crash with out of memory errors.
I think I should say that I tried doing a VSS backup with 4.4.0-66 5
times and it didn't crash on any of them but it did log worrying
messages (see attachment) which are very similar to what
** Branch linked: lp:~chromium-team/chromium-browser/trusty-stable
** Branch linked: lp:~chromium-team/chromium-browser/xenial-stable
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1697496
Title:
A view of the whole world with the changes added.
** Attachment added: "bg (1).png"
https://bugs.launchpad.net/ubuntu/+source/libtimezonemap/+bug/1697474/+attachment/4895768/+files/bg%20%281%29.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Tags added: block-proposed
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
tests ran: 141, failed: 2;
http://kernel.ubuntu.com/testing/4.4.0-80.101~14.04.1-generic/archytas__4.4.0-80.101~14.04.1__2017-06-14_09-22-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sorry, forgot above:
#> cat /run/systemd/network/10-netplan-eth0.network
[Match]
Name=eth0
[Network]
DHCP=ipv4
[DHCP]
RouteMetric=100
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1697730
Title:
tests ran: 15, failed: 3;
http://kernel.ubuntu.com/testing/4.8.0-55.58-generic/s2lp4__4.8.0-55.58__2017-06-14_09-47-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/1696365
Image showing just India.
** Attachment added: "timezone_5.5.png"
https://bugs.launchpad.net/ubuntu/+source/libtimezonemap/+bug/1697474/+attachment/4895769/+files/timezone_5.5.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
tests ran: 16, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-55.58-generic/s2lp4__4.8.0-55.58__2017-06-14_09-41-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/1696365
@Matt Hall
This sounds exactly like the issue that this update is trying to
resolve. Can you restart your machine and paste the output from this
command:
apt-cache policy thunar
I just want to be sure that you are running the latest version and that
the old version is no longer in memory.
--
As far as I can see, according to that first link I gave, the area that
is about to be changed to be a part of India in Ubuntu's installer is
UTC+5.
Are we saying that's wrong?
The legal advice is helpful. Can we find a copy of the definitive map
that we're updating to be in line with?
--
You
Ping - Since 2.10 likely will be too late to make 17.10 polling for
related commit ID's for p9 support
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1692447
Title:
[17.10 FEAT] qemu: P9 guest -
Ping - Since 2.10 likely will be too late to make 17.10 polling for
related commit ID's for p9 support
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1692450
Title:
[18.04 FEAT] qemu: P9 guest -
Ping - Since 2.10 likely will be too late to make 17.10 polling for
related commit ID's for p9 support
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1692452
Title:
[17.10 FEAT] qemu: P9 guest -
** Tags removed: bugnameltc-146635 p9-virt-stack severity-medium
ubuntu-18.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1692476
Title:
[18.04 FEAT]: qemu: Enable RDMA support in qemu
To manage
Ping - Since 2.10 likely will be too late to make 17.10 polling for
related commit ID's for p9 support - also this is maybe ~18.04 material.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1692476
Also this might be 18.04 according to the tagging, but if known and
ready please let me know.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1692450
Title:
[18.04 FEAT] qemu: P9 guest - XIVE
tests ran: 3, failed: 1;
http://kernel.ubuntu.com/testing/4.8.0-55.58-generic/s2lp4__4.8.0-55.58__2017-06-14_09-24-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/1696365
Ping - Since 2.10 likely will be too late to make 17.10 polling for
related commit ID's for p9 support
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1692451
Title:
[17.10 FEAT] qemu: P8-Compat mode
tests ran: 141, failed: 0;
http://kernel.ubuntu.com/testing/4.10.0-23.25-generic/gonzo__4.10.0-23.25__2017-06-14_08-50-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/1696369
Public bug reported:
just set up
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-23.25-generic 4.10.17
Uname: Linux 4.10.0-23-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
** Changed in: cloud-archive
Status: New => 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/1655182
Title:
keystone-manage mapping_engine tester problems
To manage notifications
** Patch removed: "keystone-yakkety.debdiff"
https://bugs.launchpad.net/cloud-archive/+bug/1655182/+attachment/4895735/+files/keystone-yakkety.debdiff
** Patch added: "keystone-xenial.debdiff"
Ping - Polling for related commit ID's or libvirt versions for p9
support
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1692421
Title:
[FEATURE] POWER9: libvirt: Updates needed for P8_compat mode
Ping - Polling for related commit ID's or libvirt versions for p9
support
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1690209
Title:
[P9] virsh capabilities does not show certain tags "model",
Must verification/testing be done in Zesty? I have Xenial on my machine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360
Title:
System doesn't boot properly on Gigabyte AM4 motherboards (AMD
Ping - Polling for related commit ID's for p9 support
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1692458
Title:
[17.10 FEAT] libvirt: Add support for PCI multifunction adapter hot
plug/unplug
Ping - Polling for related commit ID's or libvirt versions for p9
support
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1692422
Title:
[17.10 FEAT] POWER9: libvirt: Updates needed for basic P9
** Attachment added: "nautilus-delete-file_glitch1.png"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1697900/+attachment/4895748/+files/nautilus-delete-file_glitch1.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
tests ran: 6, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-55.58~16.04.1-generic/secchi__4.8.0-55.58~16.04.1__2017-06-14_09-00-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Glitch in the "Delete" button (see the attached screenshots).
** Affects: ubuntu-themes (Ubuntu)
Importance: Undecided
Status: New
** Tags: artful
** Tags added: artful
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks Breno, since I wait on a bunch of other commits this isn't worked on yet.
To be sure this is the only commit needed for this specific case right?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ping - Since 2.10 likely will be too late to make 17.10 polling for
related commit ID's for p9 support
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1692444
Title:
[17.10 FEAT] qemu: P8-Compat mode
tests ran: 10, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-55.58~16.04.1-generic/hainzel__4.8.0-55.58~16.04.1__2017-06-14_08-23-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ping - Since 2.10 likely will be too late to make 17.10 polling for
related commit ID's for p9 support
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1692443
Title:
[17.10 FEAT] qemu: P9 guest - RPT
tests ran: 20, failed: 0;
http://kernel.ubuntu.com/testing/4.10.0-23.25~16.04.1-generic/rumford__4.10.0-23.25~16.04.1__2017-06-14_08-26-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "nautilus-delete-file_glitch2.png"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1697900/+attachment/4895749/+files/nautilus-delete-file_glitch2.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I had an analogous problem. Mariadb install, I create the users, I import the
data and everthing is ok.
I reboot the computer and mysql dous not start.
In the logs I found
● mysql.service - LSB: Start and stop the mysql database server daemon
Loaded: loaded (/etc/init.d/mysql; bad; vendor
** Patch added: "keystone-yakkety.debdiff"
https://bugs.launchpad.net/cloud-archive/+bug/1655182/+attachment/4895735/+files/keystone-yakkety.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
As bug 1677730 demonstrates, this is also a bug that renders the
mapping_engine command unusable on stable/newton and stable/mitaka.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655182
Title:
** Description changed:
+ [Impact]
+
+ * A bug in keystone-manage tool prohibits the use of the mapping_engine
+ command for testing federation rules.
+
+ * Users of Keystone Federation will not be able to verify their mapping
+ rules before pushing these to production.
+
+ * Not being able
I'm unable to reproduce this bug:
$ lsusb
Bus 001 Device 004: ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS 802.11n
Wireless Network Adapter
...
$ uname -a
Linux raspi3 4.8.0-1033-raspi2 #36 SMP Tue Jun 13 11:24:42 UTC 2017 armv7l
armv7l armv7l GNU/Linux
probably due to the slightly
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag
** Description changed:
- [Impact]
-
- * A bug in keystone-manage tool prohibits the use of the mapping_engine
- command for testing federation rules.
-
- * Users of Keystone Federation will not be able to verify their mapping
- rules before pushing these to production.
-
- * Not being able
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag
Sorry about the noise in this bug, further process is tracked in bug
1655182
** Tags removed: sts sts-sru-needed
** No longer affects: keystone (Ubuntu)
** Patch removed: "keystone-yakkety.debdiff"
** No longer affects: cloud-archive
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1677730
Title:
keystone-manage mapping_engine is broken: TypeError
To manage notifications about this bug go to:
** Changed in: ubuntu-power-systems
Status: Fix Committed => 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/1676679
Title:
datapath: Add missing case OVS_TUNNEL_KEY_ATTR_PAD
To
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag
** Changed in: ubuntu-power-systems
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1690225
Title:
nvidia-docker on ppc64le-ubuntu16.04 issue due to cross-thread
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag
Public bug reported:
Different title bar size (see the attached screenshots).
** Affects: ubuntu-themes (Ubuntu)
Importance: Undecided
Status: New
** Tags: artful
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-55.58-generic/s2lp4__4.8.0-55.58__2017-06-14_08-58-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/1696365
** Attachment added: "gnome-software_nonglitch.png"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1697898/+attachment/4895733/+files/gnome-software_nonglitch.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "gnome-software_glitch.png"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1697898/+attachment/4895732/+files/gnome-software_glitch.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag
Hi everybody,
with this being an issue for so long but nobody than "us" (=canonical STS +
canonical Dev) caring I wonder if we should even switch that on again - since
it is also disabled upstream intentionally as Serge reported.
The question is if users that want/need it can enable it.
So I
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag
@fnordahl having just realised that the patch you are backporting is
from another bug I'm afraid I'll have to ask you to stick to our usual
process for submitting SRUs i.e. always use the LP bug that the patch is
actually associated with. Please also ensure that all of the following
are extant in
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag
501 - 600 of 704 matches
Mail list logo