Screen corruption of slides during install on Raspberry Pi 4
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| ubiquity (Ubuntu) | Status tracked in Noble | |||||
| Mantic |
Confirmed
|
Low
|
Dave Jones | |||
| Noble |
Confirmed
|
Low
|
Dave Jones | |||
Bug Description
During the initial configuration of the Ubuntu Desktop for Raspberry Pi (the oem-config process, derived from ubiquity), on the Mantic beta images, after the various pages of information have been filled out and the process moves onto configuration, the "slide deck" that is usually displayed during the process appeared corrupted as if a horizontal stride were incorrectly set somewhere.
I'm attached a photo of the screen (as, while I could take a screenshot during the process, it evidently wasn't saved somewhere persistent).
I originally thought this might be a regression of LP: #1924251 as the corruption in the window looks very similar (incorrect horizontal stride causing "banding"), but I tested the embedded browser (via the help system) after completing setup and it worked perfectly so that's *probably* unrelated.
| Dave Jones (waveform) wrote | #1 |
| tags: | added: raspi-image rls-mm-incoming |
| description: | updated |
| tags: |
added: foundations-todo removed: rls-mm-incoming |
| Changed in ubiquity (Ubuntu): | |
| assignee: | nobody → Julian Andres Klode (juliank) |
| importance: | Undecided → High |
| status: | New → Triaged |
| assignee: | Julian Andres Klode (juliank) → Dave Jones (waveform) |
| Dave Jones (waveform) wrote | #3 |
| Changed in ubiquity (Ubuntu): | |
| status: | Triaged → Fix Released |
| Dave Jones (waveform) wrote | #4 |
| Changed in ubiquity (Ubuntu): | |
| status: | Fix Released → Confirmed |
| importance: | High → Low |
| summary: |
- Screen corruption of slides during install on Raspberry Pi + Screen corruption of slides during install on Raspberry Pi 4 |
| Paride Legovini (paride) wrote | #5 |
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
https:/