** 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
** 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 --
+
Hello bugproxy, or anyone else affected,
Accepted makedumpfile into xenial-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/makedumpfile/1:1.5.9-5ubuntu0.6 in
a few hours, and then in the -proposed repository.
Please help us by testing this new
Dear Colleagues.
TL;DR - there is hope!
I've been approached by Anthony from Canonical and later Brian from
Lenovo. We have agreed I will send my Laptop to Lenovo for
investigations. So I wanted to prepare fresh system (clean my personal
data, naturally). After making the hacks and changes I did
** 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
Status: New => Confirmed
** 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
And just to illustrate my point, on 4.14.0 vanilla:
while true; do
dd if=/nfsmount/debian-live-9.1.0-amd64-xfce+nonfree.iso bs=16M iflag=direct
2>/dev/null | sha1sum; done
With rx offload on (default):
489ed92b17aa9a4582899356d3123621b5d92189 -
742462292c76189f63fc3e7af1acc9dec56c0a8d -
This is happening even on my 9560 with 4.13.9 vanilla; when running a
background rsync backup job, packages downloaded in a Debian docker
build frequently do not match their checksum and need multiple runs to
succeed.
--
You received this bug notification because you are a member of Kernel
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
--
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/1738178
** 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/1738073
Title:
thunderx2: i2c driver PEC and ACPI clock fixes
** Changed in: kernel-sru-workflow/automated-testing
Status: Incomplete => Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
** Tags removed:
** Changed in: systemd (Ubuntu Artful)
Status: Confirmed => Fix Committed
** Changed in: systemd (Ubuntu Artful)
Status: Fix Committed => In Progress
** Changed in: systemd (Ubuntu Artful)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
You received this bug
** Description changed:
Hi all,
Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
reported a corrupted BIOS.
It's not possible to save new settings in BIOS anymore and after
rebooting, the system starts with the old settings.
Moreover (and most important)
I wonder what ist done to prevent any other Lenovo über to run into that
issue. As it is not yet sure if this issue can be solved, Canonical
should do something to make sure that no other Lenovo owner installs or
updates to 17.10, no matter if it's their fault at all.
--
You received this bug
Can you give the latest 4.13 upstream stable kernel a try:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13.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/1737316
Title:
Having
This is a brand new laptop that shipped with windows 10. This is the
first time trying to install. I will proceed with newest kernel.
existing is 4.13.0-19-generic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
SRU Request submitted:
https://lists.ubuntu.com/archives/kernel-team/2017-December/088912.html
** Also affects: linux (Ubuntu Bionic)
Importance: Medium
Assignee: Joseph Salisbury (jsalisbury)
Status: In Progress
** Description changed:
+ == SRU Justification ==
+ Artful uses
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** 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
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Invalid
--
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/1737511
Title:
linux: 4.4.0-104.127 -proposed
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Invalid
--
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/1737515
Title:
linux-aws: 4.4.0-1044.53
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 1738224
and then change the status of the bug to 'Confirmed'.
If, due to the
Attempted with mainline generic kernel at http://kernel.ubuntu.com
/~kernel-ppa/mainline/v4.15-rc3
The issue persists. I can boot into the 4.15-rc3 kernel in recovery
mode fine. In that case it comes up with the built in intel 800x640
resolution, not the nvidia graphics.
I've attached a zip
The original bug title was '15:10: bluetoothd reports "Not enough
handles to register service" at start', and the original bug description
described both the "Not enough free handles to register service" problem
and the "Failed to start discovery" problem[1]. Between #47 and #48, the
title and
** 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/1738219
Title:
the kernel is blackholing IPv6 packets to linkdown
** Changed in: ubuntu-z-systems
Importance: Undecided => Medium
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1734130
Title:
[18.04 FEAT] Add kvm_stat
** Changed in: kernel-sru-workflow/automated-testing
Status: Incomplete => Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
** Tags removed:
Hello, I have seen the exactly same issue, with the exactly same
hardware you have: it's the HP EliteDesk 705 G3 Desktop Mini.
I've tested already a ton of options, including recompiling the latest
kernel, booting with several parameters, and so on and so forth. Got
nothing more than a big
** Changed in: linux (Ubuntu)
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/1716491
Title:
New PMU fixes for marked events.
Status in The
This bug was fixed in the package dkms - 2.3-3ubuntu4
---
dkms (2.3-3ubuntu4) bionic; urgency=medium
* 0015-change-arch-in-mkdeb-template.patch: Utilize DEBIAN_BUILD_ARCH in the
control file for mkdeb. Thanks to Launchpad user martin for the patch.
(LP: #1729051)
-- Brian
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux-lts-xenial (Ubuntu Xenial)
Importance: Undecided
** Changed in: debconf (Ubuntu)
Status: Incomplete => New
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
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/1736770
Public bug reported:
When the 'ignore_routes_with_linkdown' sysctl is set, we should not
consider linkdown nexthops during route lookup.
While the code correctly verifies that the initially selected route
('match') has a carrier, it does not perform the same check in the
subsequent multipath
You have been subscribed to a public bug:
My machine (XPS 13 9360) won't go into suspend properly after upgrading
from linux-image-4.13.0-17-generic to linux-image-4.13.0-19-generic.
This affects both suspend through lid close and "systemctl suspend".
Screen goes off, power led remains lit. Then
Public bug reported:
My machine (XPS 13 9360) won't go into suspend properly after upgrading
from linux-image-4.13.0-17-generic to linux-image-4.13.0-19-generic.
This affects both suspend through lid close and "systemctl suspend".
Screen goes off, power led remains lit. Then after some time 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.15 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
SRU Request submitted:
https://lists.ubuntu.com/archives/kernel-team/2017-December/088920.html
** Description changed:
+
+ == SRU Justification ==
+ This issue was first reported on the netdev email list by Lennart Sorensen:
+ https://www.mail-archive.com/netdev@vger.kernel.org/msg178170.html
+
Yes, these commits will also land in the HWE kernels.
** Also affects: linux (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Artful)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Zesty)
Status: New => In Progress
**
Can you confirm that Zesty with the latest updates and at least the
Ubuntu-4.10.0-38 resolves this bug?
** No longer affects: perforate (Ubuntu Zesty)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Information type changed from Private to Public
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
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/1734130
Title:
[18.04
The fix for this bug made it into Zesty via bug 1716491.
--
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/1711104
Title:
[P9][Ubuntu 16.04.03] Additional PMU fixes for P9
Status in The
** 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 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 1738219
and then change the status of the bug to 'Confirmed'.
If, due to the
Is this fix released in artful & bionic too?
--
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/1730596
Title:
s390/mm: fix write access check in gup_huge_pmd()
Status in Ubuntu on IBM z
I tested now with Kernel 4.4.0-103-generic + the patch from commit
bbfcd7 and it works for me
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bbfcd77631573ac4a9f57eb6169e04256a111bc1
--
You received this bug notification because you are a member of Kernel
Packages,
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => Invalid
--
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/1737512
Title:
linux-aws: 4.4.0-1006.6
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => Invalid
--
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/1737511
Title:
linux: 4.4.0-104.127 -proposed
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => Invalid
--
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/1737515
Title:
linux-aws: 4.4.0-1044.53
** Changed in: linux (Ubuntu)
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/1706033
Title:
[P9, Power NV][ WSP][Ubuntu 16.04.03] : perf hw
** Changed in: linux (Ubuntu Artful)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Zesty)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Xenial)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu)
Status: Incomplete => In
*** This bug is a duplicate of bug 1738147 ***
https://bugs.launchpad.net/bugs/1738147
** This bug has been marked a duplicate of bug 1738147
Cherry Trail & USB 3.0
--
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/regression-testing
Status: Confirmed => Invalid
--
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/1737512
Title:
linux-aws: 4.4.0-1006.6
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
** Tags removed: block-proposed-xenial
** Tags removed: block-proposed
--
You received this bug notification because you
** 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 is for tracking the upload package. This
bug will contain status
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 1738067
and then change the status of the bug to 'Confirmed'.
If, due to the
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 1738263
and then change the status of the bug to 'Confirmed'.
If, due to the
That file is not shipped with standard Ubuntu. Was this an OEM shipped
machine and it came in an oem package? Or was that something you added
yourself?
You can check:
dpkg -S /etc/modprobe.d/blacklist_i2c_hid.conf
On Thu, Dec 14, 2017, 12:55 Kevin Dalley <1737...@bugs.launchpad.net>
wrote:
>
Among other issues this is also failing to link because some of the dma-
mapping api has now caused an indirect dependency on a GPL-only export.
Adding a linux task for this issue.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
This file was a workaround, done outside of packaging. The touchpad has
frequently been a problem over the lifetime of the laptop, through
multiple Ubuntu releases.
The problem historically was that the touchpad was flakey, and would
often freeze, jitter, move all over the place. Many users of
You have been subscribed to a public bug:
I am using Xubuntu 16.04 with the latest software.
# Steps to reproduce
1. Select specific access point in the dropdown menu of the default graphical
network manager’s “indicator”.
2. Enter WiFi encryption password.
# What I expected
A connection to
** Package changed: 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/1738067
Title:
cfg80211 crashes when trying to connect to encrypted access point
Status in
The workaround by adding the proposed repository into package
repositories in MAAS worked for me. Thanks for the help!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1737640
Title:
Public bug reported:
Notebook: ASUS GL703VD
Touchpad: probably ELAN clickpad
it seems to be connected to i2c bus
the modules loaded are elan_i2c and multitouch_hid
the multitouch hid module take almost 100% of cpu and the mouse cursor
moves badly (loosing it for a second or 2 then resuming)
In case anybody finds this via search, Dell put out a firmware patch
(Windows only right now) that upgrades the chip.
https://ludovicrousseau.blogspot.com/2016/08/broadcom-ccid-readers.html
I am also affected. :(
4 days ego I was Installing ubuntu 18.04 developer version.on my Lenovo E40-70
I was running win 10 upgraded from 8.1, I erased my hard disk and tried to
install ubuntu with new partitioning from ubuntu install wizard. and while
installation I got 'grub efi boot error'
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-trusty
** Tags added: block-proposed
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that
** 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
This bug was fixed in the package linux-aws - 4.4.0-1006.6
---
linux-aws (4.4.0-1006.6) trusty; urgency=low
* linux-aws: 4.4.0-1006.6 -proposed tracker (LP: #1737512)
[ Ubuntu: 4.4.0-104.127 ]
* linux: 4.4.0-104.127 -proposed tracker (LP: #1737511)
* upgrading linux-image
This bug was fixed in the package linux-aws - 4.4.0-1006.6
---
linux-aws (4.4.0-1006.6) trusty; urgency=low
* linux-aws: 4.4.0-1006.6 -proposed tracker (LP: #1737512)
[ Ubuntu: 4.4.0-104.127 ]
* linux: 4.4.0-104.127 -proposed tracker (LP: #1737511)
* upgrading linux-image
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1738257
Title:
package ubuntu-fan 0.12.8~16.04.1 failed to install/upgrade:
subprocess
** 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1737942
Title:
linux: 4.10.0-43.47 -proposed
Public bug reported:
I don't know
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: ubuntu-fan 0.12.8~16.04.1
ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
Uname: Linux 4.4.0-103-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.14
AptOrdering:
ubuntu-fan: Configure
NULL:
And here is the /proc/bus/input/devices
under
4.13.0-16-generic
** Attachment added: "cat /proc/bus/input/devices under 4.13.0-16-generic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1737639/+attachment/5022746/+files/devices-5
--
You received this bug notification because you
The package has been published 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:
** Summary changed:
- linux-aws: -proposed tracker
+ linux-aws: 4.4.0-1045.54 -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/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-precise
** Tags added: block-proposed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-trusty in Ubuntu.
The package has been published 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:
The package has been published 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 bug was fixed in the package linux-aws - 4.4.0-1044.53
---
linux-aws (4.4.0-1044.53) xenial; urgency=low
* linux-aws: 4.4.0-1044.53 -proposed tracker (LP: #1737515)
[ Ubuntu: 4.4.0-104.127 ]
* linux: 4.4.0-104.127 -proposed tracker (LP: #1737511)
* upgrading
** 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
This bug was fixed in the package linux-aws - 4.4.0-1044.53
---
linux-aws (4.4.0-1044.53) xenial; urgency=low
* linux-aws: 4.4.0-1044.53 -proposed tracker (LP: #1737515)
[ Ubuntu: 4.4.0-104.127 ]
* linux: 4.4.0-104.127 -proposed tracker (LP: #1737511)
* upgrading
** 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
This bug was fixed in the package linux - 4.4.0-104.127
---
linux (4.4.0-104.127) xenial; urgency=low
* linux: 4.4.0-104.127 -proposed tracker (LP: #1737511)
* upgrading linux-image package to 4.4.0-103.126 breaks Ceph network file
system connection (LP: #1737033)
-
I built Xenial, Zesty, Artful and Bionic test kernels, all with a cherry
pick of commit bbfcd77631573ac4a9f57eb6169e04256a111bc1. The test
kernels can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1738219/
Can you give these test kernels a try and see if they resolve this bug?
** Tags added: 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/1738105
Title:
asus zen ultrabook
This bug was fixed in the package linux - 4.4.0-104.127
---
linux (4.4.0-104.127) xenial; urgency=low
* linux: 4.4.0-104.127 -proposed tracker (LP: #1737511)
* upgrading linux-image package to 4.4.0-103.126 breaks Ceph network file
system connection (LP: #1737033)
-
This bug was fixed in the package linux - 4.4.0-104.127
---
linux (4.4.0-104.127) xenial; urgency=low
* linux: 4.4.0-104.127 -proposed tracker (LP: #1737511)
* upgrading linux-image package to 4.4.0-103.126 breaks Ceph network file
system connection (LP: #1737033)
-
** Changed in: kernel-sru-workflow/snap-release-to-stable
Status: New => Invalid
--
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/1737920
Title:
linux-aws: 4.4.0-1045.54
The I2C comment gave me a hint, which led to a solution.
But I still have a question of what changed and what can be done to warn
the user about the change.
I removed the file:
/etc/modprobe.d/blacklist_i2c_hid.conf?field.comment=The I2C comment
gave me a hint.
I removed the file:
Hello Thadeu, or anyone else affected,
Accepted makedumpfile into artful-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.1-2ubuntu0.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package.
Hello bugproxy, or anyone else affected,
Accepted makedumpfile into artful-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.1-2ubuntu0.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new
** 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/1737752
Title:
nvidia-graphics-drivers-384 384.90-0ubuntu6 ADT
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-xenial
** Tags added: block-proposed
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that
there is no need for logs because I checked them all and there is no clue about
the cause.
ANYWAYS, a guy with the same problem on a simlar notebook solved by patching 2
kernel modules.
Please read this:
https://patchwork.kernel.org/patch/9710953/
** Changed in: linux (Ubuntu)
Status:
Default Comment by Bridge
** Attachment added: "fix for bionic"
https://bugs.launchpad.net/bugs/1658733/+attachment/5022764/+files/makedumpfile_1.6.2-1ubuntu0.1.diff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in
I'm wondering, is it realy ubuntu 17.10 bug, or it may be just a
symptom... and our BIOSes was corrupted erlier? Before we noticed the
disease.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
On Thu, Dec 14, 2017 at 09:21:31PM -, Pavel wrote:
> I'm wondering, is it realy ubuntu 17.10 bug, or it may be just a
> symptom... and our BIOSes was corrupted erlier? Before we noticed the
> disease.
With so many users reporting this only after using Ubuntu 17.10, and at
least one user
Attaching an update to fix issues with 4.15, along with a fix for an
issue that was missed when updating for 4.14. Note that the following
kernel patch from the Ubuntu unstable tree is also needed in order to
build with 4.15:
commit 5c07f2a3183e7fae55a990525fc6f407512fb23d
Author: Seth Forshee
No, I've enabled virtualization technology just a bit before installing
Ubuntu, and Ubuntu did manage to write it's name into one of the boot
entries in my bios
Le 14 déc. 2017 22:30, "Pavel" <1734...@bugs.launchpad.net> a écrit :
> I'm wondering, is it realy ubuntu 17.10 bug, or it may be
Hello bugproxy, or anyone else affected,
Accepted makedumpfile into xenial-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/makedumpfile/1:1.5.9-5ubuntu0.6 in
a few hours, and then in the -proposed repository.
Please help us by testing this new
Default Comment by Bridge
** Attachment added: "target fix for artful"
https://bugs.launchpad.net/bugs/1658733/+attachment/5022763/+files/makedumpfile_1.6.1-2ubuntu0.1.diff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools
1 - 100 of 162 matches
Mail list logo
