** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Description changed:
This bug is for tracking the 3.2.0-1668.93 upload package. This bug will
contain status and testing results related to that upload.
For an explanation of the tasks and the
BQ E5 OTA 11
Now working with Jabra Freeway v 3.3
Call in
Call out
Speaks out the phone number of inbound call
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1435040
Title:
Ubuntu
Hi Tim Passingham (tim-8aw3u04umo),
the new kernel you installed (4.4.0-24) will definitely produce the issue as it
does not contain the patch.
Please clarify if you where also able to reproduce the issue with
4.4.0-22-generic #40+lp1579190.
--
You received this bug notification because you
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Chris J Arges
(arges)
--
You received this bug notification because you are a
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Chris J Arges
(arges)
--
You received this bug notification because you are a
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Hardware Enablement ARM Kernel
(canonical-hwe-arm-kernel) => Ike Panhc (ikepanhc)
--
You received this bug notification
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1591289
Title:
linux: 4.4.0-25.44
Yes, exactly that, I can no longer reproduce it with the current system
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1589997
Title:
The device on /dev/sdx is not created when
Hi Tim Passingham (tim-8aw3u04umo),
you are not using the patched kernel.
The patched is: 4.4.0-22-generic #40+lp1579190
And you are using: 4.4.0-24
What might have happened is that you installed the patched kernel and then you
updated Ubuntu and 4.4.0-24 was installed and set as the default
Now I can not resolve this problem.
I use another Wi-Fi+BT card.
But may be my story will be usefull for future work with problem.
I have Acer TM B113-E which complected with Broadcom Corporation BCM43228
Wi-Fi+BT card.
With older kernels(3.11) it works fine. But when I began upgrade kernel,
4.4.0-24-generic #43-Ubuntu SMP just failed for me as well.
I had installed it a few days ago and it was OK, but just went wild
again with repeating 5's. It may be a coincidence, but I
also was using Thunderbird at the time.
I shall revert to the patched version.
--
You received
I can confirm that this is still an issue in Ubuntu 14.04.4. I ran into
this problem trying to backup a server hosting lxc containers, some of
them using overlayfs as the root fs. When the containers are running
(and therefore overlayfs is mounted) lvcreate -s hangs forever. The
debug output is:
Sorry, I should have explained better. I was using the patched kernel,
with no problems. When the 24 update came up for installation a few
days ago I thought I would try it, so I did. Today that newer version
still showed the same problem, so I have reverted to the patched version
(by using
hi Christoper,
OK, will do, but it may not be until next weekend.
cheers
Tom
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1576909
Title:
[Acer Aspire V3-472G] Suspend not working on
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Chris J Arges
(arges)
--
You received this bug notification because you are a
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Chris J Arges
(arges)
--
You received this bug notification because you are a
As I said, "I was using the patched kernel, with no problems". I was
away for a few days so have probably only run 4.4.0-22-generic
#40+lp1579190 for 4 or 5 days in all, so far without seeing the problem,
but it is transient.
4.4.0-24 didn't display the fault for a couple of days, and then did
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Chris J Arges
(arges)
--
You received this bug notification because you are a
@faulpeltz, yes sorry that test kernel was for vivid. Thanks for
testing an narrowing it down further.
I did build a Utopic 3.16 based kernel now. It has commit 89fb4cd1f7
reverted. It can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1470250/revert-and-bisect/utopic/
Can you
Patch has been accepted in upstream, commit ID
e1f00c87f75d6f739aaf50958db26cd357d68797
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1590655
Title:
[Hyper-V] storvsc messages for
*** This bug is a duplicate of bug 1572659 ***
https://bugs.launchpad.net/bugs/1572659
Public bug reported:
Hi this could be the package causing the bug. I am not sure, when I ran
the bug report on it it seemed to produce the attached info all by
iteself so I am asusming some of it is
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Chris J Arges
(arges)
--
You received this bug notification because you are a
** Changed in: kernel-sru-workflow
Assignee: (unassigned) => Ike Panhc (ikepanhc)
** Changed in: kernel-sru-workflow/regression-testing
Assignee: Canonical Kernel Team (canonical-kernel-team) => Ike Panhc
(ikepanhc)
** Changed in: kernel-sru-workflow/verification-testing
** Changed in: turbo
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1590844
Title:
Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition
Status
tests ran: 10, failed: 1;
http://kernel.ubuntu.com/testing/3.2.0-105.146/cavac__3.2.0-105.146__2016-06-14_12-20-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 10, failed: 1;
http://kernel.ubuntu.com/testing/3.2.0-105.146/dagmar__3.2.0-105.146__2016-06-14_12-16-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Testing with a JBL SB400 BT on a Lenovo Thinkpad T450S with the intel
ibt driver on F/W version 37081001103110e23 works correctly.
Doing a parallel test on my laptop (HP evo 850) that has :
[12383.666088] Bluetooth: hci0: read Intel version: 370710018002030d00
[12383.666095] Bluetooth: hci0:
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Chris J Arges
(arges)
--
You received this bug notification because you are a
Public bug reported:
Execute xchg %ax,%ax after finishing the running funtion.
Here is content of perf report:
native_apic_mem_write /proc/kcore
│ ▒
│
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1592369
Title:
On function
tests ran: 10, failed: 1;
http://kernel.ubuntu.com/testing/3.2.0-105.146/alkaid__3.2.0-105.146__2016-06-14_12-13-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 10, failed: 1;
http://kernel.ubuntu.com/testing/3.2.0-105.146/phact__3.2.0-105.146__2016-06-14_12-13-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 10, failed: 1;
http://kernel.ubuntu.com/testing/3.2.0-105.146/onibi__3.2.0-105.146__2016-06-14_12-13-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 10, failed: 1;
http://kernel.ubuntu.com/testing/3.2.0-105.146/onza__3.2.0-105.146__2016-06-14_12-14-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hi Christopher
I've followed your recommendations and installed the latest bios found
on the HP database corresponding to my "HP Envy x360 15-w100nf" PC.
Actually I'm a bit disappointed because no change, sorry ! anyway, here
is the result of your command
1) $ sudo dmidecode -s bios-version &&
We've also been running into this issue on ScalingStack instances
recently; I got this traceback which seems to strongly implicate nohz as
the problem area: https://pastebin.canonical.com/158640/ Presently
testing @pitti's workaround on a number of different sized instances to
confirm.
--
You
Same behaviour on v4.7-rc1. Tested on different PC as 4.7 doesn't even
boot on my laptop.
** Tags added: kernel-bug-exists-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is
Yes it is. The prior version that I got is 102. There's no 103?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1592131
Title:
Trouble with USB drives
Status in linux package in Ubuntu:
Thanks for handling the bug.
What's next ? Any idea when the fix will be avail in the main kernel ?
Thanks,
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1560142
Title:
No space left
Public bug reported:
After pop%rbp is running instructions:
Bellow is result of perf report:
│
◆
│
Jacob Fenton, the next step is to fully reverse commit bisect from
kernel 4.4 to 4.7-rc3 in order to identify the last bad commit, followed
immediately by the first good one. Once this good commit has been
identified, it may be reviewed for backporting. Could you please do this
following
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1592381
Title:
On function mutex_unlock
Here's the relevant information:
precise linux 3.2.0-105.146 REGR summary
Please verify test results in http://people.canonical.com/~kernel/status
/adt-matrix/overall.txt
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in:
linux-lts-vivid| 3.19.0-62.70~14.04.1 | trusty-proposed | source
linux-meta-lts-vivid | 3.19.0.62.45 | trusty-proposed | source
linux-signed-lts-vivid | 3.19.0-62.70~14.04.1 | trusty-proposed | source
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: In
linux-lts-utopic| 3.16.0-74.96~14.04.1 | trusty-proposed | source
linux-meta-lts-utopic | 3.16.0.74.65 | trusty-proposed | source
linux-signed-lts-utopic | 3.16.0-74.96~14.04.1 | trusty-proposed | source
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: In
linux| 3.13.0-89.136 | trusty-proposed | source
linux-meta | 3.13.0.89.95 | trusty-proposed | source
linux-signed | 3.13.0-89.136 | trusty-proposed | source
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: In Progress => Fix Committed
--
You received this
linux-ti-omap4 | 3.2.0-1483.110 | precise-proposed | source
linux-meta-ti-omap4 | 3.2.0.1483.78 | precise-proposed | source
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of
linux| 3.19.0-62.70 | vivid-proposed | source
linux-meta | 3.19.0.62.60 | vivid-proposed | source
linux-signed | 3.19.0-62.70 | vivid-proposed | source
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: In Progress => Fix Committed
--
You received this
linux-lts-trusty| 3.13.0-89.136~precise1 | precise-proposed | source
linux-meta-lts-trusty | 3.13.0.89.81 | precise-proposed | source
linux-signed-lts-trusty | 3.13.0-89.136~precise1 | precise-proposed | source
** Changed in: kernel-sru-workflow/promote-to-proposed
linux | 3.2.0-105.146 | precise-proposed | source
linux-meta| 3.2.0.105.121 | precise-proposed | source
linux-backports-modules-3.2.0 | 3.2.0-105.97 | precise-proposed | source
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: In
linux| 4.2.0-39.46 | wily-proposed| source
linux-meta | 4.2.0.39.42 | wily-proposed| source
linux-signed | 4.2.0-39.46 | wily-proposed| source
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: In Progress => Fix Committed
--
You received this
** Tags added: bugnameltc-123025 severity-medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1534144
Title:
[Ubuntu 16.04] CORSA CAPI enabling in PowerVM LPARs
Status in linux
tests ran: 2, failed: 0;
http://kernel.ubuntu.com/testing/3.2.0-105.146/alkaid__3.2.0-105.146__2016-06-14_13-45-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 10, failed: 1;
http://kernel.ubuntu.com/testing/3.2.0-105.146/dagmar__3.2.0-105.146__2016-06-14_13-10-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 2, failed: 0;
http://kernel.ubuntu.com/testing/3.2.0-105.146/phact__3.2.0-105.146__2016-06-14_13-43-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 2, failed: 0;
http://kernel.ubuntu.com/testing/3.2.0-105.146/onibi__3.2.0-105.146__2016-06-14_13-39-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 10, failed: 1;
http://kernel.ubuntu.com/testing/3.2.0-105.146/cavac__3.2.0-105.146__2016-06-14_13-11-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in 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-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
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-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
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-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from
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-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
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-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
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-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
linux-armadaxp | 3.2.0-1668.93 | precise-proposed | source
linux-meta-armadaxp | 3.2.0.1668.84 | precise-proposed | source
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of
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-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
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-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
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-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
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 verification is not done by 5 working days from
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 verification is not done by 5 working days from
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/3.2.0-105.146/alkaid__3.2.0-105.146__2016-06-14_14-08-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in 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-
wily' to 'verification-done-wily'.
If verification is not done by 5 working days from
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-
precise' to 'verification-done-precise'.
If verification is not done by 5 working days
tests ran: 10, failed: 1;
http://kernel.ubuntu.com/testing/3.2.0-105.146/alkaid__3.2.0-105.146__2016-06-14_12-58-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 10, failed: 1;
http://kernel.ubuntu.com/testing/3.2.0-105.146/phact__3.2.0-105.146__2016-06-14_12-57-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in 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-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
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 verification is not done by 5 working days from
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 verification is not done by 5 working days from
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 verification is not done by 5 working days from
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 verification is not done by 5 working days from
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 verification is not done by 5 working days from
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 verification is not done by 5 working days from
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 verification is not done by 5 working days from
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-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from
Verifications have been done, the bug is corrected!
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in 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-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from
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 verification is not done by 5 working days from
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-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from
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 verification is not done by 5 working days from
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-
wily' to 'verification-done-wily'.
If verification is not done by 5 working days from
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 verification is not done by 5 working days from
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-
wily' to 'verification-done-wily'.
If verification is not done by 5 working days from
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 verification is not done by 5 working days from
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 verification is not done by 5 working days from
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 verification is not done by 5 working days from
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 verification is not done by 5 working days from
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-
wily' to 'verification-done-wily'.
If verification is not done by 5 working days from
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 verification is not done by 5 working days from
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 verification is not done by 5 working days from
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 verification is not done by 5 working days from
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 verification is not done by 5 working days from
1 - 100 of 238 matches
Mail list logo
