Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: grub2-signed (Ubuntu Artful)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: grub2 (Ubuntu Artful)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
This bug was fixed in the package grub2-signed - 1.89
---
grub2-signed (1.89) bionic; urgency=medium
* Rebuild against grub2 2.02-2ubuntu3. (LP: #1675453)
-- Łukasz 'sil2100' Zemczak Mon, 22 Jan
2018 09:40:19 +0100
** Changed in: grub2-signed (Ubuntu)
Status: New => Fix
This bug was fixed in the package grub2 - 2.02-2ubuntu4
---
grub2 (2.02-2ubuntu4) bionic; urgency=medium
* debian/patches/vt_handoff.patch: modify the existing patch to set
vt.handoff=1 instead of vt.handoff=7 as we now start display managers on
vt1 anyway. This also fixes i
I agree that's something worth considering, but I'd say it's a separate
story. The vt.handoff patches are not only needed for the d-i netboot
install of server case, but in overall for the splash boot experience
being smooth. Without vt.handoff all desktops will regress in how the
splash screen loo
** Also affects: grub2-signed (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1675453
Title:
During d-i install of ubuntu-server from mini.iso I ge
On Thu, Jan 18, 2018 at 04:56:33PM -, Łukasz Zemczak wrote:
> Ok, so it seems a few of my previous tests were a bit flawed. It looks
> like vt.handoff=1 does the trick completely for this particular bug. So
> once we switch grub2 to vt.handoff=1 this bug here will be fixed.
> Another thing that
** Changed in: plymouth (Ubuntu)
Status: In Progress => Invalid
** Changed in: plymouth (Ubuntu Artful)
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/16754
Ok, so it seems a few of my previous tests were a bit flawed. It looks
like vt.handoff=1 does the trick completely for this particular bug. So
once we switch grub2 to vt.handoff=1 this bug here will be fixed.
Another thing that needs to be still considered is somehow tweaking
netboot installs to ha
I'm learning all those bits slowly piece by piece here...
@Steve: it actually seems that "vt.handoff=1" is not equal to no-
vt.handoff. I would have to look into the vt.handoff kernel patches, but
without vt.handoff tty1 is indeed used by default for handoff and
everything, but the difference is t
So plymouth is by default using tty1 already, but there seem to be some
other problems here. Looks like with the 'quiet splash' option, when
plymouth is running there still seems to be some output printed out to
the screen on top of the splash-screen (from the looks of it it's
systemd output + a fe
What I'll do is remove the vt.handoff patch from grub2 and switch
plymouth to use vt1 as well (if xnox doesn't beat me to the latter).
** Also affects: grub2 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: grub2 (Ubuntu)
Assignee: (unassigned) => Łukasz Zemczak (sil2100)
On Fri, Nov 17, 2017 at 09:20:09AM -, Łukasz Zemczak wrote:
> The reason for this happening is that apparently this ubuntu-server
> image is booting with vt.handoff=7 while in systemd's logind we're only
> using the default number of configured tty's (i.e. 6). So plymouth is
> running, doing it
I see that by default our ubuntu-server images boot without "quiet
splash", maybe this is what we'd prefer in case of the mini.iso ubuntu-
server image as well?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
The reason for this happening is that apparently this ubuntu-server
image is booting with vt.handoff=7 while in systemd's logind we're only
using the default number of configured tty's (i.e. 6). So plymouth is
running, doing it's thing and then switches to tty7 which is not
enabled. This can be con
** Changed in: plymouth (Ubuntu)
Status: Confirmed => In Progress
** Changed in: plymouth (Ubuntu Artful)
Status: Confirmed => 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/1
** Changed in: plymouth (Ubuntu)
Assignee: Adam Conrad (adconrad) => Łukasz Zemczak (sil2100)
** Changed in: plymouth (Ubuntu Artful)
Assignee: Adam Conrad (adconrad) => Łukasz Zemczak (sil2100)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
** Tags added: id-597a832cfc4199380b98faa4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1675453
Title:
During d-i install of ubuntu-server from mini.iso I get no login
prompt
To manage notificat
** Changed in: plymouth (Ubuntu)
Assignee: (unassigned) => Adam Conrad (adconrad)
** Also affects: plymouth (Ubuntu Artful)
Importance: High
Assignee: Adam Conrad (adconrad)
Status: Confirmed
** Tags removed: rls-aa-incoming
--
You received this bug notification because you
** Tags removed: rls-z-incoming
** Tags added: rls-aa-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1675453
Title:
During d-i install of ubuntu-server from mini.iso I get no login
prompt
In a fresh install, it hangs for five minutes, while it waits for the
network interfaces to go up. After login prompt, if you try to restart
networking, it complains about policykit-1 not found. Does this happen
to you? If so, it is related to bug #1682201
--
You received this bug notification be
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/1675453
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
** Tags added: rls-z-incoming
** Tags added: zesty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1675453
Title:
During d-i install of ubuntu-server from mini.iso I get no login
prompt
To manage
** Changed in: plymouth (Ubuntu)
Status: New => Confirmed
** Changed in: plymouth (Ubuntu)
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/1675453
Title:
Durin
Look like mini.iso/netboot will use plymouth in text mode where the
server.iso does not. So I think that plymouth is not being taken down
and therefore utilising tty1 which is why we see no login adding
plymouth to the bug.
** Package changed: debian-installer (Ubuntu) => plymouth (Ubuntu)
--
Y
25 matches
Mail list logo
