I faced the following error/message in Ubuntu 14.04 LTS while updating my softwares through apt-get command:
The following packages have been kept back:
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
After some googling and reading some posts which were either inappropriate or risky/dangerous, I came up with the following solution that works every time and is safe.
Continue reading Kept back packages in apt-get
Few days back I updated my Xcode and today when I opened my IDE to start coding, I realized the IDE is not recognising Git on my computer, so I tried to run git in terminal:
and I got the following error:
Agreeing to the Xcode/iOS license requires admin privileges, please re-run as root via sudo.
so I search internet and I found Continue reading Git error after updating Xcode
There is an annoying error which you get when you want to connect to the same IP via SSH but the server authentication key has been changed and you computer does not accept the risk to connect with a key other than the one you have used before.
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the RSA host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
Please contact your system administrator.
Add correct host key in /home/user/.ssh/known_hosts to get rid of this message.
Offending key in /home/user/.ssh/known_hosts:1
RSA host key for ras.mydomain.com has changed and you have requested strict checking.
Host key verification failed.
This can happen when you install a new OS on the server (or what ever you are trying to connect with via SSH) or if you have completely change the device on the other end (which is also the same case as changing the OS). This error is basically for your own security and safety but it annoys anyway 😀
In this article i’m going to explain few ways to resolve the issue:
Continue reading SSH “Host key verification failed” error
I had this issue for my Ubuntu and Pidora, so in this article you can have both solutions:
The problem I had was to add a user on an Ubuntu 14.04 at my work, so that someone else from the company can help me do some basic maintenance of the system (it was requested by my employee!), so this is how I did it after creating a user (new_user):
gpasswd -a new_user sudo
This command will add the user new_user to the group sudo.
I was working with Pidora (which is a Fedora remix for Raspberry Pi) and I was about to run a command using sudo that I faced the following error:
[NixSOS@pidora ~]$ sudo iptables -L -n
[sudo] password for NixSOS:
NixSOS is not in the sudoers file. This incident will be reported.
and I was confused for a while and then I searched for a way to add my user in the “sudoers file” and I’m going to explain how to add a user or a group to sudoers file. This should work all major linux distributions.
Continue reading Add user or group to sudoers file
During installing Ubuntu 12.04.2 LTS on an Acer laptop I got the following error:
ubi-partman failed with exit code 10
the error message had three buttons and the “continue” button was letting me proceed the installation progress to select date and other stuff, but before selecting the partition I was stock ! After few hours searching and reading blogs I found a clue but there was no specific solution for it, so I decided to write this article.
The problem occurs when the Ubuntu installer wants to check the HDD (Hard Drive Disk) but it was failing each and every time. The solution I found was in configuring the live disk before loading. Follow the following steps:
Continue reading “ubi-partman failed with exit code 10” error during Ubuntu 12.04.* resolution
Q: Why do I receive this error “Error getting a Request Token: Bad Request” when I try to add Online Account to my Linux?
A: This Error pops up when your computer time is not acceptable by Google server. This issue can be solved by setting your computers time and region.
In below you can see the link of RedHat Bugzilla post about such a problem.: