FS#3035 - Default /etc/profile screws up console apps running in xterms

Attached to Project: Arch Linux
Opened by j (archdaemon) - Wednesday, 03 August 2005, 17:19 GMT
Last edited by arjan timmerman (blaasvis) - Wednesday, 02 November 2005, 10:10 GMT
Task Type Bug Report
Category System
Status Closed
Assigned To Judd Vinet (judd)
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Or at least, it seems. There's this in /etc/profile
export COLUMNS LINES
While tin and BitchX weren't bothered by it, lynx and muttng were screwed up in large xterm windows (as though they were in an 80x25 term). I put
unset LINES COLUMNS
in my ~/.xinitrc and the variables were correct in xterms and all apps in question functioned properly. I then removed the lines from both .xinitrc and /etc/profile and the variables were still correct both in console and in X and the apps still functioned properly.

Maybe I'm misdiagnosing this entirely (I have a knack for that) but this is what seems to be the case. I thought it might be the shopt checkwinsize but having that set or not made no difference.

Can't believe I'm the only one to experience this, though.
This task depends upon

Closed by  Roman Kyrylych (Romashka)
Thursday, 30 November 2006, 23:54 GMT
Reason for closing:  Fixed
Comment by arjan timmerman (blaasvis) - Sunday, 26 March 2006, 12:29 GMT
hmmm i can't reproduce this with the latest bash ?

can you give more details?
Comment by Janne Paalijarvi (usv) - Tuesday, 23 May 2006, 19:27 GMT
I can confirm this on Arch Linux 0.7.2 with current/bash 3.1.17-1 and current/xterm 207-1 . Apps like cplay or alsamixer get messed up if COLUMNS LINES is set. Commenting out 'export COLUMNS LINES' from /etc/profile resolves this.
Comment by Roman Kyrylych (Romashka) - Monday, 16 October 2006, 08:46 GMT
Have you tried it in VTE-based terminals (gnome-terminal, Terminal, Sakura), Konsole, rxvt?
Comment by Roman Kyrylych (Romashka) - Saturday, 25 November 2006, 13:18 GMT
Is this issue still valid?
Comment by Janne Paalijarvi (usv) - Thursday, 30 November 2006, 23:02 GMT
It seems that the issue has been resolved now.

Loading...