Kubuntu 16.10 - wifi stuck on 'waiting for authorization'











up vote
1
down vote

favorite
1












It used to work but I guess one of the updates broke it. I can connect to the wifi on my phone and other OS's. Unsure of what would cause this. I have tried deleting the profile for each connection and re-entering passwords but nothing. IF I remove passwords for the connections it will work.










share|improve this question






















  • Recently I had a similar problem. I had disabled WMM on the router and this caused the problem. There was some info about it in dmesg. Try to sign into the network and then check dmesg for any new info. If you don't find any useful info, please post the info described here: askubuntu.com/questions/425155/… thanks!
    – mchid
    Jan 9 '17 at 19:59










  • I have WMM enabled. I have this error "ADDRCONF(NETDEV_UP): wlp3s0: link is not ready" when I run dmesg
    – Derek
    Jan 9 '17 at 23:51










  • Okay, just follow the instructions outlined in the following link to provided the information needed to diagnose the issue please: askubuntu.com/a/425205/167115 thanks!
    – mchid
    Jan 10 '17 at 13:53















up vote
1
down vote

favorite
1












It used to work but I guess one of the updates broke it. I can connect to the wifi on my phone and other OS's. Unsure of what would cause this. I have tried deleting the profile for each connection and re-entering passwords but nothing. IF I remove passwords for the connections it will work.










share|improve this question






















  • Recently I had a similar problem. I had disabled WMM on the router and this caused the problem. There was some info about it in dmesg. Try to sign into the network and then check dmesg for any new info. If you don't find any useful info, please post the info described here: askubuntu.com/questions/425155/… thanks!
    – mchid
    Jan 9 '17 at 19:59










  • I have WMM enabled. I have this error "ADDRCONF(NETDEV_UP): wlp3s0: link is not ready" when I run dmesg
    – Derek
    Jan 9 '17 at 23:51










  • Okay, just follow the instructions outlined in the following link to provided the information needed to diagnose the issue please: askubuntu.com/a/425205/167115 thanks!
    – mchid
    Jan 10 '17 at 13:53













up vote
1
down vote

favorite
1









up vote
1
down vote

favorite
1






1





It used to work but I guess one of the updates broke it. I can connect to the wifi on my phone and other OS's. Unsure of what would cause this. I have tried deleting the profile for each connection and re-entering passwords but nothing. IF I remove passwords for the connections it will work.










share|improve this question













It used to work but I guess one of the updates broke it. I can connect to the wifi on my phone and other OS's. Unsure of what would cause this. I have tried deleting the profile for each connection and re-entering passwords but nothing. IF I remove passwords for the connections it will work.







networking wireless kubuntu






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Jan 9 '17 at 19:50









Derek

1118




1118












  • Recently I had a similar problem. I had disabled WMM on the router and this caused the problem. There was some info about it in dmesg. Try to sign into the network and then check dmesg for any new info. If you don't find any useful info, please post the info described here: askubuntu.com/questions/425155/… thanks!
    – mchid
    Jan 9 '17 at 19:59










  • I have WMM enabled. I have this error "ADDRCONF(NETDEV_UP): wlp3s0: link is not ready" when I run dmesg
    – Derek
    Jan 9 '17 at 23:51










  • Okay, just follow the instructions outlined in the following link to provided the information needed to diagnose the issue please: askubuntu.com/a/425205/167115 thanks!
    – mchid
    Jan 10 '17 at 13:53


















  • Recently I had a similar problem. I had disabled WMM on the router and this caused the problem. There was some info about it in dmesg. Try to sign into the network and then check dmesg for any new info. If you don't find any useful info, please post the info described here: askubuntu.com/questions/425155/… thanks!
    – mchid
    Jan 9 '17 at 19:59










  • I have WMM enabled. I have this error "ADDRCONF(NETDEV_UP): wlp3s0: link is not ready" when I run dmesg
    – Derek
    Jan 9 '17 at 23:51










  • Okay, just follow the instructions outlined in the following link to provided the information needed to diagnose the issue please: askubuntu.com/a/425205/167115 thanks!
    – mchid
    Jan 10 '17 at 13:53
















Recently I had a similar problem. I had disabled WMM on the router and this caused the problem. There was some info about it in dmesg. Try to sign into the network and then check dmesg for any new info. If you don't find any useful info, please post the info described here: askubuntu.com/questions/425155/… thanks!
– mchid
Jan 9 '17 at 19:59




Recently I had a similar problem. I had disabled WMM on the router and this caused the problem. There was some info about it in dmesg. Try to sign into the network and then check dmesg for any new info. If you don't find any useful info, please post the info described here: askubuntu.com/questions/425155/… thanks!
– mchid
Jan 9 '17 at 19:59












I have WMM enabled. I have this error "ADDRCONF(NETDEV_UP): wlp3s0: link is not ready" when I run dmesg
– Derek
Jan 9 '17 at 23:51




I have WMM enabled. I have this error "ADDRCONF(NETDEV_UP): wlp3s0: link is not ready" when I run dmesg
– Derek
Jan 9 '17 at 23:51












Okay, just follow the instructions outlined in the following link to provided the information needed to diagnose the issue please: askubuntu.com/a/425205/167115 thanks!
– mchid
Jan 10 '17 at 13:53




Okay, just follow the instructions outlined in the following link to provided the information needed to diagnose the issue please: askubuntu.com/a/425205/167115 thanks!
– mchid
Jan 10 '17 at 13:53










2 Answers
2






active

oldest

votes

















up vote
3
down vote













Try this if you have network-manager enabled :



sudo nmcli dev wifi 


to find your wifi ssid and



sudo nmcli dev wifi connect <your ssid> password <your pass>


Looks like network-manager is waiting for root permission.






share|improve this answer























  • It worked! Thanks, although the only bad thing is that, in your bash history the wifi password, will remain visible.
    – Edenshaw
    Nov 27 '17 at 12:44




















up vote
1
down vote













If you don't want your password to appear in your history just leave out the password part and add the
-a option and it will ask for it after you hit enter:



 sudo nmcli -a dev wifi connect <your ssid>


From man nmcli



 -a | --ask    When using this option nmcli will stop and ask for any missing 
required arguments, so do not use this option for non-interactive purposes like
scripts. This option controls, for example, whether you will be prompted for a
password if it is required for connecting to a network.





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',
    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%2f869955%2fkubuntu-16-10-wifi-stuck-on-waiting-for-authorization%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    3
    down vote













    Try this if you have network-manager enabled :



    sudo nmcli dev wifi 


    to find your wifi ssid and



    sudo nmcli dev wifi connect <your ssid> password <your pass>


    Looks like network-manager is waiting for root permission.






    share|improve this answer























    • It worked! Thanks, although the only bad thing is that, in your bash history the wifi password, will remain visible.
      – Edenshaw
      Nov 27 '17 at 12:44

















    up vote
    3
    down vote













    Try this if you have network-manager enabled :



    sudo nmcli dev wifi 


    to find your wifi ssid and



    sudo nmcli dev wifi connect <your ssid> password <your pass>


    Looks like network-manager is waiting for root permission.






    share|improve this answer























    • It worked! Thanks, although the only bad thing is that, in your bash history the wifi password, will remain visible.
      – Edenshaw
      Nov 27 '17 at 12:44















    up vote
    3
    down vote










    up vote
    3
    down vote









    Try this if you have network-manager enabled :



    sudo nmcli dev wifi 


    to find your wifi ssid and



    sudo nmcli dev wifi connect <your ssid> password <your pass>


    Looks like network-manager is waiting for root permission.






    share|improve this answer














    Try this if you have network-manager enabled :



    sudo nmcli dev wifi 


    to find your wifi ssid and



    sudo nmcli dev wifi connect <your ssid> password <your pass>


    Looks like network-manager is waiting for root permission.







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Dec 2 at 21:08









    abu_bua

    3,16081023




    3,16081023










    answered Apr 21 '17 at 19:38









    user3545361

    313




    313












    • It worked! Thanks, although the only bad thing is that, in your bash history the wifi password, will remain visible.
      – Edenshaw
      Nov 27 '17 at 12:44




















    • It worked! Thanks, although the only bad thing is that, in your bash history the wifi password, will remain visible.
      – Edenshaw
      Nov 27 '17 at 12:44


















    It worked! Thanks, although the only bad thing is that, in your bash history the wifi password, will remain visible.
    – Edenshaw
    Nov 27 '17 at 12:44






    It worked! Thanks, although the only bad thing is that, in your bash history the wifi password, will remain visible.
    – Edenshaw
    Nov 27 '17 at 12:44














    up vote
    1
    down vote













    If you don't want your password to appear in your history just leave out the password part and add the
    -a option and it will ask for it after you hit enter:



     sudo nmcli -a dev wifi connect <your ssid>


    From man nmcli



     -a | --ask    When using this option nmcli will stop and ask for any missing 
    required arguments, so do not use this option for non-interactive purposes like
    scripts. This option controls, for example, whether you will be prompted for a
    password if it is required for connecting to a network.





    share|improve this answer



























      up vote
      1
      down vote













      If you don't want your password to appear in your history just leave out the password part and add the
      -a option and it will ask for it after you hit enter:



       sudo nmcli -a dev wifi connect <your ssid>


      From man nmcli



       -a | --ask    When using this option nmcli will stop and ask for any missing 
      required arguments, so do not use this option for non-interactive purposes like
      scripts. This option controls, for example, whether you will be prompted for a
      password if it is required for connecting to a network.





      share|improve this answer

























        up vote
        1
        down vote










        up vote
        1
        down vote









        If you don't want your password to appear in your history just leave out the password part and add the
        -a option and it will ask for it after you hit enter:



         sudo nmcli -a dev wifi connect <your ssid>


        From man nmcli



         -a | --ask    When using this option nmcli will stop and ask for any missing 
        required arguments, so do not use this option for non-interactive purposes like
        scripts. This option controls, for example, whether you will be prompted for a
        password if it is required for connecting to a network.





        share|improve this answer














        If you don't want your password to appear in your history just leave out the password part and add the
        -a option and it will ask for it after you hit enter:



         sudo nmcli -a dev wifi connect <your ssid>


        From man nmcli



         -a | --ask    When using this option nmcli will stop and ask for any missing 
        required arguments, so do not use this option for non-interactive purposes like
        scripts. This option controls, for example, whether you will be prompted for a
        password if it is required for connecting to a network.






        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Dec 2 at 21:19









        abu_bua

        3,16081023




        3,16081023










        answered Dec 2 at 20:41









        Joseph Johnson

        112




        112






























            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.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • 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%2f869955%2fkubuntu-16-10-wifi-stuck-on-waiting-for-authorization%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

            flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

            Mangá

             ⁒  ․,‪⁊‑⁙ ⁖, ⁇‒※‌, †,⁖‗‌⁝    ‾‸⁘,‖⁔⁣,⁂‾
”‑,‥–,‬ ,⁀‹⁋‴⁑ ‒ ,‴⁋”‼ ⁨,‷⁔„ ‰′,‐‚ ‥‡‎“‷⁃⁨⁅⁣,⁔
⁇‘⁔⁡⁏⁌⁡‿‶‏⁨ ⁣⁕⁖⁨⁩⁥‽⁀  ‴‬⁜‟ ⁃‣‧⁕‮ …‍⁨‴ ⁩,⁚⁖‫ ,‵ ⁀,‮⁝‣‣ ⁑  ⁂– ․, ‾‽ ‏⁁“⁗‸ ‾… ‹‡⁌⁎‸‘ ‡⁏⁌‪ ‵⁛ ‎⁨ ―⁦⁤⁄⁕