I wonder how other distros manage this package if it is breaking packages, is it just for us?

Just being curious, is systemd upgrade also expected for the new iso?

Any news about Fastly response?

Is there any blocker or anything else expected to get done before Solus 4.1 release? Just out of curiosity

I think these two should be added too:
https://dev.solus-project.com/T2833
https://dev.solus-project.com/T4336

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'm using just current (did clean install when Solus 3 was released and I chose in the installer to use all disk)

I'm my case I have Bios and full disk encryption, made by Solus' installer

Not getting exactly the same as the above

In T4235#83002, @ikey wrote:

So do you mean fw capsule updates managed by clr-boot-manager? Sounds good to me tbh - so we should raise this on the upstream clr-boot-manager repo. Weird me not
being the upstream anymore :P

Now that Make repos go fastly is resolved, you can mark "Draw up a formal sync cycle (i.e. how to remain unblocked and maintain high velocity)" as done right?

If you are still deciding into multiple options, maybe you could do a poll on Google+ to finally choose one and close this task :p

I think these things could be added too:

Well, I finally manage to get it working:

@ikey This appeared (I used /dev/sda):
"tune2fs 1.43.4 (31-Jan-2017)
tune2fs: Número mágico incorrecto en el superbloque mientras se intentaba abrir /dev/sda (translated: Superblock incorrect magic number when trying to open /dev/sda)
/dev/sda contiene datos `DOS/MBR boot sector'"

@ikey oh, didn't know that, I just thought you maybe forgot about this;p And how can I check that?

Now that you are rebuilding the kernel, any chance you could take at look at the systemd-fscheck message to hide it too (silent boot related)

In my case it lasts like 8 seconds. In my .profile and .bashrc the only line I have is "source /usr/share/defaults/etc/profile". I don't know if this is the default behavior, but I always end up using Ctrl+C as 8 seconds waiting it to restore the prompt seems for me too much.

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

Yeah, already tried on a virtual machine and you are right, maybe I overwrote it, so let's close this. Thanks anyways!

Any news on this?

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

There is no need to have a duplicate task, so you can close this one (not sure if I can change the status or not)

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?