Is there any problem with new Tumbleweed using cnf command ?
shahram@EWS:~> cnf cnf
cnf: searching … shahram@EWS:~>
It seems to be working here.
My googlefu struck out try to find out how cnf works. Does it depend on a database that might not yet have been built since TW was installed?
It might be the reason, but could not find it!
cnf cnf
Program 'cnf' is present in package 'command-not-found', which is installed on your system.
Absolute path to 'cnf' is '/usr/bin/cnf'. Please check your $PATH variable to see whether it contains the mentioned path.
Somehow you could be missing that package.
Is your openSUSE install from a fairly standard source or is it a kind of JeOS?
HTH,
TSU
It is full Tumbleweed not JeOS.
I have installed many packages and have a feeling that some sort of mismatching occurred.
shahram@EWS:~> zypper info cnf
Loading repository data…
Reading installed packages…
package ‘cnf’ not found.
shahram@EWS:~>
Also see the result of this command:
shahram@EWS:~> zypper info command-not-found
Loading repository data…
Reading installed packages…
Information for package command-not-found:
Repository : Main Repository (OSS)
Name : command-not-found
Version : 0.2.1+20181004.20a0aae-1.2
Arch : noarch
Vendor : openSUSE
Installed Size : 106.5 KiB
Installed : Yes
Status : up-to-date
Source package : scout-0.2.1+20181004.20a0aae-1.2.src
Summary : Command Not Found extension for shell
Description :
The “command not found” message is not very helpful. If e.g. the unzip
command is not found but it’s available in a package, it would be very
interesting if the system could tell that the command is currently not
available, but installing a package would provide it.
shahram@EWS:~>
Hi
Perhaps as indicated in the output, check $PATH and see if the which command works…
which cnf
/usr/bin/cnf
echo $PATH
The output:
shahram@EWS:~> which cnf
/usr/bin/cnf
shahram@EWS:~> echo $PATH
/home/shahram/bin:/usr/local/bin:/usr/bin:/bin:/usr/lib/mit/bin:/snap/bin
The path to your User home directory appears to be causing problems.
Instead, elevate your console and then run “cnf”
Don’t know what the problem may be on your system though…
I can’t replicate your problem on a TW.
TSU
Noticed your other post about Anaconda installed, that may be what altered your $PATH.
TSU
Yes I had a problem running jupyter notebook and navigator after installed latest Anaconda and cnf issue might happened after that.
Nevertheless, I have deleted Anaconda and installed Jupyter from the source and works fine.
Can you please let me know I can revert back my home path to the proper one?
Actually, your $PATH looks fine but behaves oddly so I can’t be certain what the problem might be.
Maybe check to see if a “cnf” exists somewhere in your Anaconda directory tree.
TSU