Syndicate content

Gnome Keyring stopped working...

At some point in time, I upgraded Ubuntu and my Gnome Keyring stopped working. So each time I do ssh I have to enter the password at the prompt and that's a bit annoying after a while (depends how much I access the servers, obviously.)

I read many threads ZERO of them gave me an answer I want to hear. All of them speak of things that do not make sense in that situation. So I tried to install a brand new clean 14.04 server + ubuntu-desktop and guess what... Gnome Keyring is installed and everything makes me think that is is correctly installed (I get the correct SSH_AUTH_SOCK value) and yet I still get a terminal prompt.

The Actual Proper Solution (for now)

Okay! So it works, but it's annoying. The fact is that at some point I added a new key and could not connect using that key. The reason was because I had too many keys under my ~/.ssh directory.

To paliate to that problem, I decided to add a sub-directory named other_keys and move all my keys in there. At least that fixed the ssh client which then stopped complaining about having too many keys. However, that was not a good solution because the result was that the SSH agent would not be fed those hidden keys.

I moved one of my keys back to ~/.ssh and I get the normal prompt again. Hurray!

What is sad, this far, is that the keys present right under ~/.ssh do work by being added to the ssh-agent without asking me for my passphrase until I try to connect to the remote computer. However, if I try to use ssh-add directly, there seem to be no options to do the same thing from the command line. I will be looking further for that possibility... that way I could just add all the files in my sub-directory.


There is a way to define many IdentityFile entries in your ~/.ssh/config file, however that will eventually make ssh fail, just the same as when you have too many keys in ~/.ssh. I guess that the ssh developer really very strongly believe that you should have a single key. Only, if your one key gets compromised, then all the computers with that one .pub key are compromised at once. Just like using the same password for Facebook and your bank account. (Hint Hint!)


Just in case, I tried manually and it works just fine. If you want to make sure that the SSH agent works on your system, then do this:

ssh-add ~/.ssh/my_private_key
Password: ****
ssh-add -l

This will add the key to the keyring. After that you can use your SSH key without having to re-enter the password each time. The -l (lowercase L like list) command line option lists the various key that were loaded to the keyring thus far.

Kill Input /dev/tty

This one solution, I do not like because there is really NO reason why SSH would react differently today than it was before so why should I start it in a different way. Also that's kind of the only place where I found that solution:

alias ssh="setsid ssh"

Plus it should have been there before and I had never heard of setsid.

Not only that, it makes absolutely no sense. Although it works as in it opens the popup as expected, once SSH started, you do not have access to the shell since your system disconnected stdin from that software. Again, I do not get the intend of this one!?



Some people have problems when starting their terminal and get an invalid SSH_AUTH_SOCK if defined at all (see Invalid Start Order below).

That has been all good all the time for me. The path does point under:


Exactly as expected.


Invalid Starting Order

It looks like there was a problem with the order in which things got started. I double checked and the necessary patch was installed and thus this is not likely a problem anymore. Using Ctrl-Alt-T to start a terminal, the terminal has the correct variables (SSH_AUTH_SOCK at least) and yet my system still does not automatically call ssh-add.

If you think you have this problem, run this command once in your terminal and try SSH again. If you still see the prompt in your terminal, then it is not doing anything (you probably already have the fix).

gnome-keyring-daemon -s


Syndicate content

Diverse Realty

Diverse Realty Team

Want a New Home?
Want to Sell Your House?

Call Alex at
+1 (916)
220 6482

Alexis Wilke, Realtor
Lic. # 02024063

Cory Marcus, Broker
Lic. # 01079165


Terms of Site Index

Find the page/content you are looking for with our index.

  • Safari
  • games
  • number

    All software make use of numbers. Everything is a number. The most basic number in a computer is 0 or 1. This is called a bit. These are represented with electricity. Although in most cases we see it as 0 - Ground and 1 - Voltage (i.e. 1 volt), the bit representation in software and in hardware may be interpreted either way (i.e. a 0 could mean that the voltage is 1V and not 0V.)

    Combining these zeroes and ones we offer end users to handle much larger numbers. With 8 bits, you can have numbers from 0 to 255 (unsigned) or -128 to +127 (signed.) Now a day, computers can handle a much larger number of bits in one cycle. Most processors use 64 bits but they can calculate numbers on 128, 256, and for some 1024 bits at once. Also with parallelism, the size can be viewed as even larger (i.e. handling a 64 bit number in 1,536 threads like on my old nVidra Quadro 600 is equivalent to one large number of 98,304 bits! That would be 2 power 98,304 possibilitie or about 2.8359e+29592 in decimal.)

    Integers are easy to handle. Although when working on math problems you generally see the set of avaialble numbers as equivalent to N although mathematicians know that computers can really only handle a limited set of numbers. For example, on a 64 bit computer, the usual range is -9223372036854775808 to 9223372036854775807, This is generally enough although at times some equations have to be reworked to avoid really large or small intermediate numbers that work fine in math equations, but not so well on computers.

    Now, math also includes other sets of numbers such as D, R, and C. Computers do not offer any way to represent numbers in R or C but they can offer D to some extend. These numbers are called floating point numbers because we do math using an exponent. The exponent makes the decimal point "float" in any location as the number used for the exponent offers. Using a 64 bit floating point, you can have positive and negative numbers with precision varing betwee 10-308 and 10+308. This includes a positive zero (+0) and a negative zero (-0), which is import in a few cases (although +0 = -0 is true, you can get the sign of a number and distinguish both zeroes). Note that at first decimal numbers were going to also have a positive and negative zero, but it was instead decided to have one more negative number (remember, with 8 bits we have signed numbers from -128 to +127, this is because in the positive numbers we have a 0 which we don't have in the negative numbers.)

  • prompt
  • scanner