“Enter password to unlock the private key” on 18.04 when no password has been set












0















I worked on a project without problem but since I upgraded to 18.04, when I try to use git it prompts a pop-up reading "Enter password to unlock the private key. An application wants access to the private key 'loke@computer', but it is locked".



The problem is that my ssh key doesn't have a password. I can cat it or open it in gedit for instance without my root password.



I still tried using my root password in the pop up, as well as leaving it blank, clicking cancel and trying other passwords but nothing is working and I still can't use git.



I tried this but the first command gave me this error:




Error setting value: Can't overwrite existing read-only value: Value
for `/apps/gnome-keyring/daemon-components/ssh' set in a read-only
source at the front of your configuration path




and the second command didn't return anything but didn't change my situation either.



So far all the solutions I saw about closing this pop up is to delete your ssh key password, but what do I do if I don't have one to begin with?










share|improve this question



























    0















    I worked on a project without problem but since I upgraded to 18.04, when I try to use git it prompts a pop-up reading "Enter password to unlock the private key. An application wants access to the private key 'loke@computer', but it is locked".



    The problem is that my ssh key doesn't have a password. I can cat it or open it in gedit for instance without my root password.



    I still tried using my root password in the pop up, as well as leaving it blank, clicking cancel and trying other passwords but nothing is working and I still can't use git.



    I tried this but the first command gave me this error:




    Error setting value: Can't overwrite existing read-only value: Value
    for `/apps/gnome-keyring/daemon-components/ssh' set in a read-only
    source at the front of your configuration path




    and the second command didn't return anything but didn't change my situation either.



    So far all the solutions I saw about closing this pop up is to delete your ssh key password, but what do I do if I don't have one to begin with?










    share|improve this question

























      0












      0








      0


      0






      I worked on a project without problem but since I upgraded to 18.04, when I try to use git it prompts a pop-up reading "Enter password to unlock the private key. An application wants access to the private key 'loke@computer', but it is locked".



      The problem is that my ssh key doesn't have a password. I can cat it or open it in gedit for instance without my root password.



      I still tried using my root password in the pop up, as well as leaving it blank, clicking cancel and trying other passwords but nothing is working and I still can't use git.



      I tried this but the first command gave me this error:




      Error setting value: Can't overwrite existing read-only value: Value
      for `/apps/gnome-keyring/daemon-components/ssh' set in a read-only
      source at the front of your configuration path




      and the second command didn't return anything but didn't change my situation either.



      So far all the solutions I saw about closing this pop up is to delete your ssh key password, but what do I do if I don't have one to begin with?










      share|improve this question














      I worked on a project without problem but since I upgraded to 18.04, when I try to use git it prompts a pop-up reading "Enter password to unlock the private key. An application wants access to the private key 'loke@computer', but it is locked".



      The problem is that my ssh key doesn't have a password. I can cat it or open it in gedit for instance without my root password.



      I still tried using my root password in the pop up, as well as leaving it blank, clicking cancel and trying other passwords but nothing is working and I still can't use git.



      I tried this but the first command gave me this error:




      Error setting value: Can't overwrite existing read-only value: Value
      for `/apps/gnome-keyring/daemon-components/ssh' set in a read-only
      source at the front of your configuration path




      and the second command didn't return anything but didn't change my situation either.



      So far all the solutions I saw about closing this pop up is to delete your ssh key password, but what do I do if I don't have one to begin with?







      ssh login password git






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Mar 14 at 7:20









      LokeLoke

      114




      114






















          1 Answer
          1






          active

          oldest

          votes


















          1














          As I couldn't find a fix for this I decided to go around it by replacing my ssh keys altogether, and my problem disappeared.



          I created a new set of keys, overriding the old ones, and uploaded those to my BitBucket, and when I tried again the password prompt didn't appear.



          So it definitely looks like a bug, as neither the old keys nor the new ones had a password, and yet they behaved differently?



          Note: in the Password and Keys settings, when I clicked Change Passphrase on the old keys it also asked for a password which didn't exist, whereas on the new keys it's just asking me if I want to set a new password.






          share|improve this answer

























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "89"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1125527%2fenter-password-to-unlock-the-private-key-on-18-04-when-no-password-has-been-se%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            1














            As I couldn't find a fix for this I decided to go around it by replacing my ssh keys altogether, and my problem disappeared.



            I created a new set of keys, overriding the old ones, and uploaded those to my BitBucket, and when I tried again the password prompt didn't appear.



            So it definitely looks like a bug, as neither the old keys nor the new ones had a password, and yet they behaved differently?



            Note: in the Password and Keys settings, when I clicked Change Passphrase on the old keys it also asked for a password which didn't exist, whereas on the new keys it's just asking me if I want to set a new password.






            share|improve this answer






























              1














              As I couldn't find a fix for this I decided to go around it by replacing my ssh keys altogether, and my problem disappeared.



              I created a new set of keys, overriding the old ones, and uploaded those to my BitBucket, and when I tried again the password prompt didn't appear.



              So it definitely looks like a bug, as neither the old keys nor the new ones had a password, and yet they behaved differently?



              Note: in the Password and Keys settings, when I clicked Change Passphrase on the old keys it also asked for a password which didn't exist, whereas on the new keys it's just asking me if I want to set a new password.






              share|improve this answer




























                1












                1








                1







                As I couldn't find a fix for this I decided to go around it by replacing my ssh keys altogether, and my problem disappeared.



                I created a new set of keys, overriding the old ones, and uploaded those to my BitBucket, and when I tried again the password prompt didn't appear.



                So it definitely looks like a bug, as neither the old keys nor the new ones had a password, and yet they behaved differently?



                Note: in the Password and Keys settings, when I clicked Change Passphrase on the old keys it also asked for a password which didn't exist, whereas on the new keys it's just asking me if I want to set a new password.






                share|improve this answer















                As I couldn't find a fix for this I decided to go around it by replacing my ssh keys altogether, and my problem disappeared.



                I created a new set of keys, overriding the old ones, and uploaded those to my BitBucket, and when I tried again the password prompt didn't appear.



                So it definitely looks like a bug, as neither the old keys nor the new ones had a password, and yet they behaved differently?



                Note: in the Password and Keys settings, when I clicked Change Passphrase on the old keys it also asked for a password which didn't exist, whereas on the new keys it's just asking me if I want to set a new password.







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Mar 14 at 8:25

























                answered Mar 14 at 8:11









                LokeLoke

                114




                114






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Ask Ubuntu!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1125527%2fenter-password-to-unlock-the-private-key-on-18-04-when-no-password-has-been-se%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    數位音樂下載

                    When can things happen in Etherscan, such as the picture below?

                    格利澤436b