Error opening terminal linux

Error opening terminal when running IFL, TBIView, or OSD Tool Script from Linux Distribution

Image for Linux (IFL), TBIView, or the OSD Tool Script will not run on a Linux distribution, producing an error message similar to the following:

Error opening terminal: linux

Note that depending on what type of terminal is in use, the terminal type in the error message may also be xterm, Eterm, rxvt, or any other terminal type being used. Also note that this problem will only occur when attempting to run IFL, TBIView, or the OSD Tool Script from a Linux distribution. It will not occur when running these programs from the IFL Boot Disk.

Starting with the Debian «Squeeze» version of the Debian distribution, as well as some other Debian-based Linux distributions, several symlinks have been removed from the /usr/share/terminfo directory. This causes the affected programs to not be able to find the specific terminfo file they need to open a terminal (such as linux, xterm, Eterm, rxvt, dumb, etc.). This results in the error message shown above, and the affected programs will not be able to run.

As root, create a new symlink by using the sequence of commands shown below for the specific terminal type shown in the error message. Note that there are 3 commands for each terminal type, and they should be executed in the order shown below.

1. For error message «Error opening terminal: linux»

mkdir -p /usr/share/terminfo/l

ln -s /lib/terminfo/l/linux linux

2. For error message «Error opening terminal: xterm»

mkdir -p /usr/share/terminfo/x

ln -s /lib/terminfo/x/xterm xterm

3. For error message «Error opening terminal: rxvt»

mkdir -p /usr/share/terminfo/r

ln -s /lib/terminfo/r/rxvt rxvt

4. For error message «Error opening terminal: dumb»

mkdir -p /usr/share/terminfo/d

ln -s /lib/terminfo/d/dumb dumb

5. For error message «Error opening terminal: Eterm»

mkdir -p /usr/share/terminfo/E

ln -s /lib/terminfo/E/Eterm Eterm

September 1, 2010 Updated: September 9, 2021

Источник

error opening terminal: xterm-256color

I logged into metasploitable from kali linux using SSH.(Windows host) Now I want to access file named config.inc ( /var/www/mutillidae/config.inc ) in metasploitable. I tried opening it using sudo nano /var/www/mutillidae/config.inc command and it showed me an error.

It gave me a warning(terminal is not fully functional). and then opened the file. When I tried to open it using less.

@abhijithpogiri: Don’t comment your own question, but edit your question to improve it by giving details.

1 Answer 1

It seems like you have a problem with the terminal definition.

Try using xterm instead of xterm-256color

or the following terminal setting:

export TERMINFO=/etc/terminfo export TERM=linux 

Also, if you still have problem with nano try using vi which is a simple editor and doesn’t required much from the terminal

sudo vi /var/www/mutillidae/config.inc 

You must log in to answer this question.

Related

Hot Network Questions

Subscribe to RSS

To subscribe to this RSS feed, copy and paste this URL into your RSS reader.

Site design / logo © 2023 Stack Exchange Inc; user contributions licensed under CC BY-SA . rev 2023.7.12.43529

Linux is a registered trademark of Linus Torvalds. UNIX is a registered trademark of The Open Group.
This site is not affiliated with Linus Torvalds or The Open Group in any way.

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.

Источник

Thread: Error opening terminal: xterm.

5 Cups of Ubuntu

Error opening terminal: xterm.

When i type «nano» into the terminal I receive the following message:
Error opening terminal: xterm.

Typing «top» will give this message:
‘xterm’: unknown terminal type.

Word wrap is not working when I push backspace on a multi-line command.

Ctrl+Alt+F6 -> commands work fine.
xterm works fine.
Have tried creating a new user but it has the same problem.
Tried what was suggested here but it doesn’t help.

Any other suggestions out there?

Cookies and cream

Re: Error opening terminal: xterm.

Not all that familiar with the Unity system, but in Systems > Settings > Preferences, which terminal is set as preferred?

5 Cups of Ubuntu

Re: Error opening terminal: xterm.

Just adding to the list of symptoms. When typing «man » The following message will be shown «WARNING: terminal is not fully functional»

I found this command to find out which terminal is preferred:
-ubuntu:~$ gsettings get org.gnome.desktop.default-applications.terminal exec
‘x-terminal-emulator’

Edit: I just changed it to xterm and was about to say I’m happy with that. but It’s hard to copy and paste things to xterm

Cookies and cream

Re: Error opening terminal: xterm.

5 Cups of Ubuntu

Re: Error opening terminal: xterm.

I installed and opened xfce terminal
sudo apt-get install xfce4-terminal

xfce4-terminal
Failed to connect to session manager: Failed to connect to the session manager: SESSION_MANAGER environment variable not defined

xfce4-terminal still opens up but it suffers from the same problems as x-terminal-emulator

Floating Round My Tin Can

Re: Error opening terminal: xterm.

Could you open a terminal run these commands, and post back the results (you can copy/paste the text)?

ls ~/.bash_logout ~/.bashrc ~/.profile diff /etc/skel/.bashrc ~/.bashrc diff /etc/skel/.profile ~/.profile

5 Cups of Ubuntu

Re: Error opening terminal: xterm.

/home/philip/.bash_logout /home/philip/.bashrc /home/philip/.profile

5 Cups of Ubuntu

Re: Error opening terminal: xterm.

Ok I have almost figured this out.

sudo apt-get install rxvt-unicode export TERM=rxvt-unicode

From there on everything works perfectly. My only problem now is that i have to set TERM all the time. How can i set it permanently to rxvt-unicode using either gnome-terminal or xfce4-terminal? . or any other terminal that supports copy n paste

5 Cups of Ubuntu

Re: Error opening terminal: xterm.

sudo apt-get install rxvt-unicode nano ~/.bashrc export TERM=rxvt-unicode

Now you should be able to run x-terminal-emulator or gnome-terminal-emulator and everything should work fine.

I’m not sure if this is just me but if you press ctrl+alt+T and are confronted with the wrong terminal, just open system settings -> keyboard -> shortcuts -> create a custom shortcut with your preferred terminal on ctrl+alt+t. This will override the system shortcut.

• Site Areas
• Settings
• Private Messages
• Subscriptions
• Who’s Online
• Search Forums
• Forums Home
• Forums
• The Ubuntu Forum Community
  1. Ubuntu Official Flavours Support
     1. New to Ubuntu
     2. General Help
     3. Installation & Upgrades
     4. Hardware
     5. Desktop Environments
     6. Networking & Wireless
     7. Multimedia Software
  2. Ubuntu Specialised Support
     1. Ubuntu Development Version
     2. Security
     3. Virtualisation
     4. Ubuntu Servers, Cloud and Juju
        1. Server Platforms
        2. Ubuntu Cloud and Juju
     5. Gaming & Leisure
        1. Emulators
     6. Wine
     7. Development & Programming
        1. Packaging and Compiling Programs
        2. Development CD/DVD Image Testing
        3. Ubuntu Application Development
        4. Ubuntu Dev Link Forum
        5. Programming Talk
        6. Repositories & Backports
           1. Ubuntu Backports
              1. Bug Reports / Support
     8. System76 Support
     9. Apple Hardware Users
  3. Ubuntu Community Discussions
     1. Ubuntu, Linux and OS Chat
        1. Recurring Discussions
        2. Full Circle Magazine
     2. The Cafe
        1. Cafe Games
     3. Market
     4. Mobile Technology Discussions (CLOSED)
     5. Announcements & News
     6. Weekly Newsletter
     7. Membership Applications
     8. The Fridge Discussions
     9. Forum Council Agenda
     10. Forum Feedback & Help
         1. Request a LoCo forum
     11. Resolution Centre
  4. Other Discussion and Support
     1. Other OS Support and Projects
        1. Other Operating Systems
           1. Ubuntu/Debian BASED
           2. Debian
           3. MINT
           4. Arch and derivatives
           5. Fedora/RedHat and derivatives
           6. Mandriva/Mageia
           7. Slackware and derivatives
           8. openSUSE and SUSE Linux Enterprise
           9. Mac OSX
           10. PCLinuxOS
           11. Gentoo and derivatives
           12. Windows
           13. BSD
           14. Any Other OS
     2. Assistive Technology & Accessibility
     3. Art & Design
     4. Education & Science
     5. Documentation and Community Wiki Discussions
     6. Tutorials
        1. Outdated Tutorials & Tips
     7. Ubuntu Women
     8. Ubuntu LoCo Team Forums
        1. Americas LoCo Teams
           1. Argentina Team
              1. Software
              2. Hardware
              3. Comunidad
           2. Arizona Team — US
           3. Arkansas Team — US
           4. Brazil Team
           5. California Team — US
           6. Canada Team
           7. Centroamerica Team
           8. Chile Team
              1. Comunidad
              2. Hardware
              3. Software
              4. Instalaci�n y Actualizaci�n
           9. Colombia Team — Colombia
           10. Georgia Team — US
           11. Illinois Team
           12. Indiana — US
           13. Kentucky Team — US
           14. Maine Team — US
           15. Minnesota Team — US
           16. Mississippi Team — US
           17. Nebraska Team — US
           18. New Mexico Team — US
           19. New York — US
           20. North Carolina Team — US
           21. Ohio Team — US
           22. Oklahoma Team — US
           23. Oregon Team — US
           24. Pennsylvania Team — US
           25. Peru Team
           26. Texas Team — US
           27. Uruguay Team
           28. Utah Team — US
           29. Virginia Team — US
           30. West Virginia Team — US
        2. Asia and Oceania LoCo Teams
           1. Australia Team
           2. Bangladesh Team
           3. Hong Kong Team
           4. Myanmar Team
           5. Philippine Team
           6. Singapore Team
        3. Europe, Middle East, and African (EMEA) LoCo Teams
           1. Albania Team
           2. Catalan Team
           3. Portugal Team
           4. Egypt Team
           5. Georgia Team
           6. Ireland Team — Ireland
           7. Kenyan Team — Kenya
           8. Kurdish Team — Kurdistan
           9. Lebanon Team
           10. Morocco Team
           11. Saudi Arabia Team
           12. Sudan Team
           13. Tunisia Team
        4. Other Forums & Teams
        5. LoCo Archive
           1. Afghanistan Team
           2. Alabama Team — US
           3. Alaska Team — US
           4. Algerian Team
           5. Andhra Pradesh Team — India
           6. Austria Team
           7. Bangalore Team
           8. Bolivia Team
           9. Cameroon Team
           10. Colorado Team — US
           11. Connecticut Team
           12. Costa Rica Team
           13. Delhi Team
           14. Ecuador Team
           15. El Salvador Team
           16. Florida Team — US
           17. Galician LoCo Team
           18. Greek team
           19. Hawaii Team — US
           20. Honduras Team
           21. Idaho Team — US
           22. Iowa Team — US
           23. Jordan Team
           24. Kansas Team — US
           25. Libya Team
           26. Louisiana Team — US
           27. Maryland Team — US
           28. Massachusetts Team
           29. Michigan Team — US
           30. Missouri Team — US
           31. Montana Team — US
           32. Namibia Team
           33. Nevada Team — US
           34. New Hampshire Team — US
           35. New Jersey Team — US
           36. Northeastern Team — US
           37. Panama Team
           38. Paraguay Team
           39. Qatar Team
           40. Quebec Team
           41. Rhode Island Team — US
           42. Senegal Team
           43. South Carolina Team — US
           44. South Dakota Team — US
           45. Switzerland Team
           46. Tamil Team — India
           47. Tennessee Team — US
           48. Trinidad & Tobago Team
           49. Uganda Team
           50. United Kingdom Team
           51. US LoCo Teams
           52. Venezuela Team
           53. Wales Team
           54. Washington DC Team — US
           55. Washington State Team — US
           56. Wisconsin Team
           57. Yemen Team
           58. Za Team — South Africa
           59. Zimbabwe Team

Tags for this Thread

Bookmarks

Bookmarks

Posting Permissions

• You may not post new threads
• You may not post replies
• You may not post attachments
• You may not edit your posts

vBulletin �2000 — 2023, Jelsoft Enterprises Ltd. Ubuntu Logo, Ubuntu and Canonical � Canonical Ltd. Tango Icons � Tango Desktop Project.
User contributions on this site are licensed under the Creative Commons Attribution Share Alike 4.0 International License. For details and our forum data attribution, retention and privacy policy, see here

Источник

Error opening terminal: xterm-256color

When I try to nano something on my server I’m getting this error «Error opening terminal: xterm-256color.» that I’ve never seen before, and on top of that nano used to work fine last week. Even when I use vi, the file will open but I can’t manipulate using normal vi commands. When I press i to activate insert mode and then try to navigate the document, it just types an A or B or something. The only thing that changed is I lost my private key and had to generate a new one, so I had to upload the new public key to my server. Anyone know why this is happening? The server is running Ubuntu 8.04 Hardy. SOLUTION Open Terminal, select from the menu Terminal > Preferences > Settings > Advanced and under Emulation select «Declare terminal as: xterm-color not xterm-256color» Reference: http://ricochen.wordpress.com/2011/07/23/mac-os-x-lion-terminal-color-remote-access-problem-fix/

As of Mac OS X Lion 10.7, Terminal’s default $TERM value is xterm-256color. (Prior to Lion it was xterm-color.) If you’re connecting to a remote host that doesn’t have the necessary terminfo files installed, I recommend you install them. Selecting xterm-color is a workaround, but disables some important enhancements that are new in Lion Terminal. At the very least, you should try using xterm instead of xterm-color to see how that works for you, because xterm-color represents an older branch of xterm that isn’t as capable as modern xterm.

Источник