when booting fresh install on i386 system, screen output shows evidence of buffer overwrites

[Kate Stewart]

To reproduce:
   On Aspire intel Atom system, with Windows XP:
   - download signed WUBI, invoke in windows environment
   - install 12.10 release candidate image
   - reboot
   - select boot in Ubuntu
   - see: image for screen progress - looks like something is overwriting some buffers it shouldn't.
   - system did eventually boot

lsb_release -rd
Description: Ubuntu 12.10
Release 12.10

apt-cache policy grub2
grub:
   Installed: (none)
   Candidate: 2.00-7ubuntu11
   Version table:
       2.00-7ubuntu11 0
           500 http://archive.ubuntu.com/ubuntu/ quantal/universe i386 packages
---
ApportVersion: 2.6.1-0ubuntu3
Architecture: i386
CurrentDmesg:

DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
DistroRelease: Ubuntu 12.10
MachineType: Acer Aspire one
Package: plymouth 0.8.4-0ubuntu3
PackageArchitecture: i386
ProcCmdLine: BOOT_IMAGE=/vmlinuz root=UUID=18E034E2E034C7B0 loop=/hostname/disks/root.disk preseed/file=/hostname/install/preseed.cfg wubi-diskimage ro quiet splash
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=UUID=18E034E2E034C7B0 loop=/hostname/disks/root.disk preseed/file=/hostname/install/preseed.cfg wubi-diskimage ro quiet splash
ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
Tags: quantal running-unity
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Uname: Linux 3.5.0-17-generic i686
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 07/09/2009
dmi.bios.vendor: Acer
dmi.bios.version: V1.08
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Aspire one
dmi.board.vendor: Acer
dmi.board.version: V1.08
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.08
dmi.modalias: dmi:bvnAcer:bvrV1.08:bd07/09/2009:svnAcer:pnAspireone:pvrV1.08:rvnAcer:rnAspireone:rvrV1.08:cvnAcer:ct10:cvrV1.08:
dmi.product.name: Aspire one
dmi.product.version: V1.08
dmi.sys.vendor: Acer

[Steve Langasek (vorlon)]

Please run 'apport-collect -p plymouth 1067134' from the affected system.

[Kate Stewart (kate.stewart)]

One of the concern points on the top of the sequence was:
 pwconv: failed to change the mode of /etc/passwd - to 0600

which from discussion with slangasek:
<slangasek> the guilty party is lupin -> user-setup -> shadowconfig (passwd)
<slangasek> which is wubi-specific
<slangasek> so a bug report against wubi + user-setup is probably the place to start

However this is not as significant compared to the other issues, but should be cleaned up at some point.

<slangasek> the root issue is the lack of graphical boot splash
<slangasek> for which we need 'apport-collect -p plymouth 1067134' from the machine

apport-collect not cooperating right now. Will post as soon as able to.

[Kate Stewart (kate.stewart)]

apport information

[Kate Stewart (kate.stewart)]

apport information

[Kate Stewart (kate.stewart)]

apport information

[Kate Stewart (kate.stewart)]

apport information

[Kate Stewart (kate.stewart)]

apport information

[Kate Stewart (kate.stewart)]

apport information

[Kate Stewart (kate.stewart)]

apport information

[Kate Stewart (kate.stewart)]

apport information

[Kate Stewart (kate.stewart)]

apport information

[Kate Stewart (kate.stewart)]

apport information

[Kate Stewart (kate.stewart)]

apport information

[Ubuntu QA Website (ubuntuqa)]

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/1067134

[Steve Langasek (vorlon)]

Ok, since this machine has the inteldrmfb video driver, plymouth graphical splash should be working. I expect this is a hardware-specific video problem. Can you boot with the option 'plymouth.debug=file:/var/log/plymouth-debug.log' added to the kernel commandline, and attach the resulting log file?

[Steve Langasek (vorlon)]

At this point I don't believe this problem is wubi-related; marking invalid for wubi.

[Kate Stewart (kate.stewart)]

Hmm... I see to be having troubles making the bug upload the log from the machine. Anyhow, collected the log file.

The reboot happened smoothly though, none of the same symptoms as was seen on the initial boot. It may require booting from a WUBI system to see this in the first place/reproduce.

[Steve Langasek (vorlon)]

The attached plymouth-debug log doesn't seem to show any problems with the boot splash, which would be consistent with your comment that you didn't see the same symptoms from the initial boot. We probably need the plymouth debug log from a boot when the problem *is* reproducible in order to debug this.