Also please attach `journalctl -b -1 -k`.
--
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/1813820
Title:
Waking from Suspend causes screen to appear with grey static (like a
TV with no
Please file an upstream bug at https://bugs.freedesktop.org/
Product: DRI
Component: DRM/amdgpu
--
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/1813820
Title:
Waking from Suspend causes
Christoper, thanks for your help. But I think this should be mailed to
the following recipients instead:
To: Bjørn Mork
Cc: linux-...@vger.kernel.org
Cc: net...@vger.kernel.org
Cc: linux-ker...@vger.kernel.org
And please also Cc me.
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 1783651 ***
https://bugs.launchpad.net/bugs/1783651
Enabled in 4.18 and newer.
** This bug has been marked a duplicate of bug 1783651
Please enable CONFIG_PAGE_POISONING
--
You received this bug notification because you are a member of Kernel
Packages,
ok, so can someone who's experiencing this bug run the requested command
so we can collect more information?
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
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 1818134
and then change the status of the bug to 'Confirmed'.
If, due to the
There's a reasonable chance this is an issue with the lockdown kernel
patches in Ubuntu 14.04, so opening a task on linux also.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1818134
Patch available in Disco.
Porting to T/X/B/C
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
Please send a patch to upstream.
Also, 18514 should change to a hex value.
--
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/1819968
Title:
Colour banding in Lenovo G50-80 laptop display
Please test this kernel:
https://people.canonical.com/~khfeng/lp1814069-2/
Cherry-picked additional two commits:
916c5e1413be058d1c1f6e502db350df890730ce
b19b46346f483ae055fa027cb2d5c2ca91484b91
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Changed in: ubuntu-kernel-tests
Status: New => 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/1812845
Title:
3b080b2564287be91605bfd1d5ee985696e61d3c in
today tried another new kernel with the same result, still the screen
produces garbage after resuming from suspend. This was the kernel used:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.0.2/
should i report this upstream to bugzilla? should mention i also
switched from Kubuntu 18.10 to
I get this bug on Ubuntu 18.10 with the kernel upgraded to 5.0.2 from the
ubuntu repository. My machine is an Acer Predator Helios 500 Ryzen.
acpi PNP0C14:01: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first
instance was on PNP0C14:00)
--
You received this bug notification
** Changed in: apt (Ubuntu Cosmic)
Importance: Undecided => Critical
** Changed in: apt (Ubuntu Bionic)
Importance: Undecided => Critical
** Changed in: apt (Ubuntu Xenial)
Importance: Undecided => High
** Changed in: apt (Ubuntu Trusty)
Importance: Undecided => High
--
You
** No longer affects: linux (Ubuntu)
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Triaged
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a
** Also affects: dkms
Importance: Undecided
Status: New
** Changed in: dkms
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1515513
Title:
** Tags removed: verification-needed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1515513
Title:
/boot/initrd.img-*.old-dkms files left behind
Status in DKMS:
New
Status in dkms
I'm not sure how the Nvidia driver could be related.
Although this looks relevant to keyboard problems. This appears a few
times in your log (comment #22):
sty 27 21:03:24 br00net gnome-shell[2527]: JS ERROR: Exception in callback for
signal: activate: Error: Error invoking
Although ^^^ the above error ^^^ is already covered by bug 1812593.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1812014
Title:
keyboard not responding after
$ xrandr --props
Screen 0: minimum 320 x 200, current 1366 x 768, maximum 32767 x 32767
VGA1 connected primary 1366x768+0+0 (normal left inverted right x axis y axis)
410mm x 230mm
EDID:
00001e6d094c07230800
071601036c291778ead025a258559c28
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 1819989
and then change the status of the bug to 'Confirmed'.
If, due to the
elhoir:
>"i contacted with a guy with an AMD RX 470 GPU and he says irs working
fine on his system"
Besides mundane root causes (card hardware jacked and needs RMA), there
are other reason why your results differ from others (not all RX 470
cards are equivalent in every way due to OEM
Peter Schüller, if this is confirmed with the latest mainline kernel
(now 5.0.2), then the issue you are reporting is an upstream one. Could
you please report this problem following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate mailing
list (TO linux-usb CC
Public bug reported:
This bug exists to track the basic support to NVLink2 passthrough on
Ubuntu 18.04 - for the guest side only. There's a relative small
patchset that I'm going to send to Canonical Kernel Team using this
buglink.
On the host side we'll be running a custom version of Ubuntu
I have the same problem with the nvidia driver. Updated shim-signed +
dkms installed a while ago, worked fine until kernel upgrade triggered
dkms rebuild, then the nvidia driver failed to load, "modprobe: ERROR:
could not insert 'nvidia': Package not installed". Uninstalling shim-
signed,
*** This bug is a duplicate of bug 1819881 ***
https://bugs.launchpad.net/bugs/1819881
** This bug has been marked a duplicate of bug 1819881
[CONFIG] please enable highdpi font FONT_TER16x32
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-trusty
** Tags added: block-proposed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
** Tags removed: lenovo-g50
** Tags added: g50-80 lenovo
--
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/1819968
Title:
Colour banding in Lenovo G50-80 laptop display (i915)
Status in
Probably related:
https://patchwork.kernel.org/patch/9716467/
Since the introduction of kernel 4.8 I've been experiencing color
banding on my Lenovo G50-80 notebook. I also had reports of the same
symptoms on the G50-70 model.
I figured out that the problem had been introduced by commit
*** This bug is a duplicate of bug 1792957 ***
https://bugs.launchpad.net/bugs/1792957
--- Comment From lagar...@br.ibm.com 2019-03-13 16:55 EDT---
Hello Canonical,
This has been included in Ubuntu 18.04 and Ubuntu 18.10 on Launchpad
1792957. Is there anything blocking its inclusion
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 1819968
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
Colour bandind is visible everywhere in the system. I believe it's not a
hardware problem, since booting with 'nomodeset' works as expected and
the previously installed Ubuntu 14.04 also worked.
I tried installing kernel 4.18.0-16.17 from ppa:canonical-kernel-
team/ppa but
Hi,
I have no unusual extensions installed and even though I disabled all gnom
extensions the problem remained.
After checking that, I did what I should have done at the beginning - I changed
display driver to X.Org X Server nouveau and since then I have got no problems
with the keyboard at
** 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 --
+
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
I recently installed a fresh system with 18.04 as well and have
experienced this exact issue when attempting to "apt dist-upgrade" from
ssh. In the two instances where systemd was being updated (a few weeks
ago and today), my ssh connection was dropped and I'm unable to re-
connect to the server.
As I have said previously, I'm not sure that my problem was the same
that others have (I didn't have freezes on idle, but rather freezes when
compiling), but what helped me is updating BIOS to latest version. ASUS
has released a new BIOS with AGESA 0070 for X470 Pro, and I can't
trigger the bug
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Incomplete
** Description changed:
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
** 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:
- linux-kvm: -proposed tracker
+ linux-kvm: 4.18.0-1009.9 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team
Would it be possible to try kernel < 4.18.0-16?
--
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/1819924
Title:
System hangs when hot-plugging dual monitor dock
Status in linux package
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
Seems like we enabled this platform before. Let me see if I can find the
same system in our lab.
--
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/1818140
Title:
[Dell DW1560 / BCM20702A1]
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel
** Changed in: linux (Ubuntu Trusty)
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/1819869
Title:
linux-cloud-tools-common 3.13.0-166.216 in
It was unstable from the begining, I can test some bisect kernels if you
can provide me with
wt., 12 mar 2019, 18:50 użytkownik Kai-Heng Feng <
kai.heng.f...@canonical.com> napisał:
> So the bluetooth part is not proprietary. Does this issue happen to
> previous kernels?
>
> --
> You received
@ALinuxUser: the patches are not yet upstream and thus one has to build
a patched kernel yourself. You can follow the upstream process in the
links posted from aaronma.
For some people it is working because they have a different touchpad.
But according to the above discussion even the patches
** 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:
** 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:
** 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:
** 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:
Still did not get further update from our customer. Please feel free to
invalid certification-testing to move forward by following the original
release schedule. Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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/1819924
Title:
System hangs when
** Changed in: kernel-sru-workflow/prepare-package
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
** 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 --
- phase:
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 1819921
and then change the status of the bug to 'Confirmed'.
If, due to the
** Description changed:
[Impact]
Some systems boot failed at a very early stage, only blackscreen shown.
[Fix]
Some system BIOS set definition in if statement, it would be deferred to be
loaded.
Some devices would not work properly and cause a system lockup.
execute all acpi
Ubuntu 18.10
Bluez Version: 5.50-0ubuntu1
After changing batteries in my bluetooth mouse, it is connected but
doesn't work (no movement or clicking). Fix is to re-pair it.
~$ dmesg | tail -40
[12650.520061] sysfs_warn_dup.cold.4+0x17/0x32
[12650.520064] sysfs_create_dir_ns+0xa9/0xd0
** Summary changed:
- linux: -proposed tracker
+ linux: 3.13.0-167.217 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team (canonical-kernel-team) =>
Public bug reported:
When plugging in my Cable Matters USB-C Dual 4K DisplayPort Docking
Station into my system, after it has already booted, the system hangs
with a kernel OOPS. This is always repeatable.
Steps to reproduce:
1. Ensure docking station is unplugged or shut-off.
2. Boot up
Exactly. I did the "verification-done-bionic" step for 18.2.2 in comment
#12 above; and unfortunately I don't have an affected school nearby,
where I could test 18.2.8 in cosmic, and installing cosmic in a remote
school would be hard.
Thanks a lot Timo!
--
You received this bug notification
** 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:
Hi, do you install vanilla/stock Ubuntu Xenial, or the preloaded OEM
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/1818816
Title:
Ubuntu 16.04 LTS + "lspci: Cannot open
Public bug reported:
[Impact]
Some systems boot failed at a very early stage, only blackscreen shown.
[Fix]
Some system BIOS set definition in if statement, it would be deferred to be
loaded.
Some devices would not work properly and cause a system lockup.
execute all acpi tables to make system
I am sorry, but what is going on?
The authors of some posts in this thread say that they are using a
patched kernel. Yet, the developer, Aaron, seems to say one does not
need patches . However, that same developer seems to say that his work
has *not yet* become incorporated into the kernel.
Public bug reported:
Ubuntu 18.04 w/ kernel 4.18.0-15 or 4.19.28 w/ nouveau driver on top of
Xen 4.11.1 regularly deadlocks system. It's reachable via network for a
bit, then becomes completely unresponsive.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: kerneloops
I reported this incorrectly, since the actual traces aren't included.
Here's the kernel log.
** Attachment added: "kern.log-20190313"
https://bugs.launchpad.net/ubuntu/+source/kerneloops/+bug/1819918/+attachment/5245858/+files/kern.log-20190313
--
You received this bug notificati
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
** Affects: kernel-sru-workflow
Importance:
** 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 --
** Changed in: oem-priority
Status: Triaged => Fix Released
--
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/1781533
Title:
SATA device is not going to DEVSLP
Status in HWE
** Summary changed:
- linux-kvm: -proposed tracker
+ linux-kvm: 4.15.0-1031.31 -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: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de
Souza Cascardo (cascardo)
** Changed in:
bionic was already fixed earlier by 18.2.2-0ubuntu1~18.04.2 in time for
18.04.2 release
cosmic got the exact same oneliner in 18.2.8-0ubuntu0~blah, and then
that was backported to bionic which reopened this bug. Requiring Alkis
to test this on cosmic is too much IMO, as it would involve first to
** Description changed:
[Impact]
There are some new Intel GPU pci-id's that need to be added to several places:
0x3E98
0x87C0
and to make future additions easier, add platform definitions for
Whiskey Lake and Amber Lake too.
[Test case]
- Check that the user session uses
All tasks have been completed and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Changed in:
This was already fixed in bionic by 18.2.2-0ubuntu1~18.04.1, now the
same is included upstream in 18.2.8 which was upload to cosmic too as
well as to bionic via a new backport.
Again, I don't have the hardware (AML, WHL is broken atm), adding pci-
id's just allow the X driver to load the DRI
Hello there
I'm seeing this issue too on Ubuntu 16.04.6 with kernel 4.4.0-142.
We had to revert back to kernel 4.4.0-141 for java to work again.
I think, I have identified this commit
https://kernel.ubuntu.com/git/ubuntu/ubuntu-
xenial.git/commit/?id=1096e1455d67b0c804c8936947a82971ebab0644 as
This bug was fixed in the package linux-raspi2 - 4.18.0-1010.12
---
linux-raspi2 (4.18.0-1010.12) cosmic; urgency=medium
* linux-raspi2: 4.18.0-1010.12 -proposed tracker (LP: #1814755)
* bluetooth controller not detected with 4.15 kernel (LP: #1810797)
- [Config] Disable
This bug was fixed in the package linux-gcp - 4.18.0-1007.8
---
linux-gcp (4.18.0-1007.8) cosmic; urgency=medium
* linux-gcp: 4.18.0-1007.8 -proposed tracker (LP: #1814759)
* bluetooth controller not detected with 4.15 kernel (LP: #1810797)
- [Config] Disable BT_QCOMSMD_HACK
This bug was fixed in the package linux-raspi2 - 4.18.0-1010.12
---
linux-raspi2 (4.18.0-1010.12) cosmic; urgency=medium
* linux-raspi2: 4.18.0-1010.12 -proposed tracker (LP: #1814755)
* bluetooth controller not detected with 4.15 kernel (LP: #1810797)
- [Config] Disable
This bug was fixed in the package linux-kvm - 4.18.0-1008.8
---
linux-kvm (4.18.0-1008.8) cosmic; urgency=medium
* linux-kvm: 4.18.0-1008.8 -proposed tracker (LP: #1814760)
[ Ubuntu: 4.18.0-16.17 ]
* linux: 4.18.0-16.17 -proposed tracker (LP: #1814749)
* Packaging resync
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu Cosmic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Description changed:
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 --
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
** Changed in: kernel-sru-workflow/promote-to-security
** 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 --
** Tags added: patch
--
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/1812845
Title:
3b080b2564287be91605bfd1d5ee985696e61d3c in ubuntu_btrfs_kernel_fixes
triggers system hang on i386
** Tags added: id-5c88b2cecc73e1431fae0041
--
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/1819869
Title:
linux-cloud-tools-common 3.13.0-166.216 in Trusty is missing contents
of
** Summary changed:
- linux-raspi2: -proposed tracker
+ linux-raspi2: 4.18.0-1011.13 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team
** Changed in: linux (Ubuntu)
Status: Invalid => In Progress
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Andy Whitcroft (apw)
--
You received this bug notification because you are a member of Kernel
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic.
--
You received this bug notification because you are a member of Kernel
Packages, which is
What testing did you perform?
** Tags removed: verification-done verification-done-cosmic
** Tags added: verification-needed verification-needed-cosmic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
As of right now there is no non-rc version of aufs with support for
Linux 5.0. We will update it as soon as one is available. However, the
regex isn't going to work even when we have a non-rc version since it is
looking for a 4.x version, and the version will undoubtedly be 5.0
(looks like it
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Trusty)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
** 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 1819623
** Summary changed:
- linux: -proposed tracker
+ linux: 4.18.0-17.18 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team (canonical-kernel-team) =>
** 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:
** 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:
1 - 100 of 134 matches
Mail list logo
