ubiquity shows for a second goes to tty then starts live session.

Bug #1527353 reported by Lyn Perrine on 2015-12-17
28
This bug affects 7 people
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Critical
Colin Watson

Bug Description

To reproduce boot a ubuntu mate 1217 desktop amd 64 image in a kvm viirtual machine and select install ubuntu-mate from the menu. Ubutunu mate will show ubiquity then a tty login then start the live session.

I expected ubiquity to start and isntall when selecting install ubuntu-mate from the menu. Instead it went into a live session although I could run ubiquity manually. in a terminal.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.38
ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
Uname: Linux 4.3.0-2-generic x86_64
ApportVersion: 2.19.3-0ubuntu2
Architecture: amd64
CasperVersion: 1.366
CurrentDesktop: MATE
Date: Thu Dec 17 17:56:18 2015
InstallCmdLine: file=/cdrom/preseed/ubuntu-mate.seed boot=casper only-ubiquity initrd=/casper/initrd.lz quiet splash ---
LiveMediaBuild: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151217)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

Related branches

Lyn Perrine (walterorlin) wrote :
Lyn Perrine (walterorlin) wrote :

Starting ubuiquirty after the live session seemed to work and I got an installable system. 1527353

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

tags: added: iso-testing
Wen Jie (seowwjpg) wrote :

Got the same problem with Lubuntu amd64 build 20151219

tags: added: lubuntu
Changed in ubiquity (Ubuntu):
status: New → Confirmed
Changed in ubiquity (Ubuntu):
importance: Undecided → Medium
John Przybytek (jprzybytek) wrote :

Got same problem on UbuntuGnome 20151228

Dimitri John Ledkov (xnox) wrote :

ubiquity-dm: Traceback (most recent call last):
  File "/usr/bin/ubiquity-dm", line 783, in main
    ret = run(vt, display, username)
  File "/usr/bin/ubiquity-dm", line 758, in run
    ret = dm.run(*sys.argv[4:])
  File "/usr/bin/ubiquity-dm", line 647, in run
    db = DebconfCommunicator('ubiquity', cloexec=True)
  File "/usr/lib/ubiquity/ubiquity/debconfcommunicator.py", line 37, in __init__
    write=self.dccomm.stdin)
  File "/usr/lib/python3/dist-packages/debconf.py", line 50, in __init__
    self.setUp(title)
  File "/usr/lib/python3/dist-packages/debconf.py", line 53, in setUp
    self.version = self.version(2)
  File "/usr/lib/python3/dist-packages/debconf.py", line 62, in <lambda>
    lambda *args, **kw: self.command(command, *args, **kw))
  File "/usr/lib/python3/dist-packages/debconf.py", line 83, in command
    status = int(status)
ValueError: invalid literal for int() with base 10: ''

Colin Watson (cjwatson) wrote :

I think this is a regression from the big plymouth merge a while back; the timing of the failures on https://jenkins.qa.ubuntu.com/view/Releases/view/Xenial/job/xenial-desktop-amd64-smoke-default/ is exactly right for that. I haven't worked it all out, but I'm seeing the X server that's started from ubiquity-dm get an I/O error when trying to change VT.

Colin Watson (cjwatson) on 2015-12-31
Changed in ubiquity (Ubuntu):
assignee: nobody → Colin Watson (cjwatson)
importance: Medium → Critical
status: Confirmed → Fix Committed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ubiquity - 2.21.41

---------------
ubiquity (2.21.41) xenial; urgency=medium

  * Pass "-term linux" when running setterm from start-ubiquity-dm, as
    without TERM set it otherwise refuses to do anything.
  * Set "Before=plymouth-quit.service plymouth-quit-wait.service" in
    ubiquity.service, so that plymouth isn't told to quit while we're busy
    starting up on its VT (LP: #1527353).
  * Automatic update of included source packages: apt-setup 1:0.104ubuntu2,
    clock-setup 0.126ubuntu1, debian-installer-utils 1.113ubuntu1, tzsetup
    1:0.81ubuntu1.

 -- Colin Watson <email address hidden> Thu, 31 Dec 2015 00:07:05 +0000

Changed in ubiquity (Ubuntu):
status: Fix Committed → Fix Released
Alex Dueppen (adueppen) wrote :

Just tested the 1231.1 i386 lubuntu desktop image and this issue has been fixed as far as I can tell.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers