After installing Anaconda in root, I restarted the computer and tried to log in as root. After I keyed in the password at the log in page, the “setting” icon beside the “sign in” button started spinning, and the screen turns black, and then the log in page appears again. In other words, I am unable to log in, and it is not due to a wrong password.
However, I am able to log in with another created account.
I have tried restarting the computer a couple of times.
r3:~ # qdbus-qt5
If 'qdbus-qt5' is not a typo you can use command-not-found to lookup the package that contains it, like this:
cnf qdbus-qt5
r3:~ # qtpaths --binaries-dir
/root/anaconda3/bin
r3:~ # which qtpaths
/root/anaconda3/bin/qtpaths
r3:~ # grep anaconda /etc/profile* /etc/bash* ~/.profile* ~/.bash*
grep: /etc/profile.d: Is a directory
grep: /etc/bash_completion.d: Is a directory
grep: /root/.profile*: No such file or directory
/root/.bash_history:anaconda-navigator
/root/.bash_history:export PATH="$PATH:/home/r3/anaconda3/bin"
/root/.bashrc:export PATH="/root/anaconda3/bin:$PATH"
r3:~ #
I guess the proposed solution :
1) - remove the PATH= line that the Anaconda installer added from your ~/.bashrc and set the path manually before running Anaconda
2) - copy or symlink qdbus-qt5 in /home/haib/anaconda3/bin
Pardon me, how to do either?
You should not log in as root anyway though, and especially not to a graphical desktop.
Apparently it’s not installed. It normally would be in /usr/bin/ so it should be found even with the Anaconda installer’s changes.
What desktop are you actually using to which you cannot login anymore? That is vital in trying to troubleshoot the problem.
The threads I mentioned were about problems with KDE/Plasma, which of course relies heavily on Qt5, and cannot be started at all without qdbus-qt5.
r3:~ # qtpaths --binaries-dir
/root/anaconda3/bin
r3:~ # which qtpaths
/root/anaconda3/bin/qtpaths
r3:~ # grep anaconda /etc/profile* /etc/bash* ~/.profile* ~/.bash*
grep: /etc/profile.d: Is a directory
grep: /etc/bash_completion.d: Is a directory
grep: /root/.profile*: No such file or directory
/root/.bash_history:anaconda-navigator
/root/.bash_history:export PATH="$PATH:/home/r3/anaconda3/bin"
/root/.bashrc:export PATH="/root/anaconda3/bin:$PATH"
r3:~ #
So that’s exactly the same as in the other threads.
Not surprising, as that’s what the anaconda installer does. (and I consider this as bug in the anaconda installer, unfortunately they seem to not want to change it…)
I guess the proposed solution :
remove the PATH= line that the Anaconda installer added from your ~/.bashrc and set the path manually before running Anaconda
copy or symlink qdbus-qt5 in /home/haib/anaconda3/bin
Pardon me, how to do either?
Open the file /root/.bashrc in a text editor and remove this line:
export PATH="/root/anaconda3/bin:$PATH"
or comment it out (i.e. “disable” it) by adding a ‘#’ at the start of the line:
#export PATH="/root/anaconda3/bin:$PATH"
#2 would only help with Plasma, but actually we added a workaround to startkde meanwhile (in Leap 42.3) to avoid this problem caused by the anaconda installer, so that’s useless to try anyway.
Hm, that shouldn’t be influenced by the custom Qt that anaconda comes with.
Apparently there are other commands in /root/anaconda3/bin/ that would “clash” with the system’s ones, I don’t know as I never used or installed anaconda myself. (and I was only aware of that qtdbus-qt5 issue, that as I wrote is actually workarounded meanwhile in startkde)
and just for my future reference, the command to open and edit /root/.bashrc in text editor is:
gedit ~/.bashrc
I am still learning the commands …:beat-up:…
Well, that’s one option, there are of course many other text editors available too (both GUI and text mode).
But you can also just run one (gedit e.g.) from the application menu (like you would normally run other applications), and then click on “Open File” or similar. .bashrc is a hidden file though, so you may have to turn on the display of hidden files in the file dialog (if possible).