Can confirm this issue on my Dell XPS 9560. I downloaded iso of ubuntu
16.04 made it bootable and i tried to boot into installation menu but i
got stuck on loading screen, before it showed up error with noveau and
cant create kernel channel, 22. Any fix please.
--
You received this bug notificati
*** This bug is a duplicate of bug 1708499 ***
https://bugs.launchpad.net/bugs/1708499
You filed same bug not long ago... Please check my comment.
** This bug has been marked a duplicate of bug 1708499
usb 3-1: 2:1: cannot get freq at ep 0x1
--
You received this bug notification because
Okay, so the touchscreen issue is unrelated to touchpad. I'll send a
patch to enable the touchpad.
Also, Mark said the touchscreen works on 4.13-rc4 in comment #45. Can
you attach `dmesg` on 4.13-rc4 and 4.13-rc4?
If this is a regression, you need to find the last working mainline
kernel and the
Find the Lenovo section:
###
# Lenovo
###
# thinkpad_acpi driver
evdev:name:ThinkPad Extra Buttons:dmi:bvn*:bvr*:bd*:svnLENOVO*:pn*
KEYBOARD_KEY_01=mute
KEYBOARD_KEY_02=battery
KEYBO
Okay, so the touchscreen issue is unrelated to touchpad. I'll send a
patch to enable the touchpad first.
Also, Mark said the touchscreen works on 4.13-rc4 in comment #45. Can
you attach `dmesg` on 4.13-rc4?
--
You received this bug notification because you are a member of Kernel
Packages, which
** Also affects: ubuntu-power-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-power-systems
Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)
** Changed in: ubuntu-power-systems
Importance: Undecided => High
--
You received this bug notifi
** Tags removed: verification-needed-xenial verification-needed-zesty
** Tags added: verification-done-xenial verification-done-zesty
--
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/1693673
[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
--- Comment From md...@us.ibm.com 2017-08-16 23:08 EDT---
Split op operations do not fail with HTX when testing with proposed fix.
** Tags removed: verification-needed-xenial verification-needed-zesty
** Tags added: verification-done-xenial verification-done-zesty
--
You received this bu
hmm ok
looks like you will have to remove that broken package first,
try to remove it with the dpkg command
sudo dpkg --remove --force-remove-reinstreq linux-
image-4.10.0-23-generic
>From a similar thread on askubuntu, see if it helps
https://askubuntu.com/questions/889126/package-linux-image-4
We have another case of OOM at one of the host that we upgraded kernel
to 4.4.0-89 a week ago.
kern.log attached.
** Attachment added: "Kern log attached."
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842/+attachment/4934013/+files/kern-log-kernel4.4.0-89.txt
--
You received th
Attaching dmesg output
** Attachment added: "dmesg-kernel4.4.0-89.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842/+attachment/4934014/+files/dmesg-kernel4.4.0-89.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to l
4.4.0-93.116 can fix the Bluetooth firmware loading issue for 8087:0a2b.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.lau
Back from holidays, so here is the list of options for the arm64 kernel .config.
I copied your list from above and changed the options accordingly, adding
comments with explanations. Let me know if you need more information.
CONFIG_ARCH_SUNXI=y
# CONFIG_AHCI_SUNXI is not set ## no SATA
Public bug reported:
---Problem Description---
A vhost performance patch was introduced in the 4.10 kernel upstream, and is
currently included in the Zesty 4.10 kernel:
commit 809ecb9bca6a9424ccd392d67e368160f8b76c92
Author: Jason Wang
Date: Mon Dec 12 14:46:49 2016 +0800
vhost: cache us
You have been subscribed to a public bug:
---Problem Description---
A vhost performance patch was introduced in the 4.10 kernel upstream, and is
currently included in the Zesty 4.10 kernel:
commit 809ecb9bca6a9424ccd392d67e368160f8b76c92
Author: Jason Wang
Date: Mon Dec 12 14:46:49 2016 +0800
--- Comment From mauri...@br.ibm.com 2017-08-16 20:09 EDT---
Hi Indira,
Can you please test whether this test kernel fixes the problem?
http://dorno.rch.stglabs.ibm.com/~mauricfo/kernel/linux-
hwe-4.10.0-330_4.10.0-330.37~16.04.1+bz156441/
Thanks,
Mauricio
--
You received this bug noti
Neither touch screen nor touchpad works :(
--
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/1658345
Title:
Touchpad not recognized on Lenovo Ideapad Flex 4 running Ubuntu 16.10
Status in
--- Comment on attachment From mauri...@br.ibm.com 2017-08-16 18:20
EDT---
Hi Joseph,
> Can you post a note when the patch from Paul lands in mainline or
linux-next?
Ingo pulled Paul's patch into tip.git, and it's now in linux-next.git.
rcu: Migrate callbacks earlier in the CPU-offlin
--- Comment From ar...@us.ibm.com 2017-08-16 18:13 EDT---
Much better! Thank you.
$ grep HOTPLUG_DEFAULT config-4.10.0-32-generic
# CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE is not set
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to li
works on
Linux probook 4.10.0-33-generic #37-Ubuntu SMP Fri Aug 11 10:55:28 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
changed tag to verification-done-zesty
** Tags removed: verification-needed-zesty
** Tags added: verification-done-zesty
--
You received this bug notification because you are a
The title of the email might be better to include the directory path to
the file, and a brief description.
Use the body of the email to mention Lenovo.
I assume you already got that feedback...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribe
Please do use my email or name, etc.
B
--
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/1700657
Title:
Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB
Status in Linux:
Unknow
I built a v2 version of the test kernel. The test kernel can be
downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1709171/
Can you test this kernel and see if it resolves this bug?
Thanks in advance!
--
You received this bug notification because you are a member of Kernel
Packages, whic
** Description changed:
---Problem Description---
+
The following patches are missing in the ubuntu 16.04.3 kernel
+
https://lists.ozlabs.org/pipermail/linuxppc-dev/2017-April/156104.html
+
https://lists.ozlabs.org/pipermail/linuxppc-dev/2017-April/156105.html
+
https://lists.ozla
Can't reproduce the crash as described before (consistently failed on a
heavy export job in virtualbox W10 guest).
** Tags removed: verification-needed-zesty
** Tags added: verification-done-zesty
** Description changed:
Upgraded to zesty about a week ago. Ran into this on latest kernel.
(du
** Tags removed: verification-needed-xenial verification-needed-zesty
** Tags added: verification-done-xenial verification-done-zesty
** Changed in: hwe-next
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is su
--- Comment From b...@us.ibm.com 2017-08-16 16:14 EDT---
I added the tag: verification-done-zesty
** Tags removed: verification-needed-zesty
** Tags added: verification-done-zesty
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to li
** Tags removed: verification-needed-zesty
** Tags added: verification-done-zesty
--
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/1689365
Title:
ibmvscsis: Do not send aborted task respon
I've ran the vm-start-stop test on a ThunderX system for an hour on the
proposed kernel w/o any issues.
** Tags removed: patch verification-needed-zesty
** Tags added: verification-done-zesty
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed t
The builtin module in http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.19.8-vivid/linux-
headers-3.19.8-031908-generic_3.19.8-031908.201505110938_amd64.deb is
also broken.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
h
is this the same bug? https://bugs.launchpad.net/dri/+bug/1660485
--
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/1554613
Title:
Screen flickers on XPS 13 9350/9550 (Intel Skylake/Broadwe
** Package changed: linux (Ubuntu) => dri
** Bug watch added: freedesktop.org Bugzilla #101586
https://bugs.freedesktop.org/show_bug.cgi?id=101586
** Changed in: dri
Importance: Medium => Unknown
** Changed in: dri
Status: Confirmed => Unknown
** Changed in: dri
Remote watch: None
** Also affects: bluez
Importance: Undecided
Status: New
** No longer affects: bluez
--
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/1691556
Title:
Can't send audio to Amazon E
@kleber-souza It seems like the issue affects both Zesty and Xenial
(when using the HWE stack). Does that mean that we need an additional
tag "verification-done-xenial" or is it sufficient the way you write it
above? Thanks for clarifying!
--
You received this bug notification because you are a m
** Changed in: kernel-sru-workflow/automated-testing
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1709300
Title:
linux-aws: 4.4.0-1032.41 -pr
** Changed in: linux (Ubuntu)
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/1711182
Title:
ACPI ID for Hip07/08 I2C controller has typo
Stat
Just installed the kernel from proposed, if I don't report back that
means it works fine.
--
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/1680904
Title:
zesty unable to handle kernel NULL
** 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/1709296
Title:
linux: 4.4.0-93.116 -proposed
** Attachment added: "dmesg output of proposed kernel collected via ssh over
hns NIC"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704885/+attachment/4933839/+files/dmesg.out
** Tags removed: verification-needed-zesty
** Tags added: verification-done-zesty
--
You received this bug
** 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/1709303
Title:
linux: 4.10.0-33.37 -proposed
--- Comment From danie...@br.ibm.com 2017-08-16 14:37 EDT---
> Did this issue start happening after an update/upgrade? Was there a prior
> kernel version where you were not having this particular problem?
First time I've noticed this issue was with a 4.11 kernel in Ubuntu
17.10 about a mo
** 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/1709294
Title:
linux: 3.19.0-92.100 -propose
Thanks for the response and sorry for the limited details.
I confirmed bug is present with http://kernel.ubuntu.com/~kernel-
ppa/mainline/v4.13-rc4/linux-
image-4.13.0-041300rc4-generic_4.13.0-041300rc4.201708062231_amd64.deb
I don't know of a previous working version. My colleagues were compilin
** 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 subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1710765
Title:
cp2105 usb s
I've tested this kernel and observed no regressions. Updated firmware
has not been released to expose these IDs, so I can't directly test
this. However, it turns out that there is a typo in the ACPI IDs that
has since been fixed upstream, meaning the proposed patches are
insufficient to solve the i
** 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/1709292
Title:
linux: 3.13.0-129.178 -propos
** 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/1709293
Title:
linux-lts-trusty:
Public bug reported:
[Impact]
Due to a typo in the upstream fix for LP: #1708293, the i2c driver still does
not recognize the ACPI IDs for the i2c devices on the Hip07/08 platforms,
making these devices unusable.
[Test Case]
ls -l /sys/class/i2c-dev/*/device/firmware_node | grep HISI
[Regres
adt tests appear to pass quickly enough. A new bug will be opened if and
when any new adt issues arise.
** Tags removed: verification-needed-trusty verification-needed-xenial
verification-needed-zesty
** Tags added: verification-done-trusty verification-done-xenial
verification-done-zesty
--
Y
Hello,
http://marc.info/?l=linux-usb&m=150290165217984&w=2
Regards,
--
Cristian
** Also affects: linux
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
Verification done!
** Tags removed: verification-needed-zesty
** Tags added: verification-done-zesty
--
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/1704479
Title:
Change CONFIG_IBMVETH
This is a fresh install. I just got a new Laptop and installed Ubuntu.
I installed the latest upstream kernel.
uname -a
Linux mlp-GL553VD 4.13.0-041300rc4-generic #201708062231 SMP Mon Aug 7 02:32:51
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
It does fix the issue but not in it's entirety. Fn+F5/F6
Still not working after those edits. Did I do something wrong?
Here is my entire file after the edits:
# /lib/udev/hwdb.d/60-keyboard.hwdb
# This file is part of systemd.
#
# This file contains 3 types of metadata to apply to keyboards and
# keyboard-like input devices:
# - Key mapping
# - Hard-
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 'verificati
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 'verificati
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 'verificati
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 'verifica
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 'verificati
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 'verificati
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 'verificati
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 'verificati
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 'verificati
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 'verificati
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 'verifica
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 'verifica
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 'verificati
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 'verificati
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 'verificati
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 'verifica
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 'verificati
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 'verificati
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 'verificati
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 'verificati
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 'verifica
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 'verificati
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 'verificati
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 'verificati
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 'verifica
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 'verifica
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 'verifica
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 'verificati
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 'verificati
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 'verifica
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 the problem still exists,
change the tag 'verifica
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 'verifica
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 'verificati
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 'verifica
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 'verificati
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 'verifica
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 'verifica
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 'verifica
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 'verificati
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 'verificati
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 'verificati
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 'verifica
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 'verificati
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 'verifica
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 'verifica
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 'verificati
1 - 100 of 260 matches
Mail list logo
