elementary / greeter

Login and Lock Screen greeter for elementary OS and Pantheon, using LightDM
GNU General Public License v3.0
152 stars 39 forks source link

[Odin] Boot log visible as console output between greeter and logout/shutdown, no boot animation (plymouth) on system startup #552

Open joeredhead76 opened 2 years ago

joeredhead76 commented 2 years ago

What Happened

When I shutdown my computer, I get this weird writing before the computer shuts off. h0iay9bajyg71

Expected Behavior

According to sub-reddit, this writing should only be present when installed in legacy mode (I installed in UEFI). I re-installed a second time (clean install) in UEFI mode and same writing in screen at shutdown. I should see the device logo, but I do not. I ran the command "sudo nano /etc/default/grub" and have this setting: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash". The splash screen should be persistent after next reboot, but it is not.

See this sub-reddit post as I am not the only one with this issue: https://www.reddit.com/r/elementaryos/comments/p33wma/anybody_else_have_this_screen_on_shut_down_and/

There seems to be a solution here: https://elementaryos.stackexchange.com/questions/28374/shutdown-splash-not-working/28377?noredirect=1#comment28209_28377 but did not try it.

Steps to Reproduce

  1. Shutdown my computer
  2. (see writing of shutdown screen attached)

Platform Information

joeredhead76 commented 2 years ago

Should I try updating the drivers / software found here: https://www.dell.com/support/home/en-ca/product-support/product/latitude-e6520/drivers

joeredhead76 commented 2 years ago

I noticed that this "writing" also appears when logging out (not only shut down).

stradicat commented 2 years ago

By any chance, do you see any (Elementary) logo whilst booting the computer?

(possibly related)

joeredhead76 commented 2 years ago

You are correct. I do not see the eOS logo at start up or shutdown.

stradicat commented 2 years ago

I decided to install, on the same machine, Ubuntu and Kubuntu 20.04 over the course of 2 days, and on both, the boot logo, provided by the plymouth package, is shown, and no boot log on the console is shown between logouts and the greeter, or shutdowns for that matter.

It looks as if plymouth weren't working correctly, leaving a layer gap between the boot log information and the greeter.

joeredhead76 commented 2 years ago

Wow, thanks for the testing. So is this due to eOS 6? Or my specific laptop (Dell Latitude E650)? And is it fixable?

joeredhead76 commented 2 years ago

Found this old post: https://elementaryforums.com/index.php?threads/solved-plymouth-bootsplash-problems.2434/

Would instructions to fix help my situation?

stradicat commented 2 years ago

I'll try later this afternoon, but it does looks like the right place to begin troubleshooting.

joeredhead76 commented 2 years ago

Thanks in advance!

stradicat commented 2 years ago

It didn't work for Odin.

joeredhead76 commented 2 years ago

Hmm, that’s too bad. So will the Odin developers look into this bug?

stradicat commented 2 years ago

I truly hope they do, 'cause it's a bit of a show-stopper for the clean user experience the team has been providing for the past years.

stradicat commented 2 years ago

For visibility, I'd edit the issue's title and change it to:

[Odin] Boot log visible as console output between greeter and logout/shutdown, no boot animation (plymouth) on system startup

That way, maintainers will better identify the type of bug, and handle it accordingly.

joeredhead76 commented 2 years ago

Just changed the title; thanks for the suggestion!

dbustosrc commented 2 years ago

Hello, I also have this bug. This is the hardware configuration of my computer: Samsung 700Z5B CPU: Intel i72675QM GPU: AMD ATI Radeon HD 6400M/7400M Series GPU: Intel 2nd Generation Core Processor Family UEFI Boot: Enabled Secure Boot: Not available/disabled

GPU ATI Radeon HD 6400M/7400M Series is using the open-source controller radeon GPU Intel 2nd Generation Core Processor Family is using i915 open source controller

When GRUB loads, it falls into RECORDFAIL_TIMEOUT ignoring GRUB_TIMEOUT=0 and counting down 30s on every boot, you can see #168 and #178

In case this information would be useful, this is the service plymouth-read-write status

● plymouth-read-write.service - Tell Plymouth To Write Out Runtime Data
     Loaded: loaded (/lib/systemd/system/plymouth-read-write.service; static; vendor preset: enabled)
     Active: inactive (dead) since Wed 2021-08-25 18:46:27 -05; 16min ago
    Process: 673 ExecStart=/bin/plymouth update-root-fs --read-write (code=exited, status=2)
   Main PID: 673 (code=exited, status=2)

ago 25 18:46:27 Samsung-700Z5B systemd[1]: Starting Tell Plymouth To Write Out Runtime Data...
ago 25 18:46:27 Samsung-700Z5B plymouth[673]: error: unexpectedly disconnected from boot status daemon
ago 25 18:46:27 Samsung-700Z5B systemd[1]: plymouth-read-write.service: Succeeded.
ago 25 18:46:27 Samsung-700Z5B systemd[1]: Finished Tell Plymouth To Write Out Runtime Data.