Apparently there's work on new splashscreen method, maybe it will be faster than Plymouth: https://www.phoronix.com/scan.php?page=news_item&px=SUSE-Kernel-Bootsplash

Instead of Plymouth, a simple Solus ASCII art would look nice :)

@Faults Comment removed. Please keep your language appropriate here. Thanks =)

1. It's normal.
2. I mean, this issue isn't resolved yet so should be pretty obvious that you're still gonna get the messages :P

Urrr.... it's not that bad.

I confirm. I have lots of nasty noise on my LUKS password prompt... looks like shit has hit the fan.

As it was not yet explicitly mentioned, I'll add that (only after upgrading a newly installed system), right before the Luks passphrase prompt, there's a message saying:

When I shutdown I get this message: "Reboot: Power off", and on boot up, after entering pass to decrypt (FDE) I see some blue messages. After last kernel update, I'm not seeing the fsck messages.

I still get some messages during boot or shutdown: watchdog did not sleep.

@ikey can this be closed now ?

Yes I also noticed a very clean black screen with just a blinking vertical line like this --> |
Silent boot is finally silent. Thanks! :)

Since the update of today the boot is only black screen, I think it's slient now :P

Not sure why it was closed still lol - i know we made it noisier

@ikey Opening this again since it's not fully silent.

I can confirm that it is not entirely silent. I also did a clean install of the latest release without Luks.

I did a clean install of the latest release and have them too, so don't think it's either due to Luks

I still see messages about systemd-fsck. Maybe because I installed Solus Mate 2017.01.01.0 and now I'm on the latest version.

OK closing due to lack of response. Reopen if you disagree

Recent activities was emptied so as this is close, I'm posting this just just to let it appear again.

I'm using LUKS and after enter password it still shows a few messages about systemd-fsck for just a second or less. Is this normal or could it be hidden too?

Silent boot now implemented in https://git.solus-project.com/packages/linux-lts/commit/?h=linux-lts-4.9.23-19

No we'll merge it now because I'm doing the ffmpeg revdeps, and the ABI diff is ok

@ikey you'll be happy to ear that ffmpeg 3.3 has just been released today **no don't hit me please** ;-)
I did compile it and I checked VLC to make sure the patch still works.
I guess you probably don't want to rebuild everything today so I'm looking at the configure option there are many libraries that could be enabled.

@ikey Lollypop push pending as well once the upgrade is more finalized: https://git.solus-project.com/packages/lollypop/commit/?id=7b29acf135eda0fb979beefa623e1610810fe752

I'd say this is fixed..

Marking as resolved. We have since chosen our default wallpapers and updated the cursor theme.

@Tick Please confirm as to whether the latest kernel updates (you'll have one from more recently than 4.9.10) resolves this issue.

Resolved in unstable as of https://git.solus-project.com/packages/solus-sc/commit/?id=e520ec78cfc613ddc91d270893f681cafdb7434a

Happy to hear it :)

@kyrios123 @ikey i can confirm that after installing the latest round of updates this issue is resolved.
Thank you very much for all the amazing hard work !!

@the_mentor are you on unstable ? If not, you'll have to wait a little longer until it's pushed on the stable repo

Hi @ikey i've updated my Solus MATE to the latest version and i'm still experiencing this issue.
is there anything specific i need to do to install this fix?

Nice, I was looking forward to this for my netbook install. Thanks for the great work!

Ok, can T2794 be reopened then ?
Because it was closed and merged with this task.

That's a different issue @kyrios123 - this one is about basic layout switching. which is resolved.

@ikey unfortunately it doesn't solve the problem here (at least for T2794)

Resolved in https://git.solus-project.com/packages/libxklavier/commit/?h=libxklavier-5.4-7
Update is now in unstable

Thanks to the update in the repos, I could do a real world test, and it showed that there's just a one-line issue:

It's already been chosen

I was also thinking Excl_Autumn_Retreat as the default login screen image and the desktop wallpaper image as the lock screen image (though BrittasLake looks a lot better than Excl_Focal_Leaf on the lock screen).

On a 2nd thought, we need a timeout callback because otherwise if the user does not click, we'll run into the issue that we're blocking solus_update.

You'll want to get the MainLoop() into a variable though, and you'll want to quit it to avoid "hanging" in the background ;-). It will block until the Popen is through though (not when SC quits, but when the command was actually fired by Popen).

Does this break the GApplication integration? like will it still quit when told, retain single instance, etc.

Actually, there isn't a mainloop, neither Gtk nor GLib.

Awesome! :)

Very happy to finally resolve this :)

Minor underps:

• https://git.solus-project.com/packages/kernel-glue/commit/?h=kernel-glue-2-187
• https://git.solus-project.com/packages/kernel-glue/commit/?h=kernel-glue-3-188

open-vm-tools ported https://git.solus-project.com/packages/open-vm-tools/commit/?h=open-vm-tools-10.1.0-37

razer-drivers ported https://git.solus-project.com/packages/razer-drivers/commit/?h=razer-drivers-1.1.8-9

bbswitch ported https://git.solus-project.com/packages/bbswitch/commit/?h=bbswitch-0.8-35

broadcom-sta ported https://git.solus-project.com/packages/broadcom-sta/commit/?h=broadcom-sta-6.30.223.271-100

nvidia-glx-driver ported https://git.solus-project.com/packages/nvidia-glx-driver/commit/?h=nvidia-glx-driver-375.39-128

nvidia-340-glx-driver ported https://git.solus-project.com/packages/nvidia-340-glx-driver/commit/?h=nvidia-340-glx-driver-340.102-88

nvidia-304-glx-driver ported https://git.solus-project.com/packages/nvidia-304-glx-driver/commit/?h=nvidia-304-glx-driver-304.135-124

Old janky kernel packages deprecated: https://github.com/solus-project/solus-sc/commit/e18aab1cec009d3eb572fcf1d87776d85189b3af

First build of linux-lts now going in: https://git.solus-project.com/packages/linux-lts/commit/?h=linux-lts-4.9.18-10

dracut now ypkg only and dejankified https://git.solus-project.com/packages/dracut/commit/?h=dracut-33-34

Added a janky kernel-glue package to handle the triggers: https://git.solus-project.com/packages/kernel-glue/commit/?h=kernel-glue-1-186

Can't wait to see how it goes :D

OK CBM is in Solus repos now, time to actually make things "work"

GRUB2 support is now in git - we just need to get this integrated and tested in Solus now

BTW while I'm weighing on the splash thing - I'll say one last bit here and then open a new bug:

This is a bug not a discussion :P Not sure why this is going as derailed as this is. It's for me to track a bug. I'm not adding a splash at this moment because it *seriously* regresses boot times and causes VT switch failures.
When I'm ready to add a splash, I'll create a bug about it :)

Latest comment removed for violation of our Community Guidelines. Further commenting of such type will result in a ban.

I removed your comment because you were giving a fellow user a hard time. You're doing it again, thus removing again. The conversation was already had regarding Plymouth, I suggest the focus remain on the initial TODOs and other ideas that wouldn't degrade boot times.

We're not adding a boot / splash screen. Not really sure why such an off-topic discussion is happening on this task. Let's move the discussion back to the actual task at hand, thank you.