-
-
Notifications
You must be signed in to change notification settings - Fork 132
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[odin-beta] Boot "error: Unexpectedly disconnected from boot status daemon" #482
Comments
Does this also occur on Ubuntu? |
My Ubuntu laptop is also on the same kernel (5.8.0-50). I do not see this issue on my laptop. |
It happened to me after a bit much trying of plymouth using I changed a configuration file of the default plymouth and now it's broken. Reverted changes and still happening, reboot does nothing. Plymouth start service is suprisingly running |
There is no pid-file for whatever reason Restarting plymouth broke it:
|
A person (scamming person) had this on ubuntu |
This is the problem. Plymouth got quitted (forcefully?) but did not clean up. Does anyone have an idea how to fix that? Oh: It looks like that's not the problem. I killed plymothd and now it's starting but following happens: Sorry didn't copy the very first line
This might be it |
It somehow works again, no clue why. |
It seems to be a theme related issue. Doesn't work with my theme anymore. |
Description of Problem:
There seems to be 2 errors on the boot splash screen.
The
error: Unexpectedly disconnected from boot status daemon
appears on both on the live CD, and the finished installation;The
Failed to start Show Plymouth Boot Screen
only appears in a completed installation.plymouth
cannot be found injournalctl -xe
nordmesg
/var/log/boot.log
does not exist, and thus I cannot see what happened on boot.Screenshot of boot screen
Screenshot of
systemctl status plymouth-start
Expected behaviour:
The elementaryOS boot splash screen should be displayed on screen, then "boot normally"
/var/log/boot.log
should also exist (correct me if I am wrong)What I tried
Some searching around suggests that it is a kernel incompatibility (for some reason).
As such I downgraded the kernel from
5.8.0-50-generic
to5.8.0-49-generic
. The errors stopped appearing, but the splash screen is still not showing (might be a separate issue altogether).Platform:
elementary-os-6.0-daily.20210430.iso
linux-5.8.0-50-generic
The text was updated successfully, but these errors were encountered: