[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.
Mordi,
Please ensure you have the latest updates installed:
sudo apt update
sudo apt full-upgrade
then reboot and tell us if you still experience the problem.
** Changed in: plymouth (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a
it sounds like this bug is a dup of bug 1872159? I'm assuming so, and
marking this invalid for systemd.
** Changed in: systemd (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Now I've written a fix for bug 1872159 I can confirm that multiple
monitors are not a requirement. You could hit it even with a single
display, but I haven't seen that case happen myself.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Maybe related to bug 1872159, which supposedly happens when extra
monitors are connected. Although I doubt that's the only requirement to
make the bug happen.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags removed: rls-ff-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871641
Title:
Ubuntu never finishes booting: A start job is running for Hold until
boot process finishes up (3min
Is there a reliable way I can reproduce the problem? (I don't face it on my
laptops.)
Is this happening on any Ubuntu-certified model? This could let our
certification team to investigate the issue.
How can the systemd help? killing plymouth earlier?
** Changed in: systemd (Ubuntu)
** Tags added: id-5f10737aea5c871f9fb256f6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871641
Title:
Ubuntu never finishes booting: A start job is running for Hold until
boot process finishes
I think we need help from a systemd expert.
** Also affects: systemd (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/1871641
Title:
Ubuntu never
Could the desktop team please take a look at this bug report as they did
a fair bit of work on flicker free boot?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871641
Title:
Ubuntu never finishes
For those that would land here because of lightdm:
https://bugs.launchpad.net/lightdm/+bug/1882970
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871641
Title:
Ubuntu never finishes booting: A
Hi,
I encountered the same problem today.
Removing splash did not help.
Disabling plymouth worked, but I face a console login screen. It was
also impossible to start lightdm manually. Apparently in my case lightdm
is the problem...
--
You received this bug notification because you are a
** Tags added: rls-ff-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871641
Title:
Ubuntu never finishes booting: A start job is running for Hold until
boot process finishes up (3min 7s
UPDATE: I "fixed" my issue by disabling plymouth in kernel params. I
changed my grub file with the following:
GRUB_CMDLINE_LINUX_DEFAULT="noplymouth video=SVIDEO-1:d"
After this change my computer booted normally (w/o plymouth of course)
but now both monitors work and I can change my display's
I have a related issue. I did a clean install (previously had Linux Mint
19.04) and I'm not able to reach login screen unless I add `nomodeset`
to the kernet parameters. However, after adding `nomodeset` it appears
that my graphics driver never loads and I cannot change display
brightness nor use
I'm not sure which package is to blame here but to avoid the bug getting
lost I will assign it to Plymouth for now.
** Package changed: ubuntu => plymouth (Ubuntu)
** Summary changed:
- Ubuntu never finishes booting: A start job is running for Hold until boot
process finishes up (3min 7s / no
I think I have the same problem.
I did a fresh install of 20.04 on a Lenovo Carbon X1 6th gen. Previously
it was working fine under 18.04.
The 20.04 install ran perfectly, and at first the system booted up and
ran normally.
Shortly afterward I got a notice about a Thunderbolt firmware update
I'm also affected, using a Lenovo W540 laptop, that was working with
19.10,
Interestingly it worked when I upgraded 19.10 to 20.04, but I then
decided to do a clean install of 20.04 to get rid of some old graphics
experiments with KVM, in order to get both graphics cards usable in
ubuntu (this
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: 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/1871641
Title:
Ubuntu
Identical bug.
Clean install on an elderly Lenovo Thinkpad that had worked perfectly on every
version of Ubuntu since 12.10.
Clean install. The restart from installation process goes through correctly.
But if the computer is powered down, it gets stuck on the splash screen. No
time out - I
** Changed in: ubuntu
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871641
Title:
Ubuntu never finishes booting: A start job is running for Hold until
boot
This time I waited for two hours. I can get around this by enabling
automatic login.
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+bug/1871641/+attachment/5354681/+files/prevboot.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Thanks, but weirdly that log contains less than 2 minutes' worth.
Nothing is timing out there!?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871641
Title:
Ubuntu never finishes booting: A start
Journal of the failed boot is attached.
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+bug/1871641/+attachment/5353806/+files/prevboot.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Mordi,
> Note that the attachment shows the log of a succesful boot, not one
that failed.
In that case please:
1. Reproduce the problem again.
2. Reboot.
3. Run this command to collect a log of the previous (failed) boot:
journalctl -b-1 > prevboot.txt
4. Attach the resulting
Editing out splash from grub removes the splash screen and the problem.
Interestingly, I can suspend the computer from the keyboard, change
screen brightness but can't change to console.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
What happens if you edit
/etc/default/grub
to remove splash as a setting (that is, boot without plymouth).
I was having similar problems to you, also with log message saying job was on
hold. I did not wait beyond 3 minutes. In my case, this only happens if an
external monitor is connected at
Waiting does not solve the problem. Note that the attachment shows the
log of a succesful boot, not one that failed.
** Attachment added: "journal.txt"
https://bugs.launchpad.net/ubuntu/+bug/1871641/+attachment/5350357/+files/journal.txt
--
You received this bug notification because you are
What if you wait 5-10 minutes? Does it eventually time out and boot
then?
Also, please run this command:
journalctl -b0 > journal.txt
and then attach the resulting file here.
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a
29 matches
Mail list logo
