ubuntu-16.10 unable to locate package [closed] - putty

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
I have recently setup Ubuntu 16.10 and am trying to install PuTTY but keep getting an 'E: Unable to locate package putty' error. I have run both 'sudo apt-get update' and 'sudo apt-get upgrade'. Both complete with success. I have verified that 'main', 'universe', 'restricted', and 'multiverse' are all enabled. But I continue to get the error when trying to install PuTTY. This is the command I'm using 'sudo apt install putty'. Any thoughts on what might be going on?

I was able to finally determine that 16.10 was just too old to update properly. I have moved to 18.04 and successfully installed PuTTY.

This is a common problem when you follow the instructions on the PuTTY website.
Here is how to solve it for ubuntu:
instead of:
sudo apt-get install PuTTY
use:
sudo apt install putty
As expected the package is case sensitive but somehow even PuTTY haven't figured it out.

Related

Ubuntu apt dist-upgrade failing due to "/var/lib/dkms/nvidia-fs/2.14.12/source/dkms.conf does not exist" [closed]

Closed. This question is not about programming or software development. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 days ago.
Improve this question
I unfortunately found out during a boot that apt had failed to setup boot for an updated kernel correctly.
When I ran sudo apt dist-upgrade I found it was broken..
I have a manually installed the latest Nvidia GPUdirect/CUDA environment because of how old the official Ubuntu packages are. Obviously the install is now causing problems.
Things I tried:
I tried to find where you could "uninstall nvidia-fs". Couldn't find it on any documentation.
I tried to re-install nvidia-fs using the cuda.run installer. The didn't work successfully.
I traced out the scripts, and found a sizable script program that was called /usr/sbin/dkms, that had a "remove" flag.
ran the following command:
sudo dkms remove -m nvidia-fs -v 2.14.12
and then sudo apt dist-upgrade.
This repaired the kernel install. On to fixing the nvidia-fs install.

Error: grub-efi-amd64-signed in Ubuntu 20.04. Trying to install packages [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
I'm having problems when Iḿ trying ¿to install any package or software.
My OS is Ubuntu 20.04.
I've already tried all the solutions mentioned in this post https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1871963, including configure the UEFI, following the next comand lines:
# sudo apt-get purge grub\*
# sudo apt-get install grub-efi
# sudo apt-get autoremove
# sudo update-grub
etc.
The error message appears even when the upgrades and is installed an app from the "Ubuntu Software" application...
Errors were encountered while processing:
grub-efi-amd64-signed
E: Sub-process /usr/bin/dpkg returned an error code (1)
Thanks!
I had this same problem the last few days. Months ago I installed Ubuntu 20.04 alongside Win10 I had to switch the BIOS to AHCI from RAID as it wouldn't allow install. Then after install I could switch back to RAID to allow Win10 dual boot. However along some update it messed it up and I had to switch back to AHCI and reinstalled grub as above. It sorted the problem.

"Raspberry Pi 3 No sound output over hdmi" [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 3 years ago.
Improve this question
I connected the Raspberry to my tv via HDMI cable but no sound came out, i tried to install libraries:
sudo apt-get install alsa-utils
sudo apt-get install mpg321
sudo apt-get install lame
and loaded the driver:
sudo modprobe snd_bcm2835
and executed the following command:
sudo amixer cset numid=3 2
In the instructions it says that if you are using HDMI choose "2".
When I executed the command it just says:
amixer: Control default open error: No such file or directory
First of all: What are you trying to reproduce?
Then... What does it say if you type: ?
amixer controls
Also, if you go to /boot/config.txt, what is the value of dtparam=audio ? It should be on.
For more info, maybe check this out: https://elinux.org/R-Pi_Troubleshooting#Sound

Install 'yum' in Centos7 [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed last year.
Improve this question
I've deleted yum from my server and I did wget to download yum again and extract it. In this folder, I have a lot of files:
AUTHORS completion-helper.py Makefile shell.py yumcommands.py
bin COPYING output.py test yum-cron
callback.py docs po TODO yummain.py
ChangeLog etc README utils.py yum.spec
cli.py INSTALL rpmUtils yum yum-updatesd.py
How can I install it?
Another solution to install packages is to use the RPM command. You first need to download the rpm file and then install it.
For more infos: RPM man page
So, to install yum, simply run those two commands:
wget https://dl.fedoraproject.org/pub/epel/7/x86_64/Packages/e/epel-release-7-14.noarch.rpm
rpm -ivh yum-3.4.3-154.el7.centos.noarch.rpm

`which` finds file, but `bash` doesn't [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
I installed Fabric via pip.
Got pip by:
sudo apt-get install python-pip
Got fabric by:
sudo pip install fabric
(It failed when I tried w/out sudo, and warns me about a lack of files in docs or tests).
Now I get the following:
$ which fab
/usr/local/bin/fab
$
$ fab
bash: /usr/bin/fab: No such file or directory
Huh!? I thought which searched the PATH for the resolution that would be used by bash. Am I misunderstanding something? Is Fabric, Pip, or Bash to blame here? How do I fix it?
I know for now I can run /usr/local/bin/fab or:
`which fab` deploy
But I want it to run correctly!
The following will clear where bash thinks fab is located:
hash -d fab
If which fab is in /usr/*local*/bin, but /usr/bin/fab can't be run, I would think of a broken symlink. Or /usr/local/bin/fab is a script that calls /usr/bin/fab (which doesn't exist).
Try file /usr/local/bin/fab.

Resources