[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-firmware in Ubuntu.
[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.
** Changed in: libinput (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/1746740
Title:
XPS13 L322X Bionic (daily dev) touchpad laggy
@Kai-Heng Feng - I have no idea about kernel bisectionBut yes there
is a good news..this bug is finally fixed(don't know if further updates
will cause WIFI issue again) in 18.04 release :) WIFI worked without any
configuration. Please check with latest Ubuntu 18.04 Release in live
mode if it
Opened a bug here:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1767559
Haven't done an SRU request before, so we'll see how it goes.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I reinstalled 16.04 and reinstalled nvidia drivers, and I was able to
properly disengage the discrete gpu under prime profiles.
This issue seems to only affect 18.04.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in
Public bug reported:
After system update (sudo apt upgrade), the bluetooth built-in adapter
is not found anymore!
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-122-generic 4.4.0-122.146
ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117
Uname: Linux
I seem to be having an issue like this as well. I did a fresh install of
18.04 yesterday, and while the nvidia x server application states that
the discrete gpu is turned off, i have a hardware light on my laptop
that shows it to still be active, even though the nvidia x server
settings show the
This regression does not affect Xenial, so the fix is redundant.
--
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/1749420
Title:
[regression] Colour banding and artefacts appear
With a different install of Bionic in my notebook, the problem is
happening too. This appears on dmesg:
[ 95.285073] [ cut here ]
[ 95.285109] NETDEV WATCHDOG: enp1s0 (r8169): transmit queue 0 timed out
[ 95.285165] WARNING: CPU: 3 PID: 0 at
Hello dino99!
My system worked fine until only a few days ago whilst I was still using
17.10...
My system then started to fail to boot (blank screen) after a recent
update/upgrade command:
sudo apt update
sudo apt upgrade
The following kernels starting causing a problem:
4.13.0-38
4.13.0-39
I
--- Comment From jos...@br.ibm.com 2018-04-27 16:54 EDT---
I was told to write a small documentation describing what happens without the
two patches mentioned in my comment #20.
We basically lose the ability to hotplug/unplug CPUs into virtual
machines. Considering that blk-mq enqueue
Hi Po-Hsu,
The apparmor mount test is failing because while testing mounting, it is
attempting to mount with the option MS_MANDLOCK and bionic's linux-kvm
kernel has CONFIG_MANDATORY_FILE_LOCKING disabled, causing the operation
to fail even when apparmor is not involved. Given that upstream seems
Also maybe related as I am running TLP: https://www.spinics.net/lists
/linux-usb/msg167941.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/1763594
Title:
xhci hangs; reset results
ubuntu@d05-1:~$ cat /proc/version
Linux version 4.13.0-40-generic (buildd@bos02-arm64-005) (gcc version 7.2.0
(Ubuntu/Linaro 7.2.0-8ubuntu3.2)) #45-Ubuntu SMP Wed Apr 25 08:03:23 UTC 2018
ubuntu@d05-1:~$ grep enahisic2i0-tx /proc/interrupts | sed 's/.* //'
enahisic2i0-tx0
enahisic2i0-tx1
Tried it on my machine, it does not solve the touchpad problems on Chuwi
Lapbook air, i think it has a different touchpad than what that fix
solves.
lavjamanxd@sargeras:~/Downloads$ uname --all
Linux sargeras 4.15.0-20-generic #21~lp1728244 SMP Fri Apr 27 13:19:49 CST 2018
x86_64 x86_64 x86_64
** Changed in: kernel-sru-workflow/automated-testing
Status: Confirmed => Fix Released
--
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/1766614
Title:
linux-aws: 4.4.0-1056.65
ubuntu@hotdog:~$ cat /proc/version
Linux version 4.13.0-40-generic (buildd@bos02-arm64-005) (gcc version 7.2.0
(Ubuntu/Linaro 7.2.0-8ubuntu3.2)) #45-Ubuntu SMP Wed Apr 25 08:03:23 UTC 2018
ubuntu@hotdog:~$ sudo ipmitool lan print
Set in Progress : Set Complete
Auth Type Support :
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Tags added: chaotic
--
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/1767504
Title:
Dell
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
--
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/1767490
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767504/+attachment/5128913/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
ubuntu@hotdog:~$ sudo perf list | grep thunderx2
thunderx2 imp def:
ubuntu@hotdog:~$ cat /proc/version
Linux version 4.13.0-40-generic (buildd@bos02-arm64-005) (gcc version 7.2.0
(Ubuntu/Linaro 7.2.0-8ubuntu3.2)) #45-Ubuntu SMP Wed Apr 25 08:03:23 UTC 2018
** Tags removed:
Public bug reported:
Hello,
I have the problem that I cannot control the screen brightness on my XPS
15 9560 notebook.
/sys/class/backlight is empty. I'm running latest Dell BIOS firmware
1.9.4. I tried all kinds of kernel parameters, such as acpi_osi and
acpi_backlight, but without any effect.
ubuntu@hotdog:~$ dmesg | grep W+X
[ 35.653992] arm64/mm: Found insecure W+X mapping at address
00ac9000/0x00ac9000
[ 36.046414] Checked W+X mappings: FAILED, 12 W+X pages found, 0 non-UXN
pages found
Yep, that's in the userspace mapping.
** Tags removed:
** 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-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1766599
Title:
linux-oem: 4.13.0-1025.28
** Changed in: kernel-sru-workflow/automated-testing
Status: Confirmed => Fix Released
--
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/1766605
Title:
linux-aws: 4.4.0-1018.18
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 1767443
and then change the status of the bug to 'Confirmed'.
If, due to the
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
Public bug reported:
[Impact]
The hinic driver isn't included in the installer, so it isn't possible to use
Huawei NICs for network installs.
[Test Case]
Boot d-i on a system with a Huawei PCIe card. Proceed to the network
configuration screen, and see if that NIC is displayed.
[Regression
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a member
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a member
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a member
Verified fixed in all affected -proposed kernels:
trusty 3.13.0-146.195
xenial 4.4.0-123.147
artful 4.13.0-40.45
** Tags removed: verification-needed-artful verification-needed-trusty
verification-needed-xenial
** Tags added: verification-done-artful verification-done-trusty
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a member
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a member
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/certification-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in:
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a member
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a member
** Package changed: linux-signed (Ubuntu) => linux (Ubuntu)
--
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/1767443
Title:
regular hard lockup on bionic kernel
Status in linux package
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/certification-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in:
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/certification-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in:
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag
SRU Request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-April/092032.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/1766573
Title:
linux < 4.11: unable to use
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
** Changed in: kernel-sru-workflow/security-signoff
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/1766596
Title:
linux-gcp: 4.13.0-1014.18 -proposed
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
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/certification-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in:
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/certification-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in:
v2 SRU request for Artful:
https://lists.ubuntu.com/archives/kernel-team/2018-April/092024.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/1746474
Title:
unregister_netdevice:
add kernel parameter "blacklist=nouveau modprobe.blacklist=nouveau" will
help to boot up for kernel 4.13 and 4.16, but does not solve nvidia
problem
--
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-
artful' to 'verification-done-artful'. 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-
artful' to 'verification-done-artful'. 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-
artful' to 'verification-done-artful'. 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-
artful' to 'verification-done-artful'. 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-
artful' to 'verification-done-artful'. 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-
artful' to 'verification-done-artful'. 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-
artful' to 'verification-done-artful'. 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-
artful' to 'verification-done-artful'. 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-
artful' to 'verification-done-artful'. If the problem still exists,
change the tag
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/certification-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in:
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
artful' to 'verification-done-artful'. If the problem still exists,
change the tag
SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-April/092020.html
** Description changed:
+ == SRU Justification ==
+ Linux kernel 4.15 has introduced a bug in e1000e msix interrupt drivers,
+ which violates the e1000e specification. Specifically, the driver
+
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/certification-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in:
Hi Po-Hsu,
Thanks for double-checking, that's appreciated! The security team does
not have an opinion on whether CONFIG_KALLSYMS and CONFIG_KALLSYMS_ALL
should be enabled, from a security/hardening standpoint. It may be
useful from the kernel team's perspective, to make debugging kernel oops
bug
SRU Requests:
https://lists.ubuntu.com/archives/kernel-team/2018-April/092013.html
https://lists.ubuntu.com/archives/kernel-team/2018-April/092016.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
ppc64el versions of the Xenial test kernel are now available here:
http://kernel.ubuntu.com/~jsalisbury/lp1762928/xenial
Xenial required the following two prereq commits:
d96f234f47af ("powerpc: Avoid load hit store in setup_sigcontext()")
d11994314b2b ("powerpc: signals: Stop using current in
I built a test kernel with the two commits pointed out by Jay. The test
kernel also required commit f307668bfc as a prereq.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1753662
--
You received this bug notification because you are a member of Kernel
Packages,
Public bug reported:
Here's a snippet from the kernel log which I think will make the actual
issue clear:
Apr 27 09:49:20 caliburn kernel: [ 4558.910412] pcieport :0a:03.0: Refused
to change power state, currently in D3
Apr 27 09:49:20 caliburn kernel: [ 4558.917717] xhci_hcd :0d:00.0:
Here's the above in an (unmunged) attachment
** Attachment added: "kern.log"
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1767452/+attachment/5128741/+files/kern.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Description changed:
- It's impossible to use power button functionalities in Acer Swift Notebook
Series (tested on Acer Swift 3 sf314-52).
+ == SRU Justification ==
+ It's impossible to use power button functionalities in Acer Swift Notebook
+ Series (tested on Acer Swift 3 sf314-52). The
FWIW, I verified that Tycho's microcode revision is what's expected for
his CPU:
142: sig 0x000306d4, pf mask 0xc0, 2018-01-18, rev 0x002a, size 18432
I don't think his lockups are due to running a previously published
microcode revision that Intel pulled or any bad interactions with the
4.15
** 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) => Łukasz
Zemczak (sil2100)
** Changed in: kernel-sru-workflow/promote-to-proposed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
--
You received this bug notification because you
OK, i'm now running the V4.16.0 kernel:
> craigster0@p51:/local/home/craigster0/Downloads/linux-kernel-4.16$ uname -r
> 4.16.0-041600-generic
and clicking on the "speaker icon" on the menu bar at the bottom of the
screen still shows "No output or input devices found". more
importantly, trying
Here's /var/log/kern.log, just for grins.
** Attachment added: "kern.log"
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1767443/+attachment/5128706/+files/kern.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** 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) => Łukasz
Zemczak (sil2100)
** Changed in: kernel-sru-workflow/promote-to-proposed
Public bug reported:
Hi guys,
I'm sorry I have no real information to add to this, but Serge
encouraged me to file a bug to get you guys to help me to debug this, so
blame him.
I've been running the bionic kernels on a thinkpad X1 carbon 3rd
generation for several months, and experiencing 2x
One comment for future releases: would be nice if config changes could
be better documented in the changelog and/or attached bugs - listing
which exact flags have been changed to resolve the respective bug. But
that's just a thing from my wishlist.
** Changed in:
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
--
You received this bug notification because you
** 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/1766006
Title:
kworker taking 100% cpu one one single core
Status in
Thanks for the pointer, Jay! I'll build a Xenial test kernel with these
two commits and post a link to it.
--
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/1753662
Title:
[i40e] LACP
** 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) => Łukasz
Zemczak (sil2100)
--
You received this bug notification because you are
Wow, I just upgraded to 18.04 and after the restart bluetooth was gone.
I tried to restart a couple of times, no deal, then I turned off and on
again, and it worked!
My device is this one:
Bus 001 Device 005: ID 0cf3:e007 Atheros Communications, Inc.
--
You received this bug notification
Private bug reported:
Quickbooks Destop toll free number + 1-844-366-8247 .Quickbooks Errors Support
Quickbooks toll free number + 1-844-366-8247 .Quickbooks Errors Support At the
time of upgrading QuickBooks to the next version or updating files with
information you might encounter messages
** Package changed: linux (Ubuntu) => null-and-void
** Information type changed from Public to Private
** Changed in: null-and-void
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Tags removed: kernel-release-tracking-bug-live
--
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/1766445
Title:
linux-azure: -proposed tracker
Status in Kernel SRU Workflow:
Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
** Tags removed: kernel-release-tracking-bug-live
--
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/1766842
Title:
linux: -proposed tracker
Status in Kernel SRU Workflow:
Invalid
** Tags removed: kernel-release-tracking-bug-live
--
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/1767083
Title:
linux: -proposed tracker
Status in Kernel SRU Workflow:
Invalid
** 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/1766592
Title:
linux: 4.13.0-40.45
Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
** Tags removed: kernel-release-tracking-bug-live
--
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/1765101
Title:
linux: -proposed tracker
Status in Kernel SRU Workflow:
Invalid
** Tags removed: kernel-release-tracking-bug-live
--
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/1765018
Title:
linux-lts-trusty: -proposed tracker
Status in Kernel SRU
1 - 100 of 185 matches
Mail list logo
