Alsamixer Error Opening Terminal Unknown
Contents |
2010-04-08 04:52:01 synthead Member From: Seattle Registered: 2006-05-09 Posts: 1,326 [solved] Error opening terminal: unknown. [max@gayforceone jornadalin]$ htop Error opening terminal: unknown.What's
Error Opening Terminal Unknown Nano
going on here? I've updated my system a few times, error opening terminal unknown docker but that's it. My headless server is doing this too. Last edited by synthead (2010-04-08 ncurses error opening terminal unknown 20:35:12) Touch my kernel Offline #2 2010-04-08 05:55:53 pseudonomous Member Registered: 2008-04-23 Posts: 349 Re: [solved] Error opening terminal: unknown. what $TERM are you trying
Error Opening Terminal Unknown Nano Docker
to run htop in?Edit:I've got to sleep but here are some ideas that occur to me (htop is working fine on my box), but maybe:1) TERM isn't set or is set to term type that htop can't deal with, htop should be able to deal with "TERM=xterm", also I know it
Error Opening Terminal Unknown Htop
handles "linux" and "screen.linux", because I just started htop in each of those settings.2) Permissions on the /dev if you're trying to run htop from a tty, various problems with allocating terminals can occur if something screwy happens, like you mount / read-only, is / mounted read-only? Last edited by pseudonomous (2010-04-08 06:02:16) ... imagine I'm making this argument without referencing cartoons. Offline #3 2010-04-08 12:05:31 synthead Member From: Seattle Registered: 2006-05-09 Posts: 1,326 Re: [solved] Error opening terminal: unknown. This is from XFCE's terminal. If I run xterm and run htop out of it, it works. htop isn't the only app that is complaining about the terminal right now though Example::: Starting full system upgrade... resolving dependencies... looking for inter-conflicts... Targets (9): dbus-python-0.83.1-1 feh-1.4.2-2 grep-2.6.3-1 jack-0.118.0-2 libmodplug-0.8.8-1 pixman-0.18.0-1 vte-0.24.0-2 xorg-xinit-1.2.1-1 youtube-dl-2010.04.04-1 Total Download Size: 1.33 MB Total Installed Size: 7.99 MB Proceed with installation? [Y/n] :: Retrieving packages from
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or ssh error opening terminal unknown posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss
Error Opening Terminal Linux
Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes error opening terminal xterm a minute: Sign up Running nano in docker container up vote 58 down vote favorite 18 I open an interactive shell into a docker container like so sudo docker exec -t -i {container_name} bash So far so good but trying https://bbs.archlinux.org/viewtopic.php?id=94780 to run nano results in: Error opening terminal: unknown. docker share|improve this question edited Jan 7 '15 at 18:43 sjagr 9,52821540 asked Jan 7 '15 at 18:33 Myles McDonnell 5,07132549 Which container is this? also what does your PATH variable look like? –Usman Ismail Jan 7 '15 at 18:57 add a comment| 4 Answers 4 active oldest votes up vote 102 down vote accepted I think this can be related with Docker Issue #9299. There are some workarounds commented in http://stackoverflow.com/questions/27826241/running-nano-in-docker-container that issue: Run the container allocating a pseudo-TTY (option -t). Export environment variable $TERM=xterm in the container's process run in exec (i.e.: export TERM=xterm) share|improve this answer answered Jan 7 '15 at 19:05 Javier Cortejoso 4,25321021 The main issue actually seems to be this one –Pierre de LESPINAY Apr 16 '15 at 14:10 add a comment| up vote 62 down vote Run comand : export TERM=xterm share|improve this answer answered May 22 '15 at 10:32 Naresh Walia 1,0111812 add a comment| up vote 24 down vote You can add ENV TERM xterm to your Dockerfile if you will use the editor regularly. We have that setting in our base container, since we're constantly debugging things with vi/emacs. share|improve this answer answered Jan 7 '15 at 20:18 seanmcl 5,69411226 add a comment| up vote 6 down vote as $TERM was already set to xterm but still not working for me, here is a way that worked: docker exec -it [CONTAINER_ID] /bin/bash -c "export TERM=xterm; exec bash" share|improve this answer answered May 23 at 15:18 pHiL 501510 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign up using Facebook Sign up using Email and Password Post as a guest Name Email Post as a guest Name Email discard By posting your answer, you agree to the privacy policy and terms of service. Not the answer you're looking for? Browse other questions
released I encounter on my terminal the following error: ‘xterm-256color': unknown terminal type when using nano editor or https://www.cloudfarm.it/fix-error-opening-terminal-xterm-256color-unknown-terminal-type/ top command on ubuntu machine for example. On mac's terminal the command: echo $TERM returns xterm-256color To fix this problem you've to modify your~/.profile http://forum.slitaz.org/topic/problem-with-sakura nano ~/.profile add those lines to fix this TERM="xterm"
export TERM Save & quit and restart your terminal.app By CloudFarm Posted in Articles on error opening Oct 31, 2012 Tweet This Facebook LinkedIn Google Print This Listing Author: CloudFarm As Information Technology Officer, Nicola Tonon leads EIUC’s central IT system. As ITO, he is in charge of making sure that all IT strategic initiatives are in line with the EIUC’s mission, culture, and long-term error opening terminal goals. The ITO is responsible for IT-related issues ranging from policy and resource allocation to protocol and organization. Nicola has a deep understanding of the importance technology plays in research and related activities and is committed to finding new ways to support staff and students and endeavours through the use of technology. He works closely with students and staff to deliver programmes and services that enhance teaching, research, and student activities. ← Previous Leave a Reply Cancel reply Your email address will not be published. Required fields are marked * Name * Email * Website Comment You may use these HTML tags and attributes:
Home Contacts Privacy Policy Portfolio Port2 Photography Articles © 2016 CloudFarm, All Rights Reserved. . Back to top ↑
others and get involved in a community group. SliTaz Forum » English Support » Live and installation Problem with sakura (3 posts) (2 voices) Started 2 years ago by yves04 Latest reply from yves04 This topic is not a support question Tags: No tags yet. yves04 offlineMember Hi all Sorry if these questions have already been asked. I've Slitaz 5.0-rc2 on my hard disk and some problems. With sakura if I type clear the answer is --> 'xterm': unknown terminal type if I type alsamixer the answer is --> Error opening terminal: xterm. With Xterm, clear is ok but alsamixer is only black and white When I type xterm in sakura I get --> Warning: locale not supported by Xlib, locale set to C May be I've missed something during the installation. WhateverI'll keep Slitaz on my PC : thanks again for all the developers. Have a nice day Posted 2 years ago # az_ua offlineModerator Thinking, this problem made by my editing of default terminfo in ncurses-common package. Fixing one can create bug in other place, possibility to run apps is in prior, so I will cancel my edits soon. -- Fixed. http://cook.slitaz.org/cooker.cgi?pkg=ncurses-common Even using original /usr/share/terminfo/x/xterm (size 3270 b) not solving alsamixer launched from menu required changing window size to show anything. Upd: this is sakura bug, and fixed by minimizing tazweb window, maybe depends on video driver. Posted 2 years ago # yves04 offlineMember Thanks @az_ua for your quick answer. For a while I've solved the problem by : --> tazpkg remove sakura --> tazpkg -gi aterm --> in $HOME/.config/slitaz/applications.conf replacement TERMINAL="sakura" with TERMINAL="aterm" --> in /usr/bin/terminal just add a line for aterm case $TERMINAL in aterm) OPT_TITLE="-T"; OPT_GEOM="-geometry"; OPT_HELP="-help"; OPT_HOLD="-hold";; Posted 2 years ago # RSS feed for this topic Reply You must log in to post. Copyright © 2016 SliTaz Powered by bbPress - Network: Community Doc Forum Packages Bugs Hg Twitter Facebook Distrowatch Wikipedia Flattr