[Kernel-packages] [Bug 1721481] [NEW] Building kernel module fails

2017-10-05 Thread Stephan Springer
Public bug reported: Preparing to unpack .../bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu1~1.1_amd64.deb ... Removing all DKMS Modules Done. Unpacking bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu1~1.1) over (6.30.223.271+bdcom-0ubuntu1~1.1) ... Setting up bcmwl-kernel-source

[Kernel-packages] [Bug 1721477] Re: Xenial update to 4.4.89 stable release

2017-10-05 Thread Stefan Bader
Skipped "tcp: initialize rcv_mss to TCP_MIN_MSS instead of 0" because it is already applied for CVE-2017-14106. Accepted fuzz 1 for "scsi: storvsc: fix memory leak on ring buffer busy". ** Description changed: + SRU Justification - SRU Justification + Impact: +    The upstream

[Kernel-packages] [Bug 1721482] [NEW] watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [CompositorTileW:29904]

2017-10-05 Thread Mynk
Public bug reported: The system went crazy. Was trying to install gcs-fuse just before that. But did not get to it. Just the update command. Not sure if that installed something. ProblemType: KernelOops DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13

[Kernel-packages] [Bug 1721483] [NEW] watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [CompositorTileW:29904]

2017-10-05 Thread Mynk
Public bug reported: One issue has led to the collapse of the system. Multiple bugs being reported. ProblemType: KernelOops DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic

[Kernel-packages] [Bug 1721477] [NEW] Xenial update to 4.4.89 stable release

2017-10-05 Thread Stefan Bader
Public bug reported: SRU Justification Impact:    The upstream process for stable tree updates is quite similar    in scope to the Ubuntu SRU process, e.g., each patch has to    demonstrably fix a bug, and each patch is vetted by upstream    by originating either directly

[Kernel-packages] [Bug 1720042] Re: linux-aws: 4.4.0-1038.47 -proposed tracker

2017-10-05 Thread Taihsiang Ho
** 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/1720042 Title: linux-aws: 4.4.0-1038.47

[Kernel-packages] [Bug 1721455] Re: Support Dell Wireless DW5819/5818 WWAN devices

2017-10-05 Thread Shrirang Bagul
** Description changed: - [Fix] + [Impact] Dell Wireless 5819/5818 devices are re-branded Sierra Wireless MC74 series which will by default boot with vid 0x413c and pid's 0x81cf, 0x81d0, 0x81d1,0x81d2. + [Fix] This patch has already been submitted upstream, reviewed and applied by

[Kernel-packages] [Bug 1721455] Re: Support Dell Wireless DW5819/5818 WWAN devices

2017-10-05 Thread Shrirang Bagul
** Changed in: linux (Ubuntu) Importance: Undecided => Critical ** Changed in: linux (Ubuntu) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1721455] Re: Support Dell Wireless DW5819/5818 WWAN devices

2017-10-05 Thread Shrirang Bagul
** Description changed: [Fix] Dell Wireless 5819/5818 devices are re-branded Sierra Wireless MC74 series which will by default boot with vid 0x413c and pid's 0x81cf, 0x81d0, 0x81d1,0x81d2. - This patch has already been submitted upstream by linux-usb serial maintainer. - [PATCH] USB:

[Kernel-packages] [Bug 1721400] Re: Screen dim during encryption unlock prompt

2017-10-05 Thread Jean-Baptiste Lallement
** Tags removed: wayland-session -- 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/1721400 Title: Screen dim during encryption unlock prompt Status in linux package in Ubuntu: Confirmed

[Kernel-packages] [Bug 1721455] Re: Support Dell Wireless DW5819/5818 WWAN devices

2017-10-05 Thread Shrirang Bagul
** Description changed: - Dell Wireless 5819/5818 devices are re-branded Sierra Wireless MC74 - series which will by default boot with vid 0x413c and pid's 0x81cf, - 0x81d0, 0x81d1,0x81d2. + [Fix] + Dell Wireless 5819/5818 devices are re-branded Sierra Wireless MC74 series which will by default

[Kernel-packages] [Bug 1721455] Missing required logs.

2017-10-05 Thread Ubuntu Kernel Bot
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 1721455 and then change the status of the bug to 'Confirmed'. If, due to the

[Kernel-packages] [Bug 1700657] Re: Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB

2017-10-05 Thread Stefan Bader
** Also affects: linux (Ubuntu Zesty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Zesty) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Zesty) Status: New => In Progress -- You received this bug notification because you are a member of

[Kernel-packages] [Bug 1721455] [NEW] Support Dell Wireless DW5819/5818 WWAN devices

2017-10-05 Thread Shrirang Bagul
Public bug reported: Dell Wireless 5819/5818 devices are re-branded Sierra Wireless MC74 series which will by default boot with vid 0x413c and pid's 0x81cf, 0x81d0, 0x81d1,0x81d2. This bug is used for tracking purposes, please do not triage. ** Affects: linux (Ubuntu) Importance: Undecided

[Kernel-packages] [Bug 1720622] Re: Cannot wake-up from sleep mode

2017-10-05 Thread Hadrien
I opened https://bugs.freedesktop.org/show_bug.cgi?id=103102 ** Bug watch added: freedesktop.org Bugzilla #103102 https://bugs.freedesktop.org/show_bug.cgi?id=103102 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1567597] Re: implement 'complain mode' in seccomp for developer mode with snaps

2017-10-05 Thread Tyler Hicks
** Description changed: A requirement for snappy is that a snap may be placed in developer mode which will put the security sandbox in complain mode such that violations against policy are logged, but permitted. In this manner learning tools can be written to parse the logs, etc and make

<    1   2