** Also affects: linux-oracle (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1820075
Title:
[Packaging] Improve config
attaching copy of syslog from moment of error
** Attachment added: "syslog.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841132/+attachment/5284119/+files/syslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1841132
and then change the status of the bug to 'Confirmed'.
If, due to the
Error "Couldn't get size: 0x800e" has resurfaced despite of
the released fix. I found this error in latest Ubuntu 18.04 install.
Release fix needs to be re-evaluated.
$ dmesg
.
[0.933031] Loading compiled-in X.509 certificates
[0.934003] Loaded X.509 cert 'Build time
Public bug reported:
[summary]
when a server running ubuntu 18.04 with an lsi sas controller experiences high
disk io there is a chance the storage controller will reset
this can take weeks or months, but once the controller resets it will keep
resetting every few seconds or few minutes,
How do I add the tag verification-done-disco ?
** Tags added: verification-done-disco
** Tags removed: verification-needed-disco
--
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/1837136
** Changed in: linux (Ubuntu Eoan)
Status: Triaged => 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/1838133
Title:
realtek r8822be kernel module fails after update
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/1840882
Title:
[SRU][B-OEM-OSP1/D/E] reduce s2idle power
Hmm, how come this was marked as verification-needed-xenia?
--
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/1812796
Title:
TRACE_syscall.ptrace_syscall_dropped in seccomp from
Yes, I am using Kubuntu 18.04.
--
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/1824575
Title:
Can't boot Thinkpad T540 it's on docking station
Status in linux package in Ubuntu:
1. It appears nobody requested this fix for xenial so I wouldn't expect
anyone interested in testing it.
2. I can't see the bug ID documented in any proposed xenial kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
To test: intel_idle.max_cstate=4
1. Edit /etc/default/grub and add it to the line
GRUB_CMDLINE_LINUX_DEFAULT=...
2. sudo update-grub
3. Reboot.
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
This issue is not for xenial. Removing tag.
** Tags removed: verification-needed-xenial
--
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/1830587
Title:
Reduce NAPI weight in hns driver
https://launchpad.net/ubuntu/+source/linux-hwe/4.15.0-59.66~16.04.1
** Also affects: linux-hwe (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-hwe (Ubuntu)
Status: New => Fix Released
** No longer affects: linux-hwe (Ubuntu Bionic)
** No longer affects:
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
packages:
You upgrade the BIOS on your machine?
The DMI info is changed? From:
Base Board Information
Manufacturer: AMI Corporation
Product Name: Cherry Trail CR
Version: Default string
to
Base Board Information
Manufacturer: AMI Corporation
Product Name: Cherry
@ Ryan we do not test Xenial or Disco
On Thu, Aug 22, 2019 at 7:41 PM Ryan Harper <1784...@bugs.launchpad.net>
wrote:
> Finally, I did verify xenial proposed with our original test. I had
> over 100 installs with no issue.
>
> @Jason
>
> Have you had any runs on Xenial or Disco? (or do you not
Finally, I did verify xenial proposed with our original test. I had
over 100 installs with no issue.
@Jason
Have you had any runs on Xenial or Disco? (or do you not test those)?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Also, I had some confusion earlier about what kernel I was testing.
apt-cache policy shows the package version 4.15.0.59.61, however that's
the meta package, the actual kernel is the .66 one.
# dpkg --list | grep linux-image
ii linux-image-4.15.0-59-generic 4.15.0-59.66
I've adjusted my bionic testing with the simpler configuration. I
cannot reproduce the failure so far. I'll leave this running over
night.
I suspect there's something else going on baremetal that we can't
reproduce in a VM.
--
You received this bug notification because you are a member of
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
I have found something that changes the state of the flickering. I tried to
plug in a thunderbolt to hdmi display and while the machine didn't output
to the display, the flickering stopped. I found that if I plugged in the
display while flickering was occurring the flickering would stop and once I
I'm not sure how to boot with this setting, could I get more
information?
On Wed, Aug 14, 2019 at 2:50 PM Timo Aaltonen
wrote:
> does booting with intel_idle.max_cstate=4 help?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
>
** Changed in: kernel-sru-workflow/automated-testing
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/promote-to-release
Status: New => Confirmed
** Tags removed: block-proposed-eoan
** Tags removed: block-proposed
** Description changed:
This bug will
No, not similar. I get no messages on the screen. And the messages
recorded by the other user seem different from messages which I can see
in my syslog file. In my case the computer is not completely dead (there
are messages in the syslog file which confirm that e.g. WiFi connection
is activated),
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
** Summary changed:
- bionic/linux-aws: -proposed tracker
+ bionic/linux-aws: 4.15.0-1047.49 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
packages:
** Changed in: linux (Ubuntu Eoan)
Status: Confirmed => 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/1841110
Title:
Eoan update: v5.2.9 upstream stable release
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
packages:
Public bug reported:
[Impact]
The 3rd party nvidia driver fails to load on arm64 systems.
[Test Case]
sudo modprobe nvidia
On failure:
[ 812.512205] nvidia: loading out-of-tree module taints kernel.
[ 812.512216] nvidia: module license 'NVIDIA' taints kernel.
[ 812.512218] Disabling lock
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
packages:
** Changed in: linux (Ubuntu Bionic)
Status: Fix Committed => New
--
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/1784665
Title:
bcache: bch_allocator_thread(): hung task timeout
I will note that sometimes, restarting network-manager doesn't work,
especially if I have put the machine to sleep prior to trying to access
the network. Here's a dmesg where it did come back after network-manager
restart.
** Attachment added: "dmesg.txt"
** Attachment added: "spinda.maas-curtin_config.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784665/+attachment/5284072/+files/spinda.maas-curtin_config.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
We're still seeing a bcache timeout failure during curtin install
2019-08-22T10:16:40+00:00 spinda
cloud-init[1604]: finish:
cmd-install/stage-partitioning/builtin/cmd-block-meta/clear-holders: FAIL:
removing previous storage devices
2019-08-22T10:16:40+00:00 spinda cloud-init[1604]:
Further to my previous comment, I have now tested the following
additional mainline kernels from https://kernel.ubuntu.com/~kernel-
ppa/mainline/?C=N;O=D
4.16.0-041600rc1-generic
4.15.18-041518-generic
4.15.17-041517-generic
The bug does not occur when running these kernels.
** Changed in:
Public bug reported:
I am running Openstack Ansible Rocky 18.1.8 on Ubuntu 18.04 nodes. I use
PCI-passthrough (IOMMU vfio) on GTX1080Tis and and RTX2080Tis. The 1080s
work fine, but 2080 instances take anywhere from 3 minutes to over 3
hours to start with qemu/KVM and the amount of time varies
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1841098
and then change the status of the bug to 'Confirmed'.
If, due to the
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1841070/+attachment/5284069/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: kernel-sru-workflow/automated-testing
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1841070/+attachment/5284068/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1841070/+attachment/5284070/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1841070/+attachment/5284067/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1841070/+attachment/5284058/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1841070/+attachment/5284060/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1841070/+attachment/5284057/+files/CRDA.txt
--
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/1841070
apport information
** Tags added: apport-collected
** Description changed:
Regression: My laptop has become unable to enter S3 sleep/suspend.
(A.K.A. Suspend to RAM) It seems to go through all the motions,
including shutting down network interfaces and stopping the hard disk,
but fails
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1841070/+attachment/5284061/+files/Lspci.txt
--
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/1841070
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1841070/+attachment/5284062/+files/Lsusb.txt
--
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/1841070
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1841070/+attachment/5284066/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1841070/+attachment/5284065/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1841070/+attachment/5284063/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1841070/+attachment/5284064/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "HookError_generic.txt"
https://bugs.launchpad.net/bugs/1841070/+attachment/5284059/+files/HookError_generic.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
packages:
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1840820
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1841070
and then change the status of the bug to 'Confirmed'.
If, due to the
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
** Summary changed:
- disco/linux-aws: -proposed tracker
+ disco/linux-aws: 5.0.0-1014.16 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Committed
** Changed in: kernel-sru-workflow/prepare-package
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-lrm
Status: In Progress => Fix Committed
**
** Description changed:
Regression: My laptop has become unable to enter S3 sleep/suspend.
(A.K.A. Suspend to RAM) It seems to go through all the motions,
including shutting down network interfaces and stopping the hard disk,
but fails at the last moment and immediately starts back up
$ reverse-depends -b -r xenial libseccomp-dev
Reverse-Build-Depends
=
* golang-github-seccomp-libseccomp-golang
* lxc
* ocserv
* qemu
* systemd
* tor
* ubuntu-core-launcher
none of these appear to reference pkey_mprotect, so none should need a
rebuild with the xenial-hwe
I have tested the following mainline kernels from
https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D
5.3.0-050300rc5-generic
4.15.1-041501-generic
4.15.0-041500-generic
The bug does not occur when running these kernels.
** Package changed: linux-meta-hwe (Ubuntu) => linux (Ubuntu)
--
You
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-gcp 5.0.0-1015.15~18.04.1 - is in universe instead of
restricted
linux-modules-nvidia-390-5.0.0-1015-gcp 5.0.0-1015.15~18.04.1 - is in universe
instead of restricted
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/regression-testing
Status: New => Confirmed
** Changed in:
You have been subscribed to a public bug:
Regression: My laptop has become unable to enter S3 sleep/suspend.
(A.K.A. Suspend to RAM) It seems to go through all the motions,
including shutting down network interfaces and stopping the hard disk,
but fails at the last moment and immediately starts
** Changed in: linux (Ubuntu Bionic)
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/1840932
Title:
[Regression] failed to compile seccomp
** Changed in: linux (Ubuntu Bionic)
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/1840935
Title:
[Regression] net test from
*** This bug is a duplicate of bug 1840806 ***
https://bugs.launchpad.net/bugs/1840806
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
- derivatives: bug 1839978
Public bug reported:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
packages:
lrm:
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
- derivatives: bug 1839976
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
- backports: bug 1840001
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
- https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-
- backports: bug 1839996
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
- derivatives: bug 1840672
** Summary changed:
- linux-aws: -proposed tracker
+ bionic/linux-aws: -proposed tracker
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
+
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
packages:
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
- https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
+
** Summary changed:
- linux: -proposed tracker
+ bionic/linux: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
-
*** This bug is a duplicate of bug 1841086 ***
https://bugs.launchpad.net/bugs/1841086
** This bug has been marked a duplicate of bug 1841086
linux: -proposed tracker
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
** Also affects: linux-aws-hwe (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-aws-hwe (Ubuntu Artful)
Status: New => Invalid
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux-aws (Ubuntu Xenial)
** Summary changed:
- bionic/linux: -proposed tracker
+ bionic/linux: 4.15.0-60.67 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team
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
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
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
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
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
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
1 - 100 of 246 matches
Mail list logo
