i assume its caused by me messing with the ~/.bash_profile by adding fish and fastfetch like this
# ~/.bash_profile
Fastfetch
Fish
# Load ~/.bashrc if it exists
if [ -f ~/.bashrc ]; then
source ~/.bashrc
fi
# Add custom paths
export PATH="$HOME/bin:/usr/local/bin:$PATH"
# Set environment variables
export EDITOR="nano"
# Aliases
alias ll='ls -la'
i did went through the ctrl + alt + f4 to edit back the file
but it still the same
i also did ran
sudo chsh -s /usr/bin/bash
systemd.unit=rescue.target (on the grub menu thing)
last time i checked ~/.bash_profile it was like this
# ~/.bash_profile
# Load ~/.bashrc if it exists
if [ -f ~/.bashrc ]; then
source ~/.bashrc
fi
# User specific enviroment and start up program
then i change it to
# ~/.bash_profile
# Load ~/.bashrc if it exists
if [ -f ~/.bashrc ]; then
source ~/.bashrc
fi
# Add custom paths
export PATH="$HOME/bin:/usr/local/bin:$PATH"
# Set environment variables
export EDITOR="nano"
# Aliases
alias ll='ls -la'
still the same
i also did ran journallctl -b -1 -p 3 -x and it shows fedora dbus-broker-launcher(814): activation request for 'org.freedesktop.nm_diskpatcher' failed
i just switched from windows so iam trying to learn for future troubleshoot aswell
You can type ESC to see the messages on the console which may give you a clue where the system has stopped.
These edits to .bash_profile likely cause issues.
Comments on configuring bash.
aliases need to go into .bashrc not .bash_profile.
avoid printing anything from .bash_profile if the output is not a tty.
I use this to tell interactive from background using of the profile.
# Must not output anything otherwise cron jobs will send email.
if [ -t 1 ] # is stdout a tty?
then
# command here that require an interactive session
echo "Login via bash profile - terminal $TERM"
fi
Bear in mind that Linux is case sensitive, as a rule. As such, “Fastfetch” will not work, as the command is stored on disk as fastfetch. Same with “Fish”… however, you’ve removed them so we’re heading in the right direction.
Reboot KDE again, log in as you would normally, and do as @barryascott suggests and post a picture of any output you see.
You cal also switch to another terminal using Ctrl+Alt+F3/F4/F5 - it’ll be a black screen with a login: prompt. Enter your xdd username, and the password you picked and then take a screenshot of any errors you get when logging in. If that all goes, ok, you’ll be dropped off as a shell prompt.
At this point you can issue the journalct -b command to look at the log messages from the current boot and scroll to the bottom to see what occurred when you tried to log in.
i didnt really get this part too much but heres what i did idk if i did it correctly
i did press esc during the pre log in boot up and everything seems to pass (green texts)
after logging via gui it doesnt show anything just static
next i did type in the script to ~/.bash_profile via vim
i logged in fine in the Ctrl+Alt+F4 thingy the fish and fastfetch runs there normally
heres the end of the journalct (i tried my best the phone refuses to focus)
