Kali 2.0 terminal doesn't work











up vote
2
down vote

favorite












(Sorry for language)



I just installed Kali Linux 2.0 on a lenovo z50-70 , just after the installation i opened the terminal (clicking on the terminal icon) but after a bit of loading nothing shows up , i tried re installing gnome and all the needed packets, but nothing changes. i tried to google it and it seems that no one (but me and an online buddy, that also didn't found anything) is actually having some troubles like that



but here comes the interesting thing
I tried to install a different Kali version (32 bits) on a different machine (an Eee pc from asus) and I had the same problem. This thing is literally driving me crazy.



btw I tried all of the following without any results :



apt-get update

apt-get upgrade

apt-get install gnome #it wasn't installed yet

apt-get upgrade gnome-terminal #latest version already installed


update: i installed a new terminal emulator (terminator) , and it works , but i would really prefere to have back my gnome-terminal , because all the applications links are on the gnome terminal ( as nmap and setoolkit , for example) so it would be great also to know if i can change, for example, nmap, to run on the terminator terminal emulator.










share|improve this question
























  • Hi Tommaso, please remove the solution from the question, add an own answer and accept it.
    – bummi
    Jan 4 '16 at 7:49















up vote
2
down vote

favorite












(Sorry for language)



I just installed Kali Linux 2.0 on a lenovo z50-70 , just after the installation i opened the terminal (clicking on the terminal icon) but after a bit of loading nothing shows up , i tried re installing gnome and all the needed packets, but nothing changes. i tried to google it and it seems that no one (but me and an online buddy, that also didn't found anything) is actually having some troubles like that



but here comes the interesting thing
I tried to install a different Kali version (32 bits) on a different machine (an Eee pc from asus) and I had the same problem. This thing is literally driving me crazy.



btw I tried all of the following without any results :



apt-get update

apt-get upgrade

apt-get install gnome #it wasn't installed yet

apt-get upgrade gnome-terminal #latest version already installed


update: i installed a new terminal emulator (terminator) , and it works , but i would really prefere to have back my gnome-terminal , because all the applications links are on the gnome terminal ( as nmap and setoolkit , for example) so it would be great also to know if i can change, for example, nmap, to run on the terminator terminal emulator.










share|improve this question
























  • Hi Tommaso, please remove the solution from the question, add an own answer and accept it.
    – bummi
    Jan 4 '16 at 7:49













up vote
2
down vote

favorite









up vote
2
down vote

favorite











(Sorry for language)



I just installed Kali Linux 2.0 on a lenovo z50-70 , just after the installation i opened the terminal (clicking on the terminal icon) but after a bit of loading nothing shows up , i tried re installing gnome and all the needed packets, but nothing changes. i tried to google it and it seems that no one (but me and an online buddy, that also didn't found anything) is actually having some troubles like that



but here comes the interesting thing
I tried to install a different Kali version (32 bits) on a different machine (an Eee pc from asus) and I had the same problem. This thing is literally driving me crazy.



btw I tried all of the following without any results :



apt-get update

apt-get upgrade

apt-get install gnome #it wasn't installed yet

apt-get upgrade gnome-terminal #latest version already installed


update: i installed a new terminal emulator (terminator) , and it works , but i would really prefere to have back my gnome-terminal , because all the applications links are on the gnome terminal ( as nmap and setoolkit , for example) so it would be great also to know if i can change, for example, nmap, to run on the terminator terminal emulator.










share|improve this question















(Sorry for language)



I just installed Kali Linux 2.0 on a lenovo z50-70 , just after the installation i opened the terminal (clicking on the terminal icon) but after a bit of loading nothing shows up , i tried re installing gnome and all the needed packets, but nothing changes. i tried to google it and it seems that no one (but me and an online buddy, that also didn't found anything) is actually having some troubles like that



but here comes the interesting thing
I tried to install a different Kali version (32 bits) on a different machine (an Eee pc from asus) and I had the same problem. This thing is literally driving me crazy.



btw I tried all of the following without any results :



apt-get update

apt-get upgrade

apt-get install gnome #it wasn't installed yet

apt-get upgrade gnome-terminal #latest version already installed


update: i installed a new terminal emulator (terminator) , and it works , but i would really prefere to have back my gnome-terminal , because all the applications links are on the gnome terminal ( as nmap and setoolkit , for example) so it would be great also to know if i can change, for example, nmap, to run on the terminator terminal emulator.







kali-linux gnome-terminal






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 4 '16 at 7:58









pun

4,80081851




4,80081851










asked Dec 3 '15 at 21:12









Tommaso Ascari

46119




46119












  • Hi Tommaso, please remove the solution from the question, add an own answer and accept it.
    – bummi
    Jan 4 '16 at 7:49


















  • Hi Tommaso, please remove the solution from the question, add an own answer and accept it.
    – bummi
    Jan 4 '16 at 7:49
















Hi Tommaso, please remove the solution from the question, add an own answer and accept it.
– bummi
Jan 4 '16 at 7:49




Hi Tommaso, please remove the solution from the question, add an own answer and accept it.
– bummi
Jan 4 '16 at 7:49










5 Answers
5






active

oldest

votes

















up vote
3
down vote



accepted










After some research i found out that this problem is caused by the selection of c ( untrackable english ) language in the installation process, i fixed everything from the settings, changing the language from c (untrackable english language) to english, and logging out and back in.



now it works fine and the terminal starts without any issues






share|improve this answer

















  • 2




    could you share steps of how to fix the issue?
    – Dennis
    Jul 15 '16 at 7:22


















up vote
1
down vote













You can switch to the virtual terminals using CTRL-ALT-F# (like CTRL-ALT-F1). Once there, you can login and then use cat/head/tail/less to check log files in /var/log to look for errors/issues (or check using the GUI if other parts are working).



F7 will generally get you back to the GUI while 1-6 are generally virtual terminals. In addition, you may want to try re-creating your install media or downloading the ISO again as it's possible there are corruption issues.



In addition, you could try opening gnome-terminal from inside the other terminal to see if any errors/issues are reported to stderr. Finally, try opening gnome-terminal as superuser/root. It's possible it's trying to access files with incorrect or restrictive permissions.






share|improve this answer




























    up vote
    0
    down vote













    dpkg --configure -a


    fixed the problem for me






    share|improve this answer




























      up vote
      0
      down vote













      On my machine:




      apt-get -f install is OK







      share|improve this answer




























        up vote
        -1
        down vote













        apt-get install -y locales locales-all


        solved the issue for me.






        share|improve this answer






















          protected by Community Nov 21 at 22:24



          Thank you for your interest in this question.
          Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



          Would you like to answer one of these unanswered questions instead?














          5 Answers
          5






          active

          oldest

          votes








          5 Answers
          5






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          3
          down vote



          accepted










          After some research i found out that this problem is caused by the selection of c ( untrackable english ) language in the installation process, i fixed everything from the settings, changing the language from c (untrackable english language) to english, and logging out and back in.



          now it works fine and the terminal starts without any issues






          share|improve this answer

















          • 2




            could you share steps of how to fix the issue?
            – Dennis
            Jul 15 '16 at 7:22















          up vote
          3
          down vote



          accepted










          After some research i found out that this problem is caused by the selection of c ( untrackable english ) language in the installation process, i fixed everything from the settings, changing the language from c (untrackable english language) to english, and logging out and back in.



          now it works fine and the terminal starts without any issues






          share|improve this answer

















          • 2




            could you share steps of how to fix the issue?
            – Dennis
            Jul 15 '16 at 7:22













          up vote
          3
          down vote



          accepted







          up vote
          3
          down vote



          accepted






          After some research i found out that this problem is caused by the selection of c ( untrackable english ) language in the installation process, i fixed everything from the settings, changing the language from c (untrackable english language) to english, and logging out and back in.



          now it works fine and the terminal starts without any issues






          share|improve this answer












          After some research i found out that this problem is caused by the selection of c ( untrackable english ) language in the installation process, i fixed everything from the settings, changing the language from c (untrackable english language) to english, and logging out and back in.



          now it works fine and the terminal starts without any issues







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Jan 4 '16 at 7:55









          Tommaso Ascari

          46119




          46119








          • 2




            could you share steps of how to fix the issue?
            – Dennis
            Jul 15 '16 at 7:22














          • 2




            could you share steps of how to fix the issue?
            – Dennis
            Jul 15 '16 at 7:22








          2




          2




          could you share steps of how to fix the issue?
          – Dennis
          Jul 15 '16 at 7:22




          could you share steps of how to fix the issue?
          – Dennis
          Jul 15 '16 at 7:22












          up vote
          1
          down vote













          You can switch to the virtual terminals using CTRL-ALT-F# (like CTRL-ALT-F1). Once there, you can login and then use cat/head/tail/less to check log files in /var/log to look for errors/issues (or check using the GUI if other parts are working).



          F7 will generally get you back to the GUI while 1-6 are generally virtual terminals. In addition, you may want to try re-creating your install media or downloading the ISO again as it's possible there are corruption issues.



          In addition, you could try opening gnome-terminal from inside the other terminal to see if any errors/issues are reported to stderr. Finally, try opening gnome-terminal as superuser/root. It's possible it's trying to access files with incorrect or restrictive permissions.






          share|improve this answer

























            up vote
            1
            down vote













            You can switch to the virtual terminals using CTRL-ALT-F# (like CTRL-ALT-F1). Once there, you can login and then use cat/head/tail/less to check log files in /var/log to look for errors/issues (or check using the GUI if other parts are working).



            F7 will generally get you back to the GUI while 1-6 are generally virtual terminals. In addition, you may want to try re-creating your install media or downloading the ISO again as it's possible there are corruption issues.



            In addition, you could try opening gnome-terminal from inside the other terminal to see if any errors/issues are reported to stderr. Finally, try opening gnome-terminal as superuser/root. It's possible it's trying to access files with incorrect or restrictive permissions.






            share|improve this answer























              up vote
              1
              down vote










              up vote
              1
              down vote









              You can switch to the virtual terminals using CTRL-ALT-F# (like CTRL-ALT-F1). Once there, you can login and then use cat/head/tail/less to check log files in /var/log to look for errors/issues (or check using the GUI if other parts are working).



              F7 will generally get you back to the GUI while 1-6 are generally virtual terminals. In addition, you may want to try re-creating your install media or downloading the ISO again as it's possible there are corruption issues.



              In addition, you could try opening gnome-terminal from inside the other terminal to see if any errors/issues are reported to stderr. Finally, try opening gnome-terminal as superuser/root. It's possible it's trying to access files with incorrect or restrictive permissions.






              share|improve this answer












              You can switch to the virtual terminals using CTRL-ALT-F# (like CTRL-ALT-F1). Once there, you can login and then use cat/head/tail/less to check log files in /var/log to look for errors/issues (or check using the GUI if other parts are working).



              F7 will generally get you back to the GUI while 1-6 are generally virtual terminals. In addition, you may want to try re-creating your install media or downloading the ISO again as it's possible there are corruption issues.



              In addition, you could try opening gnome-terminal from inside the other terminal to see if any errors/issues are reported to stderr. Finally, try opening gnome-terminal as superuser/root. It's possible it's trying to access files with incorrect or restrictive permissions.







              share|improve this answer












              share|improve this answer



              share|improve this answer










              answered Jan 4 '16 at 4:35









              nijave

              248212




              248212






















                  up vote
                  0
                  down vote













                  dpkg --configure -a


                  fixed the problem for me






                  share|improve this answer

























                    up vote
                    0
                    down vote













                    dpkg --configure -a


                    fixed the problem for me






                    share|improve this answer























                      up vote
                      0
                      down vote










                      up vote
                      0
                      down vote









                      dpkg --configure -a


                      fixed the problem for me






                      share|improve this answer












                      dpkg --configure -a


                      fixed the problem for me







                      share|improve this answer












                      share|improve this answer



                      share|improve this answer










                      answered Jan 13 at 1:42









                      Evan Levy

                      11




                      11






















                          up vote
                          0
                          down vote













                          On my machine:




                          apt-get -f install is OK







                          share|improve this answer

























                            up vote
                            0
                            down vote













                            On my machine:




                            apt-get -f install is OK







                            share|improve this answer























                              up vote
                              0
                              down vote










                              up vote
                              0
                              down vote









                              On my machine:




                              apt-get -f install is OK







                              share|improve this answer












                              On my machine:




                              apt-get -f install is OK








                              share|improve this answer












                              share|improve this answer



                              share|improve this answer










                              answered Sep 28 at 12:21









                              Mr.Michael

                              1




                              1






















                                  up vote
                                  -1
                                  down vote













                                  apt-get install -y locales locales-all


                                  solved the issue for me.






                                  share|improve this answer



























                                    up vote
                                    -1
                                    down vote













                                    apt-get install -y locales locales-all


                                    solved the issue for me.






                                    share|improve this answer

























                                      up vote
                                      -1
                                      down vote










                                      up vote
                                      -1
                                      down vote









                                      apt-get install -y locales locales-all


                                      solved the issue for me.






                                      share|improve this answer














                                      apt-get install -y locales locales-all


                                      solved the issue for me.







                                      share|improve this answer














                                      share|improve this answer



                                      share|improve this answer








                                      edited Jul 16 at 0:23









                                      robinCTS

                                      3,83241527




                                      3,83241527










                                      answered Jul 15 at 23:10









                                      MatiasK

                                      1




                                      1

















                                          protected by Community Nov 21 at 22:24



                                          Thank you for your interest in this question.
                                          Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



                                          Would you like to answer one of these unanswered questions instead?



                                          Popular posts from this blog

                                          AnyDesk - Fatal Program Failure

                                          How to calibrate 16:9 built-in touch-screen to a 4:3 resolution?

                                          QoS: MAC-Priority for clients behind a repeater