I find the anti-aliased fonts really difficult to read in the terminal. I have been able to disable anti-aliasing across the board by using the ~/.fonts.cnf file. This makes using everything else much less pleasant, however. Can anyone tell me how to disable anti-aliasing *only in the lxterminal terminal application*? This is on a Raspberry Pi if that makes a difference. I'm using lxterminal, which allows you to set the font and font size but not its aliasing.

I am using .bashrc to execute a python script on system boot:

sudo -u pi python3 /path/to/script.py

and then I add @lxterminal to file /etc/xdg/lxsession/LXDE-pi/autostart to make sure a terminal window is opened on launch. However, when I use ps aux to check all progresses, I found that there's two script.py processes running in the system, even though I call execute the script only once in .bashrc. Having two of the same script running at the same time is causing me troubles. Any help is appreciated.

I wrote a "complex" C program using the ncurses library. It "correctly" runs in a lxterminal or gnome-terminal session; but doesn't run in a "native Linux terminal" session without X started *(obtained both restarting the PC without X or using Ctrl-Alt-F3 terminal).* The problem is that in the "native Linux session" the program doesn't display any windows, it displays only one of the text printed in the third generated window. * I saw that in gnome-terminal the TERM environment variable is set as xterm-256color. In contrast, the native Linux terminal has TERM set as linux. * Then I set TERM in the native Linux terminal using:

export TERM=xterm-256color

When I set TERM as xterm-256color the program runs better and displays an usable interface, but all the chars to construct boxes are substituted by other chars, the vertical line char is substituted by the xchar. * But I thought xterm is for X terminal section then I tried ansi:

export TERM=ansi

With this last setting, the program displays almost nothing as in the case of the native setting. * Using vt100:

export TERM=vt100

The programs runs better, but is displayed in B/W. The same behaviour happens also with the examples released with the ncurses library. Have you some explanation? How do I set the terminal capability in a way I may correctly start my ncurses program? It's possible that I've not set something relevant to terminal (or relevan to ncurses) in the code? **Example** #include static void initGeneralScreen(void); int main() { WINDOW * deskW, * msgW, * otherW; initGeneralScreen(); deskW = newwin(21,80,0,0); wbkgd(deskW, COLOR_PAIR(3)); box(deskW, 0, 0 ); // sets default borders for the window wrefresh( deskW ); // update the terminal screen msgW = newwin(3, 80, 21, 0); wbkgd(msgW, COLOR_PAIR(1)); box(msgW, 0, 0 ); // sets default borders for the window wrefresh(msgW ); // update the terminal screen otherW = newwin(1,78,0,1); wbkgd(otherW, COLOR_PAIR(1)); wrefresh(otherW ); // update the terminal screen mvwprintw(msgW,1,1,"Test ... "); wrefresh(msgW ); // update the terminal screen mvwprintw(otherW,0,0,"Test1"); wrefresh(otherW ); // update the terminal screen wgetch(deskW); delwin( otherW ); delwin( msgW ); delwin( deskW ); endwin(); return 0; } void initGeneralScreen(void) { initscr(); // initialize Ncurses noecho(); // disable echoing of characters on the screen raw(); // keypad(stdscr,TRUE); start_color(); init_pair(1,COLOR_YELLOW | 8, COLOR_BLUE); init_pair(2,COLOR_YELLOW, COLOR_BLUE); init_pair(3,COLOR_WHITE | 8, COLOR_BLACK | 8); } **Notes:** * Kernel

Linux 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

* libncurses.so.5.9

What I mean by that is when a program is running (let's say, telnet), any inputted text gets lost when something is written on the screen. For example, on a chat server, I type *> Hey, I'd like to ask y* Suddenly I receive a string, and now my screen looks like this *> Hey, I'd like to ask yHey, what's up?* I can still continue to write and hit return to successfully send the string, but I'd like to have my input move down like so *Hey, what's up?* *> Hey' I'd like to ask y* How can I do that? I use bash and lxterminal **UPDATE** So here's a quick and dirty solution: anytime your input gets lost, press

^R

to recover it.

I'm new to Linux, ubuntu, and lubuntu so this might be an easy fix. Today I installed Lubuntu 18.04 and suddenly after a reboot the lxterminal won't launch via 'CTRL-ALT-T' anymore. It still works perfectly fine after launching through run or the menu. The shortcut simply doesn't work anymore. I think it broke because I was messing around in 'default applications for lxsession'. I changed around some default programs, such as VLC. I don't think I changed the 'Terminal manager' launch application but even if I did, I'm pretty sure I've reset it to what it was before (lxterminal &) and it still isn't working. Any help would be greatly appreciated.

I've been trying to set transparent terminal background in lxterminal on Arch Linux but with no luck. Setting transparent background in preferences does nothing, so does setting transparent to 1 in lxterminal.conf. I remember it being transparent in Lubuntu 16 but I can't manage to get it on Arch. I know that it was probably fake transparency, but it's sufficient for me.

Is a temrinal emulator process a server? If yes, what is its client(s)? How can I find out its client(s)? Thanks. 1. netstat output contains lxterminal processes. Does that mean that a terminal emulator process is a server based on unix domain socket? $ sudo netstat -ap | grep -i lxterminal [sudo] password for t: unix 2 [ ACC ] STREAM LISTENING 28665 1480/lxterminal /run/user/1000/.lxterminal-socket-:0 unix 3 [ ] STREAM CONNECTED 28663 1480/lxterminal unix 3 [ ] STREAM CONNECTED 28661 1480/lxterminal unix 3 [ ] STREAM CONNECTED 28666 1480/lxterminal 2. A server is always (or usually?) a daemon, so it doesn't have a controlling terminal. lxterminal doesn't have one (?): $ ps aux | grep -i lxterminal t 1480 0.1 0.3 473204 28232 ? Sl Nov21 22:39 lxterminal

**Setup:** - Raspberry Pi running raspbian with a display connected (HDMI) - A continuously running systemd service (daemon) **Goal:** - Starting a new terminal window that's visible on the display - As a proof of concept I would like to run a shell script Running the shell script within the service works without problem but opening a visible window on the display seems to be hard. **The code (daemon)** var process = new Process() { StartInfo = new ProcessStartInfo { FileName = "/bin/bash", Arguments = $"-c \"{Paths.Dotnet} /path/to/app.dll\"", WorkingDirectory = workingDirectory, RedirectStandardOutput = false, UseShellExecute = false, CreateNoWindow = false, WindowStyle = ProcessWindowStyle.Maximized } }; process.Start(); string result = process.StandardOutput.ReadToEnd(); process.WaitForExit(); ** **EDIT** ** Modyfying the arguments to: Arguments = $"-c \"DISPLAY=:0.0 lxterminal -e {Paths.Dotnet} /path/to/app.dll\"" Didn't fix the issue. app.dll is executed but still in the background.

The problem is that I found a solution for my .config/openbox/rc.xml, but not for .config/openbox/autostart.sh. Normally, it's just the command with options like in CLI, but man lxterminal doesn't seem to provide them. Could you briefly tell me the options for the autostart.sh?

I use LXTerminal 0.20. with XFCE 4.12.2 on Linux Mint 18.2 (upgraded from 18.1). When I copy text in some desktop app and paste it into an LXTerminal session, I get 0~ and 1~ prepended and appended, respectively, to the text. So, Hello world becomes 0~Hello World1~ This doesn't happen with XFCE4's "native" terminal app (xfce4-terminal), so **not the same issue as in this question - and not resolved by the answer there**. It also doesn't happen if I copy the text to apps with GUI (i.e. the text itself, in the clipboard, is fine). Why is this happening and what can I do to avoid it?

1. In APUE (see the figure below), how do a terminal emulator process and a window manager (e.g. openbox) process communicate? Is a temrinal emulator process a client of a window manager process, based on Unix domain socket? 2. What is the relation of X server process to a terminal emulator process and a window manager process? Specifically: xlsclients output contains lxterminal. Does that means that a terminal emulator process is a client of X server? $ xlsclients -a | grep -i lxterminal ocean lxterminal xlsclients output doesn't contain a window manager process. Does that means that a window manager process is not a client of X server? $ xlsclients -a | grep -i openbox $

There is a possibility to create named tabs in lxterminal. I got an idea to create a few tabs named like basic, coding, scripting, administration. Is there a way to save it as something like a session and after I close lxterminal, I would have the possibility to open these four tabs?

Can you explain the following lines in the netstat output? Active UNIX domain sockets (w/o servers) Proto RefCnt Flags Type State I-Node Path unix 2 [ ] STREAM CONNECTED 37133819 /tmp/.lxterminal-socket:0-xralf unix 2 [ ] STREAM CONNECTED 37109191 /tmp/.lxterminal-socket:0-xralf

I am trying to understand the differences between logname and LOGNAME from https://unix.stackexchange.com/questions/268378/difference-between-logname-and-logname and https://askubuntu.com/questions/490620/difference-between-logname-and-logname On Lubuntu 18.04, why did I get logname: no login name? t@ocean:/t/t/bkg$ echo $LOGNAME t t@ocean:/t/t/bkg$ logname logname: no login name t@ocean:/t/t/bkg$ su t Password: t@ocean:/t/t/bkg$ logname logname: no login name $ echo $? 1 t@ocean:/t/t/bkg$ cat /var/run/utmp ~~~reboot4.15.0-22-generic��[8Jtty1tty1LOGINJ��[�!�tty7:0t:0��[��5~~~runlevel4.15.0-22-generic��[ t@ocean:/t/t/bkg$ sudo su [sudo] password for t: root@ocean:/tmp/test/bkg# logname logname: no login name root@ocean:/tmp/test/bkg# echo $LOGNAME root What is logname supposed to output? Thanks. From man logname: > logname - print user´s login name > > Print the name of the current user. ---------- To address the comments: $ cat /proc/self/loginuid 4294967295 t@ocean:/t/t/bkg$ grep ":$(id -u):" /etc/passwd t:x:1000:1000:t,,,:/home/t:/bin/bash t@ocean:/t/t/bkg$ tty /dev/pts/8 t@ocean:/t/t/bkg$ w 17:52:08 up 5 days, 6:28, 1 user, load average: 0.39, 0.29, 0.28 USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT t tty7 :0 Wed11 5days 1:47m 6.33s /usr/bin/lxsession -s Lubuntu -e LXDE Mark suspected the cause is that my lxterminal doesn't add an entry to utmp. Pandya: Oh. Seems a bug with entry as you've concluded.

I have the following script in my Arch Linux box: #!/bin/bash xterm -e "sudo pacman -Syu;bash" This will fire up an xterm and run the command sudo pacman -Syu on it. Because of the ;bash part, it will not close the xterm window once the command is finished. This is a command for updating my system and I don't want it to close because I'd like to see the output. Why this will not work with other terminals, and in particular with lxterminal and roxterm (the only others I tried)? The exact same command with lxterminal or roxterm instead of xterm will fire up the terminal and close it immediately after the command is executed.

In gnome-terminal, lxterminal and mlterm under Lubuntu 16.04, when pressing PgUp nothing happens, and the symbol ~ appears when PgDn is pressed, but the information won't scroll up or down. This is not the case for navigators and text editors, where they behave as expected. How can this be changed for a terminal?

While this part of the script works fine: geany & pid=$! ... kill -KILL $pid This, instead, does not. lxterminal & pid=$! ... kill -KILL $pid Looks like a bash process remains in the background, but it is not identified by $pid. How can I get the PID of the terminal window, such that the process can be killed afterwards? Note: I also tried to kill it by its name, but the --title option provokes some kind of conflict with PROMPT_COMMAND.

Is there any way to show a graphic Latex expression in a (textual) terminal? Particularly, can an LXTerminal show the rendering of a Latex equation? Alternatively, is there any terminal emulator that allows it? Note: This question is posted here because the problem focuses on the terminal itself, not on the rendering process.

I installed the solarized theme for vim but it looks quite ugly. The documentation says, that I should also enable the solarized theme in my terminal, which is the LXTerminal. Therefore I tried to setup my terminal via ~/.Xresources with solarized/xresources but it has no effect. How can I setup the solarized color scheme for LXTerminal?

debian8 is a standard user on my OS (Debian8+LXDE). I follow below steps to change the font on LXterminal. 1. Launch LXterminal after logging in as debian8. 2. Click Edit > Preferences. 3. The default font size is 10 px, which is small. 4. I change the font size to 14 px. 5. Click OK to apply the changes. Unfortunately, when the computer is restarted, the font size for user debian8 reverts to 10px regardless of the font size chosen before restart. Why is that so? Is there a script which can be saved on /home/debian8/.bashrc to set font size for user debian8?