Lubuntu live image boots to TTY
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lxdm (Ubuntu) |
Invalid
|
High
|
Unassigned | ||
Oneiric |
Won't Fix
|
High
|
Unassigned |
Bug Description
I'm testing the Oneiric Lubuntu 20110920-i386 live image and I notice that booting to a blank hard drive on my old VIA hardware (I'll attach a list later if not collected by apport) results in a TTY prompt which may leave some users confused as how to proceed.
I've repeated this twice and in both instances typing "sudo service lxdm start" (without the quotes) results in a DE, that is no need to login as "ubuntu", leave password blank, etc.
This occurred so far only when booting to a blank 80GB drive (errm - maybe had one existing partition) to perform an "entire disc" installation test. I'm now going to use the same drive to try an auto-resize install and I'll report back accordingly.
I realize this may actually be an lxdm bug but I thought filing against casper would collect the best possible info, hope I was right.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: casper 1.284
ProcVersionSign
Uname: Linux 3.0.0-11-generic i686
ApportVersion: 1.23-0ubuntu1
Architecture: i386
CasperVersion: 1.284
Date: Tue Sep 20 11:13:46 2011
LiveMediaBuild: Lubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110920)
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: casper
UpgradeStatus: No upgrade log present (probably fresh install)
tags: | added: iso-testing |
tags: | added: rls-mgr-o-tracking |
Changed in casper (Ubuntu Oneiric): | |
importance: | Undecided → High |
Changed in casper (Ubuntu Oneiric): | |
status: | Incomplete → Confirmed |
tags: | added: lubuntu |
tags: |
added: rls-p-tracking removed: rls-mgr-o-tracking |
tags: | removed: rls-p-tracking |
This is the hardware involved:
VIA PC2500 Mainboard
VIA Esther C7 CPU 1500MHz
System Memory 2GB DIMM
VT8233/A/8235/8237 AC97 Audio Controller
CN700/P4M800 Pro/P4M800 CE/VN800 [S3 UniChrome Pro] Graphics
And a single 80GB hard drive which may have either been a blank drive or had one single partition - according to the installer one partition was going to be erased but it's a testing drive so I'm clueless about what may have been there, most likely some old data transfer because a previous installation would have had more than one partition.
Now to repeat some testing.