The kernel in comment #7 pass our SMEP/SMAP test and doesn't generate
regression.
--
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/1520427
Title:
drm/fbdev: Return -EBUSY when oopsing
St
** Tags removed: verification-needed-wily
--
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/1517942
Title:
Backport upstream commit to Ubuntu 15.10 (Wily) SRU stream
Status in linux packag
tests ran: 87, failed: 36;
http://kernel.ubuntu.com/testing/4.3.0-2.11/kili__4.3.0-2.11__2015-12-09_02-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.
https://bugs.launchpad.net/bugs/1522958
T
Bumping this 7 days before expiration. Hope to find some time during
the holidays to investigate further.
--
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/1504829
Title:
[Lenovo ThinkPad
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
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/1524167
Title:
Computer freezes since 15.10 u
Public bug reported:
Machine freezes randomly. No crash logs or anything in syslog. Not
enough know-how to figure it out.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: linux-image-4.2.0-21-generic 4.2.0-21.25
ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6
Uname: Linux 4.2.0-21-gen
Public bug reported:
package linux-firmware 1.149 failed to install/upgrade: unable to create
'/lib/firmware/brcm/bcm4329-fullmac-4.bin.dpkg-new' (while processing
'./lib/firmware/brcm/bcm4329-fullmac-4.bin'): Permission denied But I
was sudo
ProblemType: Package
DistroRelease: Ubuntu 15.10
Packa
> "BTW, Since Ubuntu 15.04's "
typo.. 15.04 -> 15.10.
--
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/1470250
Title:
[Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based
B
@f-bosch @jsalisbury
I can reproduce the issue consistently within 5~6 hours with a Ubuntu 15.10 VM.
In /var/log/syslog, several minutes before the file system is remounted
as read-only, the hv_vss_daemon has stopped working: the daemon just
always hangs on the poll() , not receiving freeze/thaw
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1524122/+attachment/4531712/+files/ProcEnviron.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages
apport information
** Tags added: apport-collected wily
** Description changed:
Neither 4.4rc3 nor 4.3rc4 will boot on my Dell XPS 15 (9550). 4.3 boots
fine.
The boot process halts with "ALERT! /dev/disk/by-uuid/ does not
exist", although the UUID does exist, and other kernels boot f
Daniel Holm, if you boot into a 3.19.x kernel is this still
reproducible?
** Tags removed: bios-outdated-r1044v7
** Tags added: latest-bios-r1044v7 regression-release
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1524122
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 commen
Public bug reported:
Neither 4.4rc3 nor 4.3rc4 will boot on my Dell XPS 15 (9550). 4.3 boots
fine.
The boot process halts with "ALERT! /dev/disk/by-uuid/ does not
exist", although the UUID does exist, and other kernels boot fine.
I'm attaching a screenshot of the console boot log. I apologize
Somehow I missed the step where I rename it, though I see it now with
the word "Important" in front of it in your instructions. Working great
now! Thanks so much!
So can a script be made that grabs (wgets) the drivers from the broadcom
website and extracts the right one? Would that be legal? Maybe
See this?
BCM: Patch brcm/BCM.hcd not found
You need to convert the firmware and copy it as
/lib/firmware/brcm/BCM.hcd
2015-12-09 1:00 GMT+03:00 Josiah Raiche :
> I've just tried it with my wife's phone and it cannot see other devices
> or be seen by them.
>
> I think you're right about the firmw
** Changed in: linux (Ubuntu)
Importance: Undecided => High
--
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/1524069
Title:
Xenial KVM: updating Trusty guest from 3.13.0-68 to 3.13.0-71
I've just tried it with my wife's phone and it cannot see other devices
or be seen by them.
I think you're right about the firmware. Do I need to rename the .hcd
file?
$ dmesg | grep -i blue
[7.220345] toshiba_bluetooth: Toshiba ACPI Bluetooth device driver
[9.324633] Bluetooth: Core ver
I just tried again with two logical CPUs and the core set to "Westmere"
(I think that was the default), and didn't see the bug. So this seems
related specifically to "[x] Copy host CPU configuration" being checked.
Here's the /proc/cpuinfo from the "virtual Westmere" where it works:
http://paste.u
Unfortunately, I don't have them anymore as I had to delete them to make
space for upgrades.
--
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/1512482
Title:
Keyboard and touchpad malfuncti
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/1524069
Title:
Xenial KVM: updating Trusty gu
I got this error on my HP Notebook 15-ac131ne (i3-5005U) with Ubuntu
Gnome 15.10 freshly installed. Errors show just before login prompt. I
can log in to my desktop after that.
[26255.192670] [drm:gen8_irq_handler [i915]] *ERROR* The master control
interrupt lied (SDE)!
[26255.194650] [drm:gen8_i
** Tags added: kernel-key
--
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/1524069
Title:
Xenial KVM: updating Trusty guest from 3.13.0-68 to 3.13.0-71 causes
kernel exception
Status in
For what it's worth, unchecking "[ ] Copy host CPU configuration" in
virt-manager and selecting "Hypervisor default" for the CPU is a
workaround. (/proc/cpuinfo reports "QEMU Virtual CPU version 2.4.0")
--
You received this bug notification because you are a member of Kernel
Packages, which is su
Also, the hypervisor's /proc/cpuinfo reports the following CPU
configuration (8 cores of the same):
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 60
model name : Intel(R) Core(TM) i7-4710MQ CPU @ 2.50GHz
stepping: 3
microcode : 0x1e
cpu
Also, I've found a final workaround that gives 0% losses and a stable
connection.
For me it was 3.13.0-37 kernel and a _downgraded_ driver with version
6.30.223.141+bdcom-0ubuntu2
** Also affects: bcmwl (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification
Public bug reported:
The symptom I saw was this (note the segfault, and apt-get upgrade hangs
after this):
Setting up linux-image-3.13.0-71-generic (3.13.0-71.114) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
Examining /etc/kernel/postinst.d.
run-parts: execu
Knowing that this bug is in progress, I want to share an interesting
finding (at least for me).
I am on rc-proposed (with bluez5, see details below). When SIM 1 is
(randomly picked) used, the battery status is shown in the car display.
When SIM 2 is used, the battery status shows 100% loading.
sy
** Changed in: linux-lts-vivid (Ubuntu Trusty)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-armadaxp in Ubuntu.
https://bugs.launchpad.net/bugs/1509565
Title:
CVE-2015-7885
Status in linux p
** Changed in: linux-lts-vivid (Ubuntu Trusty)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-armadaxp in Ubuntu.
https://bugs.launchpad.net/bugs/1520184
Title:
CVE-2015-8104
Status in linux p
** Description changed:
The key_gc_unused_keys function in security/keys/gc.c in the Linux
kernel through 4.2.6 allows local users to cause a denial of service
(OOPS) via crafted keyctl commands.
Break-Fix: - f05819df10d7b09f6d1eb6f8534a8f68e5a4fe61
- Break-Fix: - 911b79cde95c7da0ec02f4
I see the same error message when I try the following:
* laptop is in docking station, external monitor is connected
* send laptop to sleep
* undock laptop
* wake laptop up
The error message is present on the terminal, my KDE session is logged out.
Nothing useful in .xsession-errors though.
The
** Changed in: linux-lts-vivid (Ubuntu Trusty)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-armadaxp in Ubuntu.
https://bugs.launchpad.net/bugs/1508329
Title:
CVE-2015-7799
Status in linux p
** Changed in: linux-lts-vivid (Ubuntu Trusty)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-armadaxp in Ubuntu.
https://bugs.launchpad.net/bugs/1509564
Title:
CVE-2015-7884
Status in linux p
** Description changed:
This bug is for tracking the 3.13.0-73.116~precise1 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:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
kerne
** Description changed:
This bug is for tracking the 3.19.0-41.46 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:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
kernel-stable-P
** Description changed:
This bug is for tracking the 3.13.0-73.116 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:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
kernel-stable-
upstream bug report:
https://bugzilla.kernel.org/show_bug.cgi?id=108581
** Bug watch added: Linux Kernel Bug Tracker #108581
http://bugzilla.kernel.org/show_bug.cgi?id=108581
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ub
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
--
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/1522918
Title:
linux: 3.19.0-41.46 -proposed
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-trusty in Ubuntu.
https://bugs.launchpad.net/bugs/1522991
Title:
linux-lts-trusty:
Thanks for the update, Martin.
** Tags removed: kernel-key
--
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/1523586
Title:
[PPA] 4.4 regression: kernel panic on reboot
Status in linux pa
Still not working on 4.4.0-040400rc4-generic
** Attachment added: "dmesg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1518570/+attachment/4531573/+files/dmesg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
h
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
--
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/1522858
Title:
linux: 3.13.0-73.116 -propose
Yes, it is a regression. Andy found the offending commit and the fix is
already queued in Tejun's tree, so this should get fixed with the next
upstream update.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
Would it be possible for you test test the latest mainline kernel, to
see if the memory leak happens there as well? It can be downloaded
from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4-rc4-wily/
--
You received this bug notification because you are a member of Kernel
Packages, which is
I built the next test kernel, up to the following commit:
c0c3a718e3ab2430a52a60d614b109e5e48e83e2
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1516547
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on y
I built a Vivid test kernel with the backport from Andy Whitcroft. The
test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1520427/
Can you test this kernel and see if it resolves this bug?
Thanks in advance!
--
You received this bug notification because you are a membe
*** This bug is a duplicate of bug 1346917 ***
https://bugs.launchpad.net/bugs/1346917
Hi,
could you please file a new bug with debugging information as per
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1346917/comments/11
?
--
You received this bug notification because you are a mem
Rebuilding as linux-lts-vivid (3.19.0-41.46~14.04.2). The .1 package
was accidentally build without a .orig tarball.
** Summary changed:
- linux-lts-vivid: 3.19.0-41.46~14.04.1 -proposed tracker
+ linux-lts-vivid: 3.19.0-41.46~14.04.2 -proposed tracker
** Description changed:
- This bug is for
It looks like you already submitted an SRU request, so please ignore
comment #4. And it looks like apw has performed the backport for #5.
--
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/152
Commit c50bfd08 does not pick cleanly in the Vivid(3.19) kernel. The
3.19 kernel does not have intel_fbdev_blank() or
intel_fbdev_pan_display(). intel_fbdev_blank() was added by commit
03e515f7 in v4.1-rc1. intel_fbdev_pan_display() was added by commit
d9a946b5 in v4.2-rc1.
Can you confirm whe
Thanks for the update. I will submit an SRU request for that commit.
** Changed in: linux (Ubuntu Xenial)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.ne
This issue appears to be an upstream bug, since you tested the latest
upstream kernel. Would it be possible for you to open an upstream bug
report[0]? That will allow the upstream Developers to examine the issue,
and may provide a quicker resolution to the bug.
Please follow the instructions on th
Thanks for the update, Miguel. Would you be able to test the kernel
posted in comment #9?
--
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/1501281
Title:
Frequent freezes on 15.04 with ke
The above working patch has been merged in linux-4.1.y branch of linux-
stable repository as can been seen here:
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-
stable.git/log/?qt=grep&q=mmc%3A+core%3A+Enable+runtime+PM+management+of+host+devices&h=linux-4.1.y
Since Ubuntu 15.10 comes w
tests ran: 1, failed: 1;
http://kernel.ubuntu.com/testing/4.2.0-21.25/kili__4.2.0-21.25__2015-12-08_12-53-00/results-index.html
--
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/1522108
Is this a regression with the 4.4 kernel? Do you happen to know if the
panic occurred with prior kernels as well?
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Tags added: kernel-key xenial
** Also affects: linux (Ubuntu Xenial)
Importance: High
Status: Confirmed
Is this regression between the 4.3 and 4.4 kernels? Do you have a way
to install test kernels to test this? If so, I can perform a kernel
bisect to identify the exact commit that caused this.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
*** This bug is a duplicate of bug 1346917 ***
https://bugs.launchpad.net/bugs/1346917
Same problem
I using kernel 3.16.0-55-generic, Ubuntu 14.04
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
We'll test the kernel in -proposed right away. 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/1509029
Title:
[Hyper-V] Crash in hot-add/remove scsi devices (smp)
Status in linux
** Tags removed: verification-needed-trusty verification-needed-vivid
** Tags added: verification-done-preciseverification-done-vivid
** Tags removed: verification-done-preciseverification-done-vivid
verification-needed-precise
** Tags added: verification-done-precise verification-done-vivid
--
We'll test the kernel in -proposed right away. 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/1294283
Title:
Memory balloning in Hyper-V generation 2 does not work
Status in lin
Works as expected in 3.19.0-41.46.
** Tags removed: verification-needed-vivid
** Tags added: verification-done-vivid
--
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/1519106
Title:
Unpriv
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
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/1514785
Title:
kernel 3.16.0.52+53 - ip rule repeats all default rul
We'll test the kernel in -proposed right away. 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/1508593
Title:
[Hyper-V] x86/ioapic: Disable interrupts when re-routing legacy IRQs
Always occurs randomly when I click in some web link but not related
with website visited. Occurs about one time at day. I only use Google
Chrome as browser.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.lau
Running 3.13.0-73-generic #116-Ubuntu and am able to unlock the
encrypted drive.
--
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/1522766
Title:
cryptsetup hangs after kernel upgrade to 3.
** 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.
https://bugs.launchpad.net/bugs/1522766
Title:
cryptsetup hangs after kernel upgrade 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-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from tod
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 tod
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 today
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 t
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 tod
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 today
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 tod
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 today
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 tod
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 t
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 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 tod
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 t
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 today
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 tod
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 today
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 today
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 today
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 tod
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 t
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 today
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 tod
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 tod
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 tod
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 t
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 today
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 t
1 - 100 of 151 matches
Mail list logo
