weird color change during oem-config debconf package removal step in serial installs

Bug #747229 reported by Oliver Grawert
30
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Release Notes for Ubuntu
Invalid
Undecided
Unassigned
ubiquity (Ubuntu)
Invalid
Medium
Unassigned
Natty
Won't Fix
Medium
Unassigned
Oneiric
Won't Fix
Medium
Unassigned
Precise
Won't Fix
Medium
Unassigned

Bug Description

Binary package hint: ubiquity

doing a serial install with the headless omap4 image via screen, i get proper coloring during all oem-config steps. once the package removal occurs, the UI color changes to some unreadable combination.

Revision history for this message
Oliver Grawert (ogra) wrote :
Changed in ubiquity (Ubuntu Natty):
importance: Undecided → Medium
milestone: none → ubuntu-11.04
Revision history for this message
Oliver Grawert (ogra) wrote :
tags: added: iso-testing
affects: ubiquity (Ubuntu Natty) → debian-installer (Ubuntu Natty)
Changed in debian-installer (Ubuntu Natty):
status: New → Triaged
Revision history for this message
Dustin Kirkland  (kirkland) wrote :

Oliver,

Can you reproduce this behavior if you add the kernel command line parameter FRONTEND_BACKGROUND=legacy? Could you screenshot the same two screens with this config parameter?

Thanks!
:-Dustin

Changed in debian-installer (Ubuntu Natty):
status: Triaged → Incomplete
Revision history for this message
Oliver Grawert (ogra) wrote :

setting that variable doesnt change a thing, even setting it to "dark" or "original" as suggested on IRC doesnt change from the violet theme.

according to colin oem-config-debconf uses debconf instead of cdebconf which may have an influence here.

Revision history for this message
Colin Watson (cjwatson) wrote :

This clearly has nothing to do with debian-installer - oem-config is part of the ubiquity source package, and the part at issue here doesn't run in the context of d-i. Reverting the reassignment.

affects: debian-installer (Ubuntu Natty) → ubiquity (Ubuntu Natty)
Changed in ubiquity (Ubuntu Natty):
milestone: ubuntu-11.04 → natty-updates
Changed in ubiquity (Ubuntu Oneiric):
milestone: ubuntu-11.04 → none
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ubiquity (Ubuntu Oneiric) because there has been no activity for 60 days.]

Changed in ubiquity (Ubuntu Oneiric):
status: Incomplete → Expired
Oliver Grawert (ogra)
Changed in ubiquity (Ubuntu Oneiric):
milestone: none → ubuntu-11.10
status: Expired → New
Oliver Grawert (ogra)
Changed in ubiquity (Ubuntu Natty):
status: Incomplete → Won't Fix
milestone: natty-updates → none
Changed in ubiquity (Ubuntu Oneiric):
status: New → Won't Fix
milestone: ubuntu-11.10 → none
Changed in ubiquity (Ubuntu Precise):
milestone: ubuntu-11.10 → none
Revision history for this message
Tobin Davis (gruemaster) wrote :

This may actually be a bug in debconf-apt-progress. Will test to see.

Tobin Davis (gruemaster)
Changed in ubiquity (Ubuntu Precise):
status: New → Confirmed
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/747229

tags: added: precise
Revision history for this message
Tobin Davis (gruemaster) wrote :

Thought I had posted my test notes, guess not.

Here is what I have done so far:
Used a daily image from http://cdimage.ubuntu.com/ubuntu-server/daily-preinstalled. Ran through entire config process. Observed color change at oem-config-remove step.
Logged in and installed the necessary oem-config packages that get removed after configuring.
Manually ran oem-config-remove (shell wrapper step), observed correct colors during oem-config-remove process.

I then started looking through the code, but got lost very quickly (shell wrapper for python wrapper for other wrappers....).

The color change is somewhere between oem-config-debconf and oem-config-remove steps. Not sure where (someone that knows the code could probably find it easily).

Revision history for this message
Michael Casadevall (mcasadevall) wrote :

Still valid, encounter on today's daily image. Its extremely disconcerting though to say the least, so it would be nice if it could be fixed for precise release.

This should be release noted however, so its expected. Adding release notes.

Changed in ubuntu-release-notes:
status: New → Confirmed
Pete Graner (pgraner)
Changed in ubuntu-release-notes:
status: Confirmed → Invalid
Revision history for this message
Marcus Tomlinson (marcustomlinson) wrote :

This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue on a maintained version of Ubuntu please let us know.

Changed in ubiquity (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Marcus Tomlinson (marcustomlinson) wrote :

This issue has sat incomplete for more than 60 days now. I'm going to close it as invalid. Please feel free re-open if this is still an issue for you. Thank you.

Changed in ubiquity (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Steve Langasek (vorlon) wrote :

The Precise Pangolin has reached end of life, so this bug will not be fixed for that release

Changed in ubiquity (Ubuntu Precise):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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