I am experiencing an identical issue to one posted here previously; after installing Anaconda, the error dialog box “Could not start d-bus, can you call qdbus-qt5” is seen at login.
After looking through many threads, I see there is a simple but inconvenient fix which is to edit ~/.bashrc and comment out the line below
# export PATH="/home/nick/anaconda3/bin:$PATH
This does work and when the line is commented out, KDE starts correctly.
However, I would really like to be able to keep the line in .bashrc as I otherwise need to state the full path to every function I call from ~/anaconda3/bin
I have read through the information in the above thread and have attempted the solutions recommended by wolfi323 in post #4
Of the three options suggested by wolfi323, I have already confirmed that option 1 works but is a little inconvenient.
The other two options were
- copy or symlink qdbus-qt5 in /home/username/anaconda3/bin
- modify /usr/bin/startkde and add the explicit path to the call to qtpaths, i.e. replace qtpaths with /usr/bin/qtpaths
I have attempted the symlink option without any success, but this could be a mistake on my part as I still very much a novice!
This is how I attempted it.
I have an up to date installation of OpenSuse Leap 42.3
**When “PATH =” line is commented out of ~/.bashrc
> qtpaths --binaries-dir /usr/lib64/qt5/bin > which qtpaths /usr/bin/qtpaths
When “PATH =” line is NOT commented out of ~/.bashrc
>qtpaths --binaries-dir /home/nick/anconda3/bin >which qtpaths /home/nick/anaconda3/bin/qtpaths
If I understand correctly, I need to backup and remove the copy of qtpaths from /home/nick/anaconda3/bin and place a symlink to either /usr/lib64/qt5/bin/qtpaths or /usr/bin/qtpaths.
This is what I tried.
mv ~/anaconda3/bin/qtpaths ~/qtpaths.bak ln -s /usr/lib64/qt5/bin/qtpaths ~/anaconda3/bin/qtpaths
Did not work so I then tried
rm ~/anaconda3/bin/qtpaths ln -s /usr/bin/qtpaths ~/anaconda3/bin/qtpaths
Am I doing this correctly. If not,please could someone explain where I am going wrong.