This bug was fixed in the package linux-gcp - 5.15.0-1047.55
---------------
linux-gcp (5.15.0-1047.55) jammy; urgency=medium
* jammy/linux-gcp: 5.15.0-1047.55 -proposed tracker (LP: #2041917)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/s2023.10.02)
* Incorrect argument from SEV live-migration fix (LP: #2040337)
- SAUCE: (no-up) x86/mm: Fixing notify_range_enc_status_changed incorrect
argument
* No graphic desktop environment on Google GCP instances (LP: #2039732)
- [Config] gcp: Inherit CONFIG_SYSFB_SIMPLEFB from master
[ Ubuntu: 5.15.0-89.99 ]
* jammy/linux: 5.15.0-89.99 -proposed tracker (LP: #2041949)
* CVE-2023-31085
- ubi: Refuse attaching if mtd's erasesize is 0
* CVE-2023-45871
- igb: set max size RX buffer when store bad packet is enabled
* CVE-2023-25775
- RDMA/irdma: Remove irdma_uk_mw_bind()
- RDMA/irdma: Remove irdma_sc_send_lsmm_nostag()
- RDMA/irdma: Remove irdma_cqp_up_map_cmd()
- RDMA/irdma: Remove irdma_get_hw_addr()
- RDMA/irdma: Make irdma_uk_cq_init() return a void
- RDMA/irdma: optimize rx path by removing unnecessary copy
- RDMA/irdma: Remove enum irdma_status_code
- RDMA/irdma: Remove excess error variables
- RDMA/irdma: Prevent zero-length STAG registration
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
-- Stefan Bader <stefan.ba...@canonical.com> Fri, 03 Nov 2023 15:14:39
+0100
** Changed in: linux-gcp (Ubuntu Jammy)
Status: Fix Committed => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-25775
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-31085
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-45871
** Changed in: linux-gcp (Ubuntu Lunar)
Status: Fix Committed => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-5090
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-5345
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/2039732
Title:
No graphic desktop environment on Google GCP instances
Status in linux-gcp package in Ubuntu:
In Progress
Status in linux-gcp source package in Jammy:
Fix Released
Status in linux-gcp source package in Lunar:
Fix Released
Status in linux-gcp source package in Mantic:
Fix Committed
Bug description:
[Impact]
* Google reports not being able to display graphic desktop
environment.
[Fix]
* CONFIG_SYSFB_SIMPLEFB was initially enabled in
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/jammy/commit/?h=master-
next&id=0bf2a2472f71a3001a8a9a0849b6bed7e7069a7b. It was subsequently
disabled for amd64 in https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/jammy/commit/?h=master-
next&id=40b0ce0833309133453c3dbc19753f62084c0a7a. This was not
reflected in the GCP kernel config.
[Test Case]
* Compile tested
* Boot tested
* To be tested by Google
[Where things could go wrong]
* Low chance of regression. Simple config change that was not taken
from generic.
[Other Info]
* SF #00366439
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2039732/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
