I can switch to console/ttys from ubiquity on the latest daily xenial and
bionic images.
However we still need to add systemd.debug-shell manually to the kernel
parameter to enable the debug shell in tty9.
** Changed in: oem-priority
Status: In Progress => Fix Released
--
You received
** Changed in: oem-priority
Status: Triaged => Fix Released
** Changed in: oem-priority
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1567194
Title:
$4, can you update the status if oem-priority per your test result when
convenient ?
** Changed in: oem-priority
Assignee: (unassigned) => Shih-Yuan Lee (fourdollars)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
** Changed in: ubuntu-cdimage
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1567194
Title:
Unable to switch to console/ttys from ubiquity
To manage notifications about
Fixed in ubiquity 18.04.5.
** Changed in: ubiquity (Ubuntu)
Status: Triaged => Fix Released
** Changed in: plymouth (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
** Changed in: oem-priority
Importance: High => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1567194
Title:
Unable to switch to console/ttys from ubiquity
To manage notifications about this
Is there any estimate of a fix for this? We have a couple of OEMs
affected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1567194
Title:
Unable to switch to console/ttys from ubiquity
To manage not
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: plymouth (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1567194
Title:
U
1) change initramfs plymouth init-premount hoook to parse /proc/cmdline
and pass --tty=/dev/tty$N where $N is vt.handoff=$N
2) change ubiquity to require getty.target, and be after getty.target,
and after getty@tty7.service, and conflict with getty@tty7.service
3) test images with above
4) chang
Actually, ubiquity used to be on vt7, why is it ending up on vt1? start-
ubiquity-dm should be starting on tty7...
With: kernel cmdline vt.handoff=7, After=getty@tty7.service,
Conflicts=getty@tty7.service, Requires=getty.target, eding ubiquity-dm
active_vt() function to just return int(7) => boot
** Branch linked: lp:~xnox/ubiquity/lp1632151
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1567194
Title:
Unable to switch to console/ttys from ubiquity
To manage notifications about this bug go t
Unlike installed desktops, we do not appear to be booting with
vt.handoff=7 this is what should be putting plymouth on vt7, not
switching and starting ubiquity there.
Similar to lightdm.service, I find that: Requires=getty.target;
After=getty@tty1.service; Conflicts=getty@tty1.service => results i
Pasting the important bits from some private email conversation here,
for posterity.
My reply:
8<
At the moment we told the boot sequence these two:
* ubiquity runs before stopping plymouth since
http://bazaar.launchpad.net/~ubuntu-installer/ubiquity/trunk/revision/6
** Changed in: oem-priority
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1567194
Title:
Unable to switch to console/ttys from ubiquity
To manage notification
> "After=" does not do anything about adding new dependencies
sorry, that was unclear. I meant to say "anything about starting new
services". Also, we don't actually need to do that, getty and the others
are already waiting to start, we just currently force ubiquity to run
before those.
--
You r
For the record: The "Before=plymouth-quit-wait.service" was introduced
in http://bazaar.launchpad.net/~ubuntu-
installer/ubiquity/trunk/revision/6363 to fix bug 1527353.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
This isn't actually easy to fix with our current dependency layout --
ubiquity has "Before=plymouth-quit-wait.service" and getty@.service has
"After=plymouth-quit-wait.service", i. e. right now we sort ubiquity ←
plymouth ← getty. Thus we can't possibly start getty before/with
ubiquity, we need to
This change (http://bazaar.launchpad.net/~ubuntu-
installer/ubiquity/trunk/revision/6411.2.2) does not actually help to
fix this bug, as "After=" does not do anything about adding new
dependencies, it controls ordering only. Thus there are still no VTs
during maybe-ubiquity, thus reopening this bug
** Changed in: oem-priority
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1567194
Title:
Unable to switch to console/ttys from ubiquity
To manage notifications ab
This bug was fixed in the package ubiquity - 2.21.56
---
ubiquity (2.21.56) xenial; urgency=medium
* Update translations from Launchpad. (LP: #1569232)
* debian/ubiquity.ubiquity.service: Start console ttys for debugging during
an installation. (LP: #1567194)
* data/oem-conf
** Branch linked: lp:ubiquity
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1567194
Title:
Unable to switch to console/ttys from ubiquity
To manage notifications about this bug go to:
https://bugs.
This is only broken in the only-ubiquity case (ie. when you pick
"Install" rather than "Try") and was already broken in wily release.
That said, it's on my list of things to fix for this cycle, it's just
kind of cosmetic so not the top priority. I'll see what I can do, I
wasn't that far from makin
** Also affects: oem-priority
Importance: Undecided
Status: New
** Changed in: oem-priority
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1567194
Title:
U
23 matches
Mail list logo
