The latest firmware for X370 Taichi, v5.50 (2019/4/24), removes the "Power
Supply Idle Control" option off the configuration UI; downgrading is not
supported (but effectively possible at least from Windows). It is still
possible to set "Power Supply Idle Control" (C6 package) via MSR using e.g.
(In reply to Philip Rosvall from comment #593)
> Since 5.0.10, and this commit ...:
>
> (https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.0.10)
> "commit 205c53cbe553c9e5a9fe93f63e398da7e59124b6
> Author: Thomas Gleixner
> Date: Sun Apr 14 19:51:06 2019 +0200
>
> x86/speculation: P
(In reply to Moritz Naumann from comment #592)
> The latest firmware for X370 Taichi, v5.50 (2019/4/24), removes the "Power
> Supply Idle Control" option off the configuration UI; downgrading is not
> supported (but effectively possible at least from Windows). It is still
> possible to set "Power 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
backports: bug 1829179 (bionic/li
Would you mind testing an older oem kernel from bionic? Install 'linux-
image-4.15.0-1034-oem' and remember to select it from the boot menu.
--
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/1
** Summary changed:
- linux-azure: -proposed tracker
+ linux-azure: 4.18.0-1019.19 -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
** Changed in: kernel-sru-workflow/prepare-package-lrm
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags ad
** 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 1829208 (xenial/li
Please test upstream stable kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.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/1829310
Title:
kernel 5 fails to start systemd-
This is fixed in mainline, but not sure if upstream stable have this fix or not.
[ 48.065638] RIP: 0010:swiotlb_tbl_map_single+0x120/0x310
[ 48.065641] Code: 4c 8b 45 a8 4c 8b 1d af c7 a9 01 89 d3 45 31 d2 44 8b 4d
a4 44 89 c7 41 89 dc 4b 8d 44 25 00 48 21 f0 48 01 f8 49 39 c7 72 0a <47> 39 0c
** 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
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Khaled El Mously (kmously) => Stefan Bader (smb)
**
I have exactly the same bug on a newly purchased Asus VivoBook Flip 12 TP202NA.
The emmc is an SanDisk DF4032 749B806.
Lubuntu 18.04.2 installer finds for time to time the emmc but I've never
been able to boot the system successfully.
--
You received this bug notification because you are a membe
** Tags added: originate-from-1827349
--
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/1826716
Title:
Include Sunix serial/parallel driver
Status in HWE Next:
New
Status in linux-oe
** Summary changed:
- linux-oracle: -proposed tracker
+ linux-oracle: 4.15.0-1013.15 -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-ke
Does this issue happen on 16.04?
--
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/1829228
Title:
boot time is too long
Status in linux package in Ubuntu:
Confirmed
Bug description:
b
[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.
https://bugs.launchpad.net/bu
** Changed in: ubuntu-kernel-tests
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/1813134
Title:
cp_abort in powerpc/context_switch from ubunu
This bug was fixed in the package dkms - 2.6.1-4ubuntu3
---
dkms (2.6.1-4ubuntu3) eoan; urgency=medium
[ Alex Tu ]
* debian/patches/0017-fix-OBSOLETE_BY-in-DKMS.CONF-Closes-81.patch:
Fix support for OBSOLETE_BY in DKMS.CONF (LP: #1828948)
-- Mathieu Trudel-Lapierre Tue, 14
** Summary changed:
- I get this annoying warning every single day every time when i start my
laptop.
+ Got "MODSIGN: Couldn't get UEFI db list" warning when I start my laptop
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubun
Test was executed against a Bionic source tree instead of the Xenial
one, retested with the correct tree and passed.
** Changed in: ubuntu-kernel-tests
Status: New => Invalid
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because
Test was executed against a Bionic source tree instead of the Xenial
one, retested with the correct tree and passed.
** Changed in: ubuntu-kernel-tests
Status: New => Invalid
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because
Test was executed against a Bionic source tree instead of the Xenial
one, retested with the correct tree and passed.
** Changed in: ubuntu-kernel-tests
Status: New => Invalid
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because
Test was executed against a Bionic source tree instead of the Xenial
one, retested with the correct tree and passed.
** Changed in: ubuntu-kernel-tests
Status: New => Invalid
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because
Test was executed against a Bionic source tree instead of the Xenial
one, retested with the correct tree and passed.
** Changed in: ubuntu-kernel-tests
Status: New => Invalid
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because
Test was executed against a Bionic source tree instead of the Xenial
one, retested with the correct tree and passed.
** Changed in: ubuntu-kernel-tests
Status: New => Invalid
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because
Test was executed against a Bionic source tree instead of the Xenial
one, retested with the correct tree and passed.
** Changed in: ubuntu-kernel-tests
Status: New => Invalid
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
** Changed in: ubuntu-kernel-tests
Status: New => 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/1828912
/var/log/syslog shows the following line whenever it freezes up:
May 15 21:41:06 SOLAIRE /usr/lib/gdm3/gdm-x-session[26978]: nvLock: client
timed out, taking the lock
May 15 21:41:13 SOLAIRE /usr/lib/gdm3/gdm-x-session[26978]: nvLock: client
timed out, taking the lock
May 15 21:58:43 SOLAIRE /us
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/1829228
Title:
boot time is too long
Status
Please be careful to only report one problem per bug. I will make this
bug just about the long boot time. If you want to discuss the other
issue then please open another bug.
Your long boot time appears to be multiple problems in the kernel log
(CurrentDmesg.txt). I can't quite put my finger on ju
Happening to me as well, with 418 drive, on 19.04 with a Geforce 940MX
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu.
https://bugs.launchpad.net/bugs/1825626
Title:
nvLock: client timed out, takin
You have been subscribed to a public bug:
boot time is too long and running HD videos starts flickering
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
Uname: Linux 4.15.0-48-generic x86_64
NonfreeKernelModules
** Tags removed: need-duplicate-check
--
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/1829315
Title:
package linux-image-5.0.0-14-generic 5.0.0-14.15 failed to
install/upgrade: installe
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/1829315
Title:
package linux-image-5.0.0-14-g
Public bug reported:
-dkms reported sgx error
-deleted sgx dkms folder
-fixed bug
-intel sgx did not support ubuntu disco 19.04 yet
ProblemType: Package
DistroRelease: Ubuntu 19.04
Package: linux-image-5.0.0-14-generic 5.0.0-14.15
ProcVersionSignature: Ubuntu 5.0.0-15.16-lowlatency 5.0.6
Uname:
** Also affects: linux (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: udisks2 (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Eoan)
Imp
using kernel 5 for kubuntu 19.04, I have no network interface and thus
no internet connection so I can't run that apport-collect command.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which
** 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
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 1829310
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Public bug reported:
linux kernel 5.0.0-13
Kubuntu 19.04
hardware: old Dell laptop Inspiron 1720
After upgrading an old Dell laptop Inspiron 1720 (from 2007 I think) from
Kubuntu 18.10 to 19.04, the result is a broken system:
booting takes + 5 minutes
looking at the boot messages I see "Failed t
rds is also blocked by default in ubuntu, via the /etc/modprobe.d
/blacklist-rare-network.conf configuration file.
# rds
alias net-pf-21 off
It's also not entirely clear that this is actually remotely exploitable,
as network namespace exit is normally a local action, which is what
would trigg
Public bug reported:
[Impact]
Users cannot use the ethtool --identify command to help them identify a NIC's
physical port.
[Test Case]
sudo ethtool --identify
[Fix]
a93f7fe134543 net: phy: marvell: add new default led configure for m88e151x
[Regression Risk]
The fix is restricted to the Hi162
** Changed in: kernel-sru-workflow/snap-release-to-stable
Status: New => Invalid
** 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:
@dimitri are you still having this issue? There isn't much to go on in
this bug submission yet.
--
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/1824407
Title:
why does booting any livef
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 1829055
and then change the status of the bug to 'Confirmed'.
If, due to the nature
** Information type changed from Private Security to Public Security
--
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/1829055
Title:
CVE-2019-11815
Status in linux package in Ubuntu:
In
Hi Louis,
can you provide some information about the physical devices and also the
benchmark tool you are using for the benchmarking?
Thanks
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: linux (Ubuntu)
Status: Confirmed => In Prog
** Summary changed:
- linux-azure: -proposed tracker
+ linux-azure: 4.15.0-1046.50 -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 1829171 (bionic/li
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-xenial
** 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.
F
** Changed in: kernel-sru-workflow/snap-release-to-stable
Status: New => Invalid
** 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:
No, my device doesn't work with 6Gbps. In kernel 4.14 if my drive was
offline, function sata_down_spd_limit() cut down link->sata_spd_limit to
1, so it corresponds to 1.5Gbps, and was working. But it wasn't even try
to set limit to 3Gbps.
In my device, unfortunately mask and link->sata_spd_limit i
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bluez (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1823076
** Summary changed:
- linux-aws: -proposed tracker
+ linux-aws: 4.15.0-1040.42 -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-t
** 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 1829185 (bionic/li
** 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
(o
** 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 1829214 (xenial/li
This bug was fixed in the package linux-snapdragon - 4.4.0-1113.118
---
linux-snapdragon (4.4.0-1113.118) xenial; urgency=medium
[ Ubuntu: 4.4.0-148.174 ]
* CVE-2018-12126 // CVE-2018-12127 // CVE-2018-12130
- Documentation/l1tf: Fix small spelling typo
- perf/x86/intel:
This bug was fixed in the package linux-kvm - 4.4.0-1046.52
---
linux-kvm (4.4.0-1046.52) xenial; urgency=medium
[ Ubuntu: 4.4.0-148.174 ]
* CVE-2018-12126 // CVE-2018-12127 // CVE-2018-12130
- Documentation/l1tf: Fix small spelling typo
- perf/x86/intel: Add model number
This bug was fixed in the package linux-raspi2 - 4.4.0-1109.117
---
linux-raspi2 (4.4.0-1109.117) xenial; urgency=medium
[ Ubuntu: 4.4.0-148.174 ]
* CVE-2018-12126 // CVE-2018-12127 // CVE-2018-12130
- Documentation/l1tf: Fix small spelling typo
- perf/x86/intel: Add mode
Hello, we have the very same problem after upgrading to ubuntu 18.04 .
Server is not booting anymore, hanging on:
aacraid: Host Adapter abort request.
aacraid: Outstanding commands on (1,1,241,0):
aacraid: Host Adapter abort request.
aacraid: Outstanding commands on (1,1,242,0):
aacraid: Host Adap
This bug was fixed in the package linux-aws - 4.4.0-1083.93
---
linux-aws (4.4.0-1083.93) xenial; urgency=medium
[ Ubuntu: 4.4.0-148.174 ]
* CVE-2018-12126 // CVE-2018-12127 // CVE-2018-12130
- Documentation/l1tf: Fix small spelling typo
- perf/x86/intel: Add model number
This bug was fixed in the package linux-gcp - 4.15.0-1032.34~16.04.1
---
linux-gcp (4.15.0-1032.34~16.04.1) xenial; urgency=medium
[ Ubuntu: 4.15.0-1032.34 ]
* CVE-2018-12126 // CVE-2018-12127 // CVE-2018-12130
- Documentation/l1tf: Fix small spelling typo
- x86/cpu: Sani
This bug was fixed in the package linux-gcp - 4.15.0-1032.34~16.04.1
---
linux-gcp (4.15.0-1032.34~16.04.1) xenial; urgency=medium
[ Ubuntu: 4.15.0-1032.34 ]
* CVE-2018-12126 // CVE-2018-12127 // CVE-2018-12130
- Documentation/l1tf: Fix small spelling typo
- x86/cpu: Sani
This bug was fixed in the package linux-oracle - 4.15.0-1013.15~16.04.1
---
linux-oracle (4.15.0-1013.15~16.04.1) xenial; urgency=medium
[ Ubuntu: 4.15.0-1013.15 ]
* CVE-2018-12126 // CVE-2018-12127 // CVE-2018-12130
- Documentation/l1tf: Fix small spelling typo
- x86/cpu
This bug was fixed in the package linux-azure - 4.15.0-1045.49
---
linux-azure (4.15.0-1045.49) xenial; urgency=medium
* [linux-azure] Storage performance drop on RAID (LP: #1828248)
- Revert "blk-mq: remove the request_list usage"
[ Ubuntu: 4.15.0-50.54 ]
* CVE-2018-1212
This bug was fixed in the package linux-oracle - 4.15.0-1013.15~16.04.1
---
linux-oracle (4.15.0-1013.15~16.04.1) xenial; urgency=medium
[ Ubuntu: 4.15.0-1013.15 ]
* CVE-2018-12126 // CVE-2018-12127 // CVE-2018-12130
- Documentation/l1tf: Fix small spelling typo
- x86/cpu
Michael,
You will need the following for the 256 Cores:
https://bugs.launchpad.net/amd/+bug/1816669
--kim
--
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:
AMD Rome : Addit
I also confirm that Paco Angulo (3rpako)'s suggestion (#42) worked for
my laptop too. It's Asus with I7 core running Debian-10. Thanks Paco
Angulo.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
With Eoan we now always default to 4k, hence Fix Released in e2fsprogs
and the project.
--
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/1817097
Title:
pvmove causes file system corruption
I not sure upstream will let us change the value of mask.
Will you get the same result of you set sata_spd_limit?
link->sata_spd_limit = 0x7
I believe that corresponds to 6Gbps but I don't see a #define
we can use.
Also, is the comment accurate? Before you started debugging
did you see a hard r
** 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 --
kernel-sta
** Summary changed:
- linux-raspi2: -proposed tracker
+ linux-raspi2: 4.4.0-1110.118 -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-ke
Hi Kim,
I have tested this on a system, using Disco with 5.0 and I am currently
seeing only 255 cores, has support landed in Disco yet?
--
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/18194
Thanks! I was about to write to you saying that I wasn't finding the
failing tests :-)
I believe we can close the bugs.
--
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/1828912
Title:
Fai
** 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 --
kernel-sta
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 1829095
and then change the status of the bug to 'Confirmed'.
If, due to the nature
** 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 --
kernel-sta
This issue was apparently resolved with the release of 19.04 as I have
not encountered it since then. This report should be closed.
** No longer affects: lightdm (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
** Changed in: slick-greeter (Ubuntu)
Status: Incom
Hello Marcelo,
It looks like this was induced by running the test from the Bionic
source tree, instead of the Xenial tree.
I have corrected this on the infrastructure. And restart the kernel-
selftest against the same P8 box, all tests have passed.
This bug will only valid if we're gonna to port
** Summary changed:
- linux-raspi2: -proposed tracker
+ linux-raspi2: 4.15.0-1037.39 -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-ke
This bug was fixed in the package linux - 4.4.0-148.174
---
linux (4.4.0-148.174) xenial; urgency=medium
* CVE-2018-12126 // CVE-2018-12127 // CVE-2018-12130
- Documentation/l1tf: Fix small spelling typo
- perf/x86/intel: Add model number for Skylake Server to perf
- per
** Package changed: ubuntu-meta (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/1829095
Title:
Keyborad backligt does not work
Status in linux package in Ubunt
** Summary changed:
- linux-raspi2: -proposed tracker
+ linux-raspi2: 5.0.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 (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
-- swm properties --
kernel-sta
You have been subscribed to a public bug:
I have a dell XPS14 (L421X). In releases 18.04 and lower the keyboard
back light used to work. However in 18.10 and 19.04 it does not
The dell_laptop model is loaded.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: ubuntu-desktop 1.431
ProcVersio
** 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 --
kernel-sta
** Summary changed:
- linux-snapdragon: -proposed tracker
+ linux-snapdragon: 4.4.0-1114.119 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: (unassigned) => Kleber Saci
** Summary changed:
- linux-kvm: -proposed tracker
+ linux-kvm: 4.15.0-1035.35 -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-t
** 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 --
kernel-sta
nils,
Does mainline kernel still have this issue?
--
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/1785171
Title:
Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver
kee
** 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
** Changed in: kernel-sru-workflow/automated-testing
Status: Fix Released => New
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => New
** Changed in: kernel-sru-workflow/prepare-package
Status: Fix Released => New
** Changed in: kernel-sru-workflo
** Summary changed:
- linux-snapdragon: 4.4.0-1113.118 -proposed tracker
+ linux-snapdragon: -proposed tracker
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-snapdragon in Ubuntu.
https://bugs.launchpad.net/bugs/1829201
Title:
** Summary changed:
- linux-raspi2: -proposed tracker
+ linux-raspi2: 4.18.0-1015.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-ke
** 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/prepare-package
Status: In Progress => Fix Released
** Changed in: kernel-sru-wo
update-initramfs: deferring update (hook will be called later)
Failed to symbolic-link boot/initrd.img-3.13.0-30-generic to initrd.img:File
exists at /var/lib/dpkg/info/linux-image-3.13.0-30-generic.postinst line 629.
dpkg: error processing package linux-image-3.13.0-30-generic (--configure)
** 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 --
kernel-sta
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Tags added: trusty
--
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/1829258
Title:
package
1 - 100 of 335 matches
Mail list logo
