I finally found 1st commit (not connected with USB problem) which prevents
booting, but it is corrected much later in 4.10-rc8.I don't know how to locate
correction commit for the one below
$ git bisect bad
174cc7187e6f088942c8e74daa7baff7b44b33c9 is the first bad commit
commit 174cc7187e6f088942
** Tags removed: apport-collected bionic verification-needed-bionic
** Tags added: verification-done-bionic
--
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/1819485
Title:
x86: add support
*** This bug is a duplicate of bug 1833438 ***
https://bugs.launchpad.net/bugs/1833438
** 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:
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
derivatives: bug 1833436 (azure-kernel), bug 18334
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
backports: bug 1833438 (bionic/linux-azure)
-- sw
** 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-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1832582
Title:
linux-aws: 4.4.0-1086
** 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 1832507 (bionic/li
*** This bug is a duplicate of bug 1833439 ***
https://bugs.launchpad.net/bugs/1833439
** 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:
** 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
+ https://wiki.ubuntu.com/Kernel/ker
** 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:
https
** 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
derivatives: bug 1833436 (azure-k
** 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
derivatives: bug 1832581 (aws-ker
** 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
** 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 --
boot-testi
** 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 --
boot-testi
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/regression-testing
Status: New => Confirmed
** Changed in: kernel-sru
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1833142
Title:
package linux-image-4.4.0-151-generic 4.4.0-151.178 faile
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/regression-testing
Status: New => Confirmed
** Changed in: kernel-sru
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1833142
Title:
package linux-image-4.4.0-151-generic 4.4.0-151.178 failed to
install/upgrade
Hi Daniel & Kei-Heng, thanks for the suggestions.
rfkill doesn't do much
> martin@martin-N15-17RD:~$ rfkill unblock 0
> rfkill: invalid identifier: 0
I'll try the kernel you suggested next.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed t
Kai-Heng: thanks for the suggestion, bluetooth now switches on & I can
pair with devices.
Output of "dmesg | grep -i bluetooth" looks healthier too:
martin@martin-N15-17RD:~$ dmesg | grep -i bluetooth
[ 18.577708] Bluetooth: Core ver 2.22
[ 18.577724] Bluetooth: HCI device and connection mana
** Summary changed:
- linux-fips: -proposed tracker
+ linux-fips: 4.4.0-1013.17 -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-
Verfied fix by reporter
** Tags removed: amd64 apport-bug apport-collected verification-needed-xenial
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.launchpad.
I tested with Kernel:
Linux tor3 4.4.0-149-generic #175+lp1824687v4 SMP Mon May 27 17:21:02 UTC 2019
x86_64 x86_64 x86_64 GNU/Linux
IPv6 is enabled and the system is under usual load.
No crashes in 24h.
For me this is a clear indication that the problem is fixed. Before there where
crashes all
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Invalid
** Changed in: kernel-sru-workflow/security-signoff
Status: New => Invalid
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the t
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Project changed: kernel => ubuntu
** No longer affects: 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/bug
** Changed in: linux (Ubuntu Bionic)
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/1833464
Title:
Request backports of ceph client commits to bionic ke
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Connor Kuehl (connork)
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Status: New
**
Kernel : 4.4.0-151
-- Logs begin at mer. 2019-06-19 22:32:00 CEST, end at mer. 2019-06-19 22:40:41
CEST. --
juin 19 22:32:01 JB-Notebook kernel: microcode: microcode updated early to
revision 0x60f, date = 2010-09-29
juin 19 22:32:01 JB-Notebook kernel: Linux version 4.15.0-52-generic
(buildd@l
** Information type changed from Private to Public
--
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/1832082
Title:
bnx2x driver causes 100% CPU load
Status in linux package in Ubuntu:
N
as an fyi ...
It has been brought to my attention that this could impact other system
(outside vmware context)
so I still suspect a userspace change (possibly mutter) that introduce
behaviour change and break the interaction with certain part of the 4.15 kernel.
Do we know if the recent point r
To continue on my comment #59 ... One user has been impacted on a
physical machine (non-vmware) with the same symptom but can't provide
public details unfortunately, but I witnessed the problem from my own
eye via remote session, and again upgrading to 4.18 kernel did the
trick.
So it really seems
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 1832082
and then change the status of the bug to 'Confirmed'.
If, due to the nature
According to this MS Documentation:
https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/reference/integration-services
The hv_fcopy_daemon have a low impact on VM.
The role of this daemon isn't necessary to a Azure VM, as you will not use it
to copy files from/to VM (This could be
Targeted the bug to cosmic only since bionic/azure is a backport of
cosmic/azure and so will get the fix automatically.
** Also affects: linux-azure (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Changed in: linux-azure (Ubuntu Cosmic)
Status: New => Fix Committed
--
You
** Changed in: gnome-shell
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-384 in Ubuntu.
https://bugs.launchpad.net/bugs/1705369
Title:
Ubuntu boots to blank screen when using
** Summary changed:
- linux-azure: -proposed tracker
+ linux-azure: 4.18.0-1022.22 -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-kern
** 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 1833438 (bionic/li
This bug was fixed in the package s390-tools - 2.9.0-0ubuntu3
---
s390-tools (2.9.0-0ubuntu3) eoan; urgency=medium
* Fix FTBFS LP: #1833238
-- Dimitri John Ledkov Wed, 19 Jun 2019 14:28:12
+0100
** Changed in: s390-tools (Ubuntu)
Status: Fix Committed => Fix Released
--
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: gnome-bluetooth (Ubuntu)
Status: Incomplete => Invalid
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete
> Do you know what change could have introduced this vmwgfx/wayland
interaction problem inside mutter in the first place ?
Technically it was a whole point release. The trigger could be any
change that went into mutter 3.28.4 as well as any Ubuntu patch. As
mentioned in comment #31, my suspicion i
** Changed in: mutter (Ubuntu Bionic)
Status: Won't Fix => 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/1832138
Title:
Login screen never appears on vmwgfx but instal
** Changed in: mutter (Ubuntu Bionic)
Importance: Undecided => High
--
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/1832138
Title:
Login screen never appears on vmwgfx but installing k
My reproducer:
1) I used virtualbox 6.0.0 on disco (my desktop machine) # I guess it doesn't
really matter but I prefer giving more details than less ;)
2) Deploy a VM with Ubuntu 18.04.1 (which come w/ 4.15)
3) Make sure in the VM setting that the display uses 'VMSVGA' which will force
the OS t
Public bug reported:
[Impact]
Dell machines which uses goodix touchpad IC emit double click event
while touching the touchpad if designware i2c adapter is in runtime
suspend.
Goodix re-assert the interrupt if host doesn't read the data within
100ms and designware takes a longer time to wake up fr
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
** Also affects: linux-oem-osp1 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: linux-oem-osp1 (Ubuntu Disco)
Impor
Because it was mentioned in comment #15 & #34 that this bug cannot be
reproduced, I decided to create a VMWare VM from scratch which managed
to be affected on my first attempt.
I started with ubuntu-18.04.1-desktop-amd64.iso
(19e10acddd14af9a9150399d876b02933c0ee724) and created a snapshot with
al
It also sounds like VirtualBox might allow me to reproduce the bug...
** Changed in: mutter (Ubuntu Bionic)
Status: Incomplete => 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.n
The fix is now released. Spinning up a new ISO as we speak.
calamares-settings-ubuntu (1:19.10.2) eoan; urgency=medium
* Fix initramfs job failing. Thanks to TJ for the fix! (LP: #1829805)
* Move before_bootloader_mkdirs process before initramfs.
* Workaround bug in update-initramfs::ge
** 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
**
** Also affects: linux-firmware (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux-firmware (Ubuntu Eoan)
Importance: Undecided
Assignee: Hui Wang (hui.wang)
Status: New
** Also affects: linux-firmware (Ubuntu Disco)
Importance: Undecided
S
** 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
derivatives: bug 1832558 (gcp-ker
** 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/1833484
Title:
Sometimes touchpad automatically trigger double click
Status in HWE Next:
New
Status in linux packag
** 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
derivatives: bug 1832558 (gcp-ker
Here is the v2 patch.
** Patch added:
"v2-0001-UBUNTU-SAUCE-i2c-designware-Add-disable-runtime-p.patch"
https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1833484/+attachment/5271688/+files/v2-0001-UBUNTU-SAUCE-i2c-designware-Add-disable-runtime-p.patch
--
You received this bug n
> Per the above, are we safe to grab the latest kernel upgrades now and
do away with the dis_ucode_ldr workaround in grub at this point?
Hi, no, or at least problematic.
I don't know if/why it seemed to work for me at that time. Now I was NOT able
to boot ubuntu 5.0/4.18 kernels without the dis_
** 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
derivatives: bug 1832558 (gcp-ker
Added WORKAROUND 3: BIOS upgrade
Please note this workaround is permanent and cannot be reverted, unlike 1,2. So
I will not be able to test this bug anymore.
** Description changed:
Description:
- my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of
booting, after gru
Hello You-Sheng, or anyone else affected,
Accepted linux-firmware into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.173.7 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. Se
Hello AceLan, or anyone else affected,
Accepted linux-firmware into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.173.7 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
h
Hello AaronMa, or anyone else affected,
Accepted linux-firmware into cosmic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.175.5 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello AaronMa, or anyone else affected,
Accepted linux-firmware into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.173.7 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
101 - 162 of 162 matches
Mail list logo
