Ubiquity screen problem during install.

Bug #1057120 reported by warren on 2012-09-26
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
X.Org X server
Won't Fix
High
xorg (Ubuntu)
High
Unassigned

Bug Description

1) Lubuntu 12.10 i386 Beta2 26 September 2012
2) Ubiquity 2.12.5
3) I did not expect during install for the screen to as is the photo I have attached to this bug report.
4) The Ubiquity screen bug is displayed in the photo image I have attached to this bug report. I have encountered this problem during September 25th and 26th Beta2 install testcases.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4
Uname: Linux 3.5.0-15-generic i686
ApportVersion: 2.5.2-0ubuntu4
Architecture: i386
Date: Wed Sep 26 14:29:55 2012
InstallCmdLine: noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/lubuntu.seed boot=casper only-ubiquity initrd=/casper/initrd.lz quiet splash --
InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Beta i386 (20120926)
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

warren (wkclemmons) wrote :
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/1057120

tags: added: iso-testing
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubiquity (Ubuntu):
status: New → Confirmed
Brian Murray (brian-murray) wrote :

Not a bug with the installer, ubiquity, rather this looks like an issue with X.

affects: ubiquity (Ubuntu) → xorg (Ubuntu)
Changed in xorg (Ubuntu):
importance: Undecided → High
Timo Aaltonen (tjaalton) wrote :

So what hardware do you have? This bug has zero useful logs or other information. If you've installed the system, run 'sudo apt-get install xdiagnose ; apport-collect 1057120'.

Changed in xorg (Ubuntu):
status: Confirmed → Incomplete
Timo Aaltonen (tjaalton) wrote :

..and then I realized the syslog has dmesg messages in it.

So, there probably should be some app drawing the background but it's stuck. Do you get the same with the Ubuntu installer?

No problem for Xubuntu and Ubuntu installer only Lubuntu.

Erick Brunzell (lbsolost) wrote :

I just installed Lubuntu Precise final in order to perform Lubuntu i386 Quantal upgrade testing and even the Lubuntu i386 Precise final will display this behavior. If you don't "drag" the installer windows around you can see still see "window-over-window" behavior.

Since a picture is worth a thousand words I'll repeat with an Lubuntu Precise image and show you very soon ;^)

I somehow doubt this is a true Xorg bug ............. maybe more related to the gtk2 -> gtk3 switch ????

I really don't think it's a serious issue, just cosmetic.

Changed in xorg (Ubuntu):
status: Incomplete → Confirmed
Erick Brunzell (lbsolost) wrote :

Just checking this again in Lubuntu Precise final and all seems well if I begin from the live desktop, but if I begin by selecting Install rather than Try I get this behavior.

I did take some pics but I'm now waiting for a camera battery to recharge. And I will of course have to double check the behavior in Lubuntu Quantal.

I'd seen this some time ago but since it was only cosmetic I didn't think it was worth mentioning :^(

Erick Brunzell (lbsolost) wrote :

Here's the shots from Lubuntu Precise. I'll follow up closer with Quantal ASAP.

Erick Brunzell (lbsolost) wrote :

OK, I've been testing the Lubuntu Quantal 20121014 i386 image intensively on two sets of hardware, but I have not tested at all in a VM.

On my old VIA C7 w/P4M800 graphics I can NOT reproduce this regardless of whether I choose Try or Install from the boot menu.

But on my Intel Atom 230 w/Intel 82945G/GZ Integrated Graphics this behavior is easy to reproduce only if I choose Install from the boot menu. If I begin from the live desktop I can't reproduce the behavior on this hardware.

It would therefore be interesting to know exactly what graphics chips are effected by this bug.

Regardless the installation does complete successfully if you simply disregard the "window-over-window" behavior.

From a testing perspective try this to see if it can be reproduced:

(1) Boot the live CD, select the preferred language, and then select Install

(2) Select your preferences on the first two installer windows. (I've only tested in English and with DL updates/do install 3rd party selected)

(3) On the third window where you select the type of installation see if you can "drag" that window and recreate this screen "blur" behavior.

Note: If choosing advanced partitioning the "window-over-window" behavior will be quite evident even w/o dragging a window.

Erick Brunzell (lbsolost) wrote :

I just happened to think that my old P4M800 will not even begin to render 3D graphics so I wondered if it's possible to use a boot parameter edit to make my Intel i945 ignore 3D capability?

Maybe nomodeset?

Or maybe just a stupid idea ;^(

--Originally by warren at the Ubuntu Launchpad Bug Tracker--
--https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1057120--

1) Lubuntu 12.10 i386 Beta2 26 September 2012
2) Ubiquity 2.12.5
3) I did not expect during install for the screen to as is the photo I have attached to this bug report.
4) The Ubiquity screen bug is displayed in the photo image I have attached to this bug report. I have encountered this problem during September 25th and 26th Beta2 install testcases.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4
Uname: Linux 3.5.0-15-generic i686
ApportVersion: 2.5.2-0ubuntu4
Architecture: i386
Date: Wed Sep 26 14:29:55 2012
InstallCmdLine: noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/lubuntu.seed boot=casper only-ubiquity initrd=/casper/initrd.lz quiet splash --
InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Beta i386 (20120926)
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

--Other files and logs are available on https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1057120--

Changed in xorg-server:
importance: Unknown → High
status: Unknown → Confirmed
C de-Avillez (hggdh2) wrote :

Marking triaged, per request in #ubuntu-bugs

Changed in xorg (Ubuntu):
status: Confirmed → Triaged

warren, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p xorg <replace-with-bug-number>

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

Changed in xorg (Ubuntu):
status: Triaged → Incomplete

Do what you feel is necessary.

On Fri, Jan 3, 2014 at 5:52 PM, Christopher M. Penalver <
<email address hidden>> wrote:

> warren, this bug was reported a while ago and there hasn't been any
> activity in it recently. We were wondering if this is still an issue? If
> so, could you please test for this with the latest development release
> of Ubuntu? ISO images are available from http://cdimage.ubuntu.com
> /daily-live/current/ .
>
> If it remains an issue, could you please run the following command in
> the development release from a Terminal
> (Applications->Accessories->Terminal), as it will automatically gather
> and attach updated debug information to this report:
>
> apport-collect -p xorg <replace-with-bug-number>
>
> Thank you for your understanding.
>
> Helpful bug reporting tips:
> https://wiki.ubuntu.com/ReportingBugs
>
> ** Changed in: xorg (Ubuntu)
> Status: Triaged => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1057120
>
> Title:
> Ubiquity screen problem during install.
>
> Status in X.Org X server:
> Confirmed
> Status in “xorg” package in Ubuntu:
> Incomplete
>
> Bug description:
> 1) Lubuntu 12.10 i386 Beta2 26 September 2012
> 2) Ubiquity 2.12.5
> 3) I did not expect during install for the screen to as is the photo I
> have attached to this bug report.
> 4) The Ubiquity screen bug is displayed in the photo image I have
> attached to this bug report. I have encountered this problem during
> September 25th and 26th Beta2 install testcases.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 12.10
> Package: ubiquity (not installed)
> ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4
> Uname: Linux 3.5.0-15-generic i686
> ApportVersion: 2.5.2-0ubuntu4
> Architecture: i386
> Date: Wed Sep 26 14:29:55 2012
> InstallCmdLine: noprompt cdrom-detect/try-usb=true
> file=/cdrom/preseed/lubuntu.seed boot=casper only-ubiquity
> initrd=/casper/initrd.lz quiet splash --
> InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Beta i386 (20120926)
> ProcEnviron:
> LANGUAGE=en_US:en
> PATH=(custom, no user)
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> SourcePackage: ubiquity
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/xorg-server/+bug/1057120/+subscriptions
>

Erick Brunzell (lbsolost) wrote :

To the best of my knowledge this effected only Lubuntu Precise and Quantal. If so it really could be marked "won't fix" since neither of those images will be respun. Or we could wait and see if it pops up again in Trusty????

Changed in xorg-server:
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

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