No graphic desktop environment on Google GCP instances

Bug #2039732 reported by John Cabaj
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux-gcp (Ubuntu)
Fix Released
High
John Cabaj
Jammy
Fix Released
High
John Cabaj
Lunar
Fix Released
High
John Cabaj
Mantic
Fix Released
High
John Cabaj

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

John Cabaj (john-cabaj)
description: updated
John Cabaj (john-cabaj)
Changed in linux-gcp (Ubuntu Jammy):
status: New → In Progress
Changed in linux-gcp (Ubuntu Lunar):
status: New → In Progress
Changed in linux-gcp (Ubuntu Mantic):
status: New → In Progress
Changed in linux-gcp (Ubuntu Jammy):
importance: Undecided → High
Changed in linux-gcp (Ubuntu Lunar):
importance: Undecided → High
Changed in linux-gcp (Ubuntu Mantic):
importance: Undecided → High
Changed in linux-gcp (Ubuntu Jammy):
assignee: nobody → John Cabaj (john-cabaj)
Changed in linux-gcp (Ubuntu Lunar):
assignee: nobody → John Cabaj (john-cabaj)
Changed in linux-gcp (Ubuntu Mantic):
assignee: nobody → John Cabaj (john-cabaj)
John Cabaj (john-cabaj)
Changed in linux-gcp (Ubuntu Jammy):
status: In Progress → Fix Committed
Changed in linux-gcp (Ubuntu Lunar):
status: In Progress → Fix Committed
Changed in linux-gcp (Ubuntu Mantic):
status: In Progress → Fix Committed
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-gcp/5.15.0-1047.55 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-gcp' to 'verification-done-jammy-linux-gcp'. If the problem still exists, change the tag 'verification-needed-jammy-linux-gcp' to 'verification-failed-jammy-linux-gcp'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-jammy-linux-gcp-v2 verification-needed-jammy-linux-gcp
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-gcp/6.2.0-1019.21 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux-gcp' to 'verification-done-lunar-linux-gcp'. If the problem still exists, change the tag 'verification-needed-lunar-linux-gcp' to 'verification-failed-lunar-linux-gcp'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-lunar-linux-gcp-v2 verification-needed-lunar-linux-gcp
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-gcp/6.5.0-1009.9 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-gcp' to 'verification-done-mantic-linux-gcp'. If the problem still exists, change the tag 'verification-needed-mantic-linux-gcp' to 'verification-failed-mantic-linux-gcp'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-mantic-linux-gcp-v2 verification-needed-mantic-linux-gcp
Revision history for this message
Pete Moore (petemoore) wrote :

Jawed, can you confirm that somebody at Google will be taking a look at this?
Many thanks,
Pete

Revision history for this message
Jawed Abbasi (jabbasi) wrote :

Kyler

Can you please clarify who is asking who to verify proposed solution in linux-gcp/6.5.0-1009.9 kernel in comment#3 above?

Is it waiting on Google or this is between your internal canonical teams?

Revision history for this message
John Cabaj (john-cabaj) wrote :

Verified all configuration changes are in latest release.

tags: added: verification-done-jammy-linux-gcp verification-done-lunar-linux-gcp verification-done-mantic-linux-gcp
removed: verification-needed-jammy-linux-gcp verification-needed-lunar-linux-gcp verification-needed-mantic-linux-gcp
Revision history for this message
Launchpad Janitor (janitor) wrote :

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 <email address hidden> Fri, 03 Nov 2023 15:14:39 +0100

Changed in linux-gcp (Ubuntu Jammy):
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux-gcp - 6.2.0-1019.21

---------------
linux-gcp (6.2.0-1019.21) lunar; urgency=medium

  * lunar/linux-gcp: 6.2.0-1019.21 -proposed tracker (LP: #2041886)

  * Include cifs.ko in linux-modules package (LP: #2042546)
    - [Packaging] Replace fs/cifs with fs/smb/client in inclusion list

  * No graphic desktop environment on Google GCP instances (LP: #2039732)
    - [Config] gcp: Inherit CONFIG_SYSFB_SIMPLEFB from master

  * Kernel oops on 32-0bit kernels due to x86_cache_alignment initialization
    (LP: #2039191)
    - x86/boot: Move x86_cache_alignment initialization to correct spot

  [ Ubuntu: 6.2.0-37.38 ]

  * lunar/linux: 6.2.0-37.38 -proposed tracker (LP: #2041899)
  * CVE-2023-31085
    - ubi: Refuse attaching if mtd's erasesize is 0
  * CVE-2023-25775
    - RDMA/irdma: Prevent zero-length STAG registration
  * CVE-2023-45871
    - igb: set max size RX buffer when store bad packet is enabled
  * CVE-2023-5345
    - fs/smb/client: Reset password pointer to NULL
  * CVE-2023-5090
    - x86: KVM: SVM: always update the x2avic msr interception
  * Packaging resync (LP: #1786013)
    - [Packaging] update helper scripts

 -- Manuel Diewald <email address hidden> Thu, 02 Nov 2023 21:47:27 +0100

Changed in linux-gcp (Ubuntu Lunar):
status: Fix Committed → Fix Released
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-gcp-tcpx/5.15.0-1003.3 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux-gcp-tcpx' to 'verification-done-focal-linux-gcp-tcpx'. If the problem still exists, change the tag 'verification-needed-focal-linux-gcp-tcpx' to 'verification-failed-focal-linux-gcp-tcpx'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-focal-linux-gcp-tcpx-v2 verification-needed-focal-linux-gcp-tcpx
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux-gcp - 6.5.0-1009.9

---------------
linux-gcp (6.5.0-1009.9) mantic; urgency=medium

  * mantic/linux-gcp: 6.5.0-1009.9 -proposed tracker (LP: #2041870)

  * No graphic desktop environment on Google GCP instances (LP: #2039732)
    - [Config] gcp: Inherit CONFIG_SYSFB_SIMPLEFB from master

  [ Ubuntu: 6.5.0-13.13 ]

  * mantic/linux: 6.5.0-13.13 -proposed tracker (LP: #2042652)
  * arm64 atomic issues cause disk corruption (LP: #2042573)
    - locking/atomic: scripts: fix fallback ifdeffery

  [ Ubuntu: 6.5.0-11.11 ]

  * mantic/linux: 6.5.0-11.11 -proposed tracker (LP: #2041879)
  * CVE-2023-31085
    - ubi: Refuse attaching if mtd's erasesize is 0
  * CVE-2023-4244
    - netfilter: nft_set_rbtree: skip sync GC for new elements in this transaction
  * CVE-2023-5633
    - drm/vmwgfx: Keep a gem reference to user bos in surfaces
  * CVE-2023-5345
    - fs/smb/client: Reset password pointer to NULL
  * CVE-2023-5090
    - x86: KVM: SVM: always update the x2avic msr interception
  * Packaging resync (LP: #1786013)
    - [Packaging] update helper scripts

 -- Stefan Bader <email address hidden> Tue, 07 Nov 2023 15:34:18 +0200

Changed in linux-gcp (Ubuntu Mantic):
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (87.2 KiB)

This bug was fixed in the package linux-gcp - 6.6.0-1001.1

---------------
linux-gcp (6.6.0-1001.1) noble; urgency=medium

  * noble/linux-gcp: 6.6.0-1001.1 -proposed tracker (LP: #2045153)

  * Packaging resync (LP: #1786013)
    - [Packaging] update update.conf
    - debian/dkms-versions -- update from kernel-versions (main/d2023.11.21)

  * Miscellaneous Ubuntu changes
    - [Config] updateconfigs after Ubuntu-6.6.0-14.14 rebase

  [ Ubuntu: 6.6.0-14.14 ]

  * noble/linux: 6.6.0-14.14 -proposed tracker (LP: #2045243)
  * Noble update: v6.6.3 upstream stable release (LP: #2045244)
    - locking/ww_mutex/test: Fix potential workqueue corruption
    - btrfs: abort transaction on generation mismatch when marking eb as dirty
    - lib/generic-radix-tree.c: Don't overflow in peek()
    - x86/retpoline: Make sure there are no unconverted return thunks due to KCSAN
    - perf/core: Bail out early if the request AUX area is out of bound
    - srcu: Fix srcu_struct node grpmask overflow on 64-bit systems
    - selftests/lkdtm: Disable CONFIG_UBSAN_TRAP in test config
    - clocksource/drivers/timer-imx-gpt: Fix potential memory leak
    - clocksource/drivers/timer-atmel-tcb: Fix initialization on SAM9 hardware
    - srcu: Only accelerate on enqueue time
    - smp,csd: Throw an error if a CSD lock is stuck for too long
    - cpu/hotplug: Don't offline the last non-isolated CPU
    - workqueue: Provide one lock class key per work_on_cpu() callsite
    - x86/mm: Drop the 4 MB restriction on minimal NUMA node memory size
    - wifi: plfxlc: fix clang-specific fortify warning
    - wifi: ath12k: Ignore fragments from uninitialized peer in dp
    - wifi: mac80211_hwsim: fix clang-specific fortify warning
    - wifi: mac80211: don't return unset power in ieee80211_get_tx_power()
    - atl1c: Work around the DMA RX overflow issue
    - bpf: Detect IP == ksym.end as part of BPF program
    - wifi: ath9k: fix clang-specific fortify warnings
    - wifi: ath12k: fix possible out-of-bound read in ath12k_htt_pull_ppdu_stats()
    - wifi: ath10k: fix clang-specific fortify warning
    - wifi: ath12k: fix possible out-of-bound write in
      ath12k_wmi_ext_hal_reg_caps()
    - ACPI: APEI: Fix AER info corruption when error status data has multiple
      sections
    - net: sfp: add quirk for Fiberstone GPON-ONU-34-20BI
    - wifi: mt76: mt7921e: Support MT7992 IP in Xiaomi Redmibook 15 Pro (2023)
    - wifi: mt76: fix clang-specific fortify warnings
    - net: annotate data-races around sk->sk_tx_queue_mapping
    - net: annotate data-races around sk->sk_dst_pending_confirm
    - wifi: ath12k: mhi: fix potential memory leak in ath12k_mhi_register()
    - wifi: ath10k: Don't touch the CE interrupt registers after power up
    - net: sfp: add quirk for FS's 2.5G copper SFP
    - vsock: read from socket's error queue
    - bpf: Ensure proper register state printing for cond jumps
    - wifi: iwlwifi: mvm: fix size check for fw_link_id
    - Bluetooth: btusb: Add date->evt_skb is NULL check
    - Bluetooth: Fix double free in hci_conn_cleanup
    - ACPI: EC: Add quirk for HP 250 G7 Notebook PC
    - tsnep: Fix tsnep_request_irq() format-overflow warning
    - gpiolib:...

Changed in linux-gcp (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.