No graphic desktop environment on Google GCP instances

Bug #2039732 reported by John Cabaj
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux-gcp (Ubuntu)
In Progress
High
John Cabaj
Jammy
Fix Committed
High
John Cabaj
Lunar
Fix Committed
High
John Cabaj
Mantic
Fix Committed
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
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.