Weird [OK] message before starting DE after installing software and/or updating

Chris2KN · March 5, 2024, 6:48am

I updated the OS today…

Something weird that I cannot catch easily with my camera is happening:

After installing something, let’s say neofetch,it doesn’t matter really, updating also does this :

Before entering the DE, at the steps before when doing that checkup of sorts when the screen has green OK lines on it,

There’s an additional line that’s like:

[OK] something about configuring either the DE and modifications after/before restart

Weirdly… after a restart the thing doesn’t happen anymore and the system doesn’t take 1/3 of a second more to start

I’m on cinnamon with Dracut btw

Good thing is that’s working, it boots and everything with the DE is ok,but there’s something weird about that message, I’ll try catching it tonight

GjMan78 · March 5, 2024, 9:53am

OMG no camera needed, just use journalctl!

Chris2KN · March 5, 2024, 9:59am

So what’s the syntax for that?

Is this enough:

journalctl --since=today

?

I found it on Copilot

Bryanpwo · March 5, 2024, 10:04am

As in many signs in daily life, green means literally okay. The system informs you it successfully started or stopped a background service. You should be worried when the red error message appears.

GjMan78 · March 5, 2024, 10:05am

journalctl -b shows all messages related to the current boot.

journalctl -b -p3

shows all error messages related to the current boot

Chris2KN · March 5, 2024, 10:05am

The point is that the text seemed like something it instructed me to do , but it had an OK thing before it

Everything happened before the DE started

Chris2KN · March 5, 2024, 10:06am

What about previous boots ?

GjMan78 · March 5, 2024, 10:07am

-b-1

man journalctl

it’s your friend and it’s free!

Bryanpwo · March 5, 2024, 10:07am

It isn’t instructing you to do something. It is informing you whilst performing the start-up/close-down.

anthony93 · March 5, 2024, 10:12am

If you remember certain keywords in that message, just pipe journalctl’s output into grep.

$ journalctl --since=today | grep "some keyword"

or

$ journalctl --since=today --grep="some keyword"

Chris2KN · March 5, 2024, 10:25am

So ?

Is anything wrong in here ?

anthony93 · March 5, 2024, 10:32am

Even if there is, I wouldn’t know. Because what you posted is only the first 52 lines of the entire journal log since today. I’m pretty sure the “[OK]” message you’re worried about is way past line 52 since, you know, it didn’t appear in the photo you took.

Like I mentioned in my earlier post, if you remember a keyword or phrase in that journal entry, use the --grep flag with the journalctl command.

Did I mistype anything in that post? Pretty sure I didn’t.

Chris2KN · March 5, 2024, 10:37am

allrighty, I have logeed in from the laptop , here’s what it gave me :

mar 05 06:37:53 cris-pl627rc systemd[1]: Starting Notify about reboot on special conditions…
mar 05 06:37:53 cris-pl627rc systemd[1]: eos-reboot-required.timer: Deactivated successfully.
mar 05 06:37:53 cris-pl627rc systemd[1]: Stopped Notify about reboot on special conditions…
mar 05 06:37:53 cris-pl627rc systemd-logind[489]: /efi/loader/loader.conf:5: Unknown line ‘reboot-for-bitlocker’, ignoring.
mar 05 06:37:54 cris-pl627rc systemd[1]: eos-reboot-required.service: Deactivated successfully.
mar 05 06:37:54 cris-pl627rc systemd[1]: Finished Notify about reboot on special conditions…
mar 05 06:37:57 cris-pl627rc systemd-logind[489]: /efi/loader/loader.conf:5: Unknown line ‘reboot-for-bitlocker’, ignoring.
mar 05 06:38:04 cris-pl627rc systemd-logind[489]: /efi/loader/loader.conf:5: Unknown line ‘reboot-for-bitlocker’, ignoring.
mar 05 06:38:05 cris-pl627rc systemd-logind[489]: /efi/loader/loader.conf:5: Unknown line ‘reboot-for-bitlocker’, ignoring.
mar 05 06:38:05 cris-pl627rc systemd-logind[489]: /efi/loader/loader.conf:5: Unknown line ‘reboot-for-bitlocker’, ignoring.
mar 05 06:38:05 cris-pl627rc systemd-logind[489]: /efi/loader/loader.conf:5: Unknown line ‘reboot-for-bitlocker’, ignoring.
mar 05 06:38:07 cris-pl627rc systemd-logind[489]: /efi/loader/loader.conf:5: Unknown line ‘reboot-for-bitlocker’, ignoring.
mar 05 06:58:35 cris-pl627rc systemd[1]: Started Notify about reboot on special conditions…
mar 05 06:58:35 cris-pl627rc systemd[1]: Starting Notify about reboot on special conditions…
mar 05 06:58:35 cris-pl627rc systemd[1]: eos-reboot-required.timer: Deactivated successfully.
mar 05 06:58:35 cris-pl627rc systemd[1]: Stopped Notify about reboot on special conditions…
mar 05 06:58:38 cris-pl627rc systemd[1]: eos-reboot-required.service: Deactivated successfully.
mar 05 06:58:38 cris-pl627rc systemd[1]: Finished Notify about reboot on special conditions…
mar 05 06:59:10 cris-pl627rc systemd-logind[489]: The system will reboot now!
mar 05 06:59:10 cris-pl627rc systemd-logind[489]: System is rebooting.
mar 05 06:59:12 cris-pl627rc systemd[1]: systemd-reboot.service: Deactivated successfully.
mar 05 06:59:12 cris-pl627rc systemd[1]: Finished System Reboot.
mar 05 06:59:12 cris-pl627rc systemd[1]: Reached target System Reboot.
– Boot d04e5d08f41341faa3151e46aadf3992 –
mar 05 06:59:32 cris-pl627rc systemd[1]: Started Notify about reboot on special conditions…
mar 05 06:59:32 cris-pl627rc systemd[1]: Starting Notify about reboot on special conditions…
mar 05 06:59:32 cris-pl627rc systemd[1]: eos-reboot-required.timer: Deactivated successfully.
mar 05 06:59:32 cris-pl627rc systemd[1]: Stopped Notify about reboot on special conditions…
mar 05 06:59:32 cris-pl627rc systemd-logind[502]: /efi/loader/loader.conf:5: Unknown line ‘reboot-for-bitlocker’, ignoring.
mar 05 06:59:33 cris-pl627rc systemd[1]: eos-reboot-required.service: Deactivated successfully.
mar 05 06:59:33 cris-pl627rc systemd[1]: Finished Notify about reboot on special conditions…
mar 05 06:59:37 cris-pl627rc systemd-logind[502]: /efi/loader/loader.conf:5: Unknown line ‘reboot-for-bitlocker’, ignoring.
mar 05 06:59:42 cris-pl627rc systemd-logind[502]: /efi/loader/loader.conf:5: Unknown line ‘reboot-for-bitlocker’, ignoring.
mar 05 06:59:43 cris-pl627rc systemd-logind[502]: /efi/loader/loader.conf:5: Unknown line ‘reboot-for-bitlocker’, ignoring.
mar 05 06:59:43 cris-pl627rc systemd-logind[502]: /efi/loader/loader.conf:5: Unknown line ‘reboot-for-bitlocker’, ignoring.
mar 05 06:59:43 cris-pl627rc systemd-logind[502]: /efi/loader/loader.conf:5: Unknown line ‘reboot-for-bitlocker’, ignoring.
mar 05 06:59:45 cris-pl627rc systemd-logind[502]: /efi/loader/loader.conf:5: Unknown line ‘reboot-for-bitlocker’, ignoring.
mar 05 07:03:25 cris-pl627rc systemd-logind[502]: /efi/loader/loader.conf:5: Unknown line ‘reboot-for-bitlocker’, ignoring.
– Boot c1402808282443e093ac18cc46a01560 –
mar 05 07:06:17 cris-pl627rc systemd[1]: Started Notify about reboot on special conditions…
mar 05 07:06:17 cris-pl627rc systemd[1]: Starting Notify about reboot on special conditions…
mar 05 07:06:17 cris-pl627rc systemd[1]: eos-reboot-required.timer: Deactivated successfully.
mar 05 07:06:17 cris-pl627rc systemd[1]: Stopped Notify about reboot on special conditions…
mar 05 07:06:17 cris-pl627rc systemd-logind[480]: /efi/loader/loader.conf:5: Unknown line ‘reboot-for-bitlocker’, ignoring.
mar 05 07:06:18 cris-pl627rc systemd[1]: eos-reboot-required.service: Deactivated successfully.
mar 05 07:06:18 cris-pl627rc systemd[1]: Finished Notify about reboot on special conditions…
mar 05 07:06:21 cris-pl627rc systemd-logind[480]: /efi/loader/loader.conf:5: Unknown line ‘reboot-for-bitlocker’, ignoring.
mar 05 07:06:25 cris-pl627rc systemd-logind[480]: /efi/loader/loader.conf:5: Unknown line ‘reboot-for-bitlocker’, ignoring.
mar 05 07:06:25 cris-pl627rc systemd-logind[480]: /efi/loader/loader.conf:5: Unknown line ‘reboot-for-bitlocker’, ignoring.
mar 05 07:06:25 cris-pl627rc systemd-logind[480]: /efi/loader/loader.conf:5: Unknown line ‘reboot-for-bitlocker’, ignoring.
mar 05 07:06:25 cris-pl627rc systemd-logind[480]: /efi/loader/loader.conf:5: Unknown line ‘reboot-for-bitlocker’, ignoring.
mar 05 07:06:27 cris-pl627rc systemd-logind[480]: /efi/loader/loader.conf:5: Unknown line ‘reboot-for-bitlocker’, ignoring.
mar 05 07:06:59 cris-pl627rc systemd-logind[480]: The system will reboot now!
mar 05 07:06:59 cris-pl627rc systemd-logind[480]: System is rebooting.
mar 05 07:07:01 cris-pl627rc systemd[1]: systemd-reboot.service: Deactivated successfully.
mar 05 07:07:01 cris-pl627rc systemd[1]: Finished System Reboot.
mar 05 07:07:01 cris-pl627rc systemd[1]: Reached target System Reboot.
– Boot 21083bd939064f539b2a71b690765e34 –
mar 05 07:07:21 cris-pl627rc systemd[1]: Started Notify about reboot on special conditions…
mar 05 07:07:21 cris-pl627rc systemd[1]: Starting Notify about reboot on special conditions…
mar 05 07:07:21 cris-pl627rc systemd[1]: eos-reboot-required.timer: Deactivated successfully.
mar 05 07:07:21 cris-pl627rc systemd[1]: Stopped Notify about reboot on special conditions…

[cris@cris-pl627rc ~]$

anthony93 · March 5, 2024, 10:38am

Can you put ``` around the logs to make them easier to read?

Also, what command did you run to get that output?

Chris2KN · March 5, 2024, 10:39am

idk how to edit them all

anthony93 · March 5, 2024, 10:43am

I don’t see anything messages related to your DE in the logs you posted. What command did you run to get the output?

Chris2KN · March 5, 2024, 10:43am

journalctl --since=today --grep=“reboot”

Bryanpwo · March 5, 2024, 10:47am

Have you tried the command @GjMan78 gave you?

Chris2KN · March 5, 2024, 10:49am

It gave me some red code about

https://www.intel.com/content/www/us/en/developer/tools/software-guard-extensions/overview.html

Apparently it’s disabled, in bios , hopefully that ain’t too bad for Linux

It said Intel SGX disabled

Bryanpwo · March 5, 2024, 11:04am

This is the answer that was staring you in the face all the time. It was just implementing the changes the update was shipping. This is why certain core updates require a reboot. (This is very common on ANY OS, btw)

On another note, You come across as very anxious to use an Arch-based system. Don’t get me wrong, I applaud any effort to learn something new and that comes with a lot of questions.

The thing is that you seem to doubt not only the system itself but also the answers given to you by the community.
I just want to remind you that everyone over here is doing this in their spare time for the love of it. If anyone answers you, they either had the same issue and resolved it at some point or they want to share their knowledge about the background of the issue you are submitting.

If you keep doubting or ignoring the handouts you are kindly receiving, you will reach a limit with the community.

Just try and read carefully the help you are receiving and follow it or take it as a fact.