Ok, I’ll do my best to read stuff I receive, thanks…
I’m new and I try to make things correctly, not to mess it up
1 Like
Also, I’m not trying to doubt anyone’s answers, maybe my English isn’t the best 
I believe what people say, ngl , I’m trying my best to learn to use this distro instead of windows, I barely got the idea how to set up the Brower so it doesn’t overheating that mx150
I’m just not understanding everything, sometimes I keep looking for alternatives, perhaps not my best practice 
At this : journalctl -b -p3
As an example I wanted to see more things than the current boot cuz I rebooted the laptop like 5-8 times today to see boot speeds and test out the SSD
Pls don’t ban me for this
We have expressed to you in a few threads about learning the System you are using. For now please learn how to use the log tool so when you do have an issue you can show us the logs with the error messages. Instead of posting pictures most of us wont bother to try and look at since they always seem to cut out most of the important information needed.
While your there you can learn about other parts of the OS from here
https://discovery.endeavouros.com/
and everything Arch from here
https://wiki.archlinux.org/
Please calm down start learning and enjoying your system. Why we are always glad to help it is ultimately your responsibility to know the system your using.
3 Likes
No, I won’t.
2 Likes
ok, I think I got it , thanks, here’s the log tool answer : https://0x0.st/H72u.txt
I think it’s my first time using this, like ever 
I don’t think this is the message that you’re concerned about since it has nothing to do with configuring your DE or making modifications.
If you have the time, just obtain the journal entries for the current boot and go through them line by line.
$ journalctl -b0
2 Likes
You know what? Just run these commands:
$ journalctl -b2 | eos-sendlog
$ journalctl -b1 | eos-sendlog
$ journalctl -b0 | eos-sendlog
Each of those commands will output a url. Post those urls here. I will try to look through them when I have time.
1 Like
[cris@cris-pl627rc ~]$ $ journalctl -b2 | eos-sendlog
bash: $: command not found
eos-sendlog-helper: error: No input!
[cris@cris-pl627rc ~]$ journalctl -b2 | eos-sendlog
→ The URL below will expire in 7 days.
https://0x0.st/H72_.txt
[cris@cris-pl627rc ~]$ journalctl -b1 | eos-sendlog~
bash: eos-sendlog~: command not found
[cris@cris-pl627rc ~]$ journalctl -b1 | eos-sendlog
→ The URL below will expire in 7 days.
https://0x0.st/H72L.txt
[cris@cris-pl627rc ~]$ journalctl -b0 | eos-sendlog
→ The URL below will expire in 7 days.
https://0x0.st/H729.txt
[cris@cris-pl627rc ~]$
I hope is better now
Nothing in these logs contain the “weird message” you mentioned.
You mentioned that the “weird message” appeared every time you reboot after the update, but not in subsequent boots.
In that case, run paclog to see the timestamp of your most recent system update. You don’t have to post the output of paclog here. Just take note of the timestamp, and then use that time stamp to filter journalctl’s output.
$ journalctl --since="the timestamp" | eos-sendlog
Since you saw the message after you rebooted post-update, we can reasonably infer that message had appeared shortly after that timestamp.
2 Likes
This is what I told you earlier… Remember the tip I gave you about the community…
1 Like
It’s likely that it was something of today, I’ve seen it 2 times , but not more, so I said yesterday in the “…” sign
Couldn’t have been something bad though, maybe it was just the OS applying the updates, after a restart
It happened after I restarted after updating and after installed Vivaldi codecs
yea, now I get it
That’s not exactly helpful when it comes to narrowing down journal logs. Systemd’s journaling system could log thousands of entries a day.
What is the timestamp for this?
$ paclog | grep "vivaldi-ffmpeg-codecs"
2 Likes
Please don’t post photos - you’ve been asked and instructed on how to inform us with your journal. Use that.
It’s at the bottom of your post so you can edit your posts.
If you’re this nervous, why not look at the exact opposite way - expect to mess it up, figure out why, how to fix it and reinstall when you get lost. Taking apart config files and what not is how I started to learn and understand. Plan to break it! Learn from it.
2 Likes
[cris@cris-pl627rc ~]$ paclog | grep “vivaldi-ffmpeg-codecs”
[2024-03-05T07:04:50+0200] [PACMAN] Running ‘pacman -S vivaldi-ffmpeg-codecs’
[2024-03-05T07:04:54+0200] [ALPM] installed vivaldi-ffmpeg-codecs (122.0.6261.84-1)
[cris@cris-pl627rc ~]$ paclog | grep “vivaldi-ffmpeg-codecs”
[2024-03-05T07:04:50+0200] [PACMAN] Running ‘pacman -S vivaldi-ffmpeg-codecs’
[2024-03-05T07:04:54+0200] [ALPM] installed vivaldi-ffmpeg-codecs (122.0.6261.84-1)
[cris@cris-pl627rc ~]$
Now run this command:
$ journalctl --since="2024-03-05 07:04:00" | eos-sendlog
Post the link here.
1 Like
You’ve also been asked to format this so we can read it.
Well, I can’t format it again, by the looks of it the SSD got corrupted somehow , gotta wipe it
I guess reinstalling might be the way:/
I’m confused. How did we go from seeing a weird boot log to a corrupted SSD? how did u come to that conclusion?
Maybe post the output of the command I mentioned first?
I was talking about your post, not your drive.