[Expired for plymouth (Ubuntu) because there has been no activity for 60
days.]
** Changed in: plymouth (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900
To be able to run the command I had to select the option to try Ubuntu and that
restarts the session.
That was my mistake
Anyway, it's a matter of waiting until tomorrow. If no one else complains it's
a problem with my hardware
--
You received this bug notification because you are a member of U
Tanks Steve
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900715
Title:
The initial screen of Plymouth takes 20 minutes to appear (Groovy
live)
To manage notifications about this bug go to:
http
(and systemd, to be clear, doesn't start until after plymouth, in a live
CD)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900715
Title:
The initial screen of Plymouth takes 20 minutes to appear (G
So this dmesg is from a 20-minute boot? Because it shows systemd
starting at 108 seconds after kernel init.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900715
Title:
The initial screen of Plymou
By creating the installer with UNetbootin the problem does not occur.
UNetbootin creates its own boot loader.
I've attached the dmesg output with UNetbootin so you can compare.
Thank you.
** Attachment added: "dmesg_unetbootin"
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1900715/+a
** Attachment added: "dmesg"
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1900715/+attachment/5425215/+files/dmesg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900715
Title:
The ini
> I know of no reason that we should be mounting ext4 filesystems from the
> host system prior to actually starting the installer.
Digging into the casper code, this is because from the initramfs we
don't automatically know what device contains the isofs that needs to be
mounted in order to get t
The journal you've attached unfortunately doesn't show timing
information for anything that happened before systemd started, so it's
impossible to say what is causing a 20-minute delay (the timestamps in
the journal only cover a 3-minute period). Would it be possible for you
to also attach the out
After the initial screen of the grub you see a black screen with a white
dash blinking in the upper left corner for about twenty minutes.
Then text and then the screen with the Ubuntu logo and the integrity check
I am trying to make a capture of the text.
--
You received this bug notification b
** Attachment added: "journal.txt"
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1900715/+attachment/5425154/+files/journal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900715
Titl
Do you really mean plymouth or some other screen? If unsure then please
attach photos of what you see during and after the 20 minutes.
Also, can you please reproduce the problem again and then start a live
session and run:
journalctl -b0 > journal.txt
and attach the resulting text file here?
12 matches
Mail list logo
