[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/1871
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 me
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.
https://bugs
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 Ubuntu.
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.
https://bugs.launchpad.net/b
** 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 7s
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)
Sta
** 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 u
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 f
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 b
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 start
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 member
** 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 bri
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 a
15 matches
Mail list logo
