this post was submitted on 31 Oct 2024
20 points (100.0% liked)
Linux
48306 readers
853 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Ok, mister/miss, thank you for such an advanced explanation and absence of fight creation.
I have access to the system via CLI but idk where I can find the logs. After all I don't even know how to use curl or grep. I'm not a very advanced user.
i'm going to assume that endeaveros is using systemd so you'll need journalctl and sudo at a minimum.
do you have access to both? as in can you run both commands?
I can run all commands. I just can't start the GUI. I'd also assume that commands like btop (TTY tools that require full color or image support) won't work.
Also I can't access anything after a GUI login attempt without a reboot so if the logs aren't saved, I can't access them.
in your shoes: i would run
journalctl -fto watch the logs scroll by on screen in one virtual terminal (whatever the systemd equivalent is nowadays; it was alt+ctrl+f1 through f7 back i the sysv-init days) and try to log in again on the base xserver virtual terminal and try to watch for errors/failures/warnings messages from that those scrolling logs.journalctl is a unifiied logging system that comes with systemd so your logs are likely to persist there and it has built in tools to help you narrow it down if you see anything in the logs.
When I try to log in, the screen goes black with artifacts and switching to another terminal to see logs is impossible.
when you use an xserver, it occupies one of those virtual terminals that i referenced in my last message.
most distros use 7 virtual terminals and the xserver is usually dedicated to one of them and that means you can use the keyboard shortcuts of alt+ctrl+f1 through alt+ctrl+f7 to switch from your xserver and into a bash prompt where you can then log in without the xserver and execute that command to look at the logs.
you can toggle between all 7 terminals at any time without impacting each other; you can use those keyboard shortcuts to help you troubleshoot this and all xserver problems in an "alt-tab" like fashion switching back and forth between the xserver and six other terminals where you can do things like execute commands; look at logs; & modify configs.
I don't think you understand what I say so I guess you won't be able to help me.
your call and good luck