Bug 76217

Summary: characters in document are scrambled (making konsole unusable)
Product: [Applications] konsole Reporter: Richard Bos <richard.bos>
Component: generalAssignee: Konsole Developer <konsole-devel>
Status: RESOLVED FIXED    
Severity: normal    
Priority: NOR    
Version: 1.3   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Richard Bos 2004-02-26 21:38:39 UTC 
Version:           1.3 (using KDE KDE 3.2.0)
Installed from:    SuSE RPMs
OS:          Linux

Since upgrading from kde-3.1.x to kde-3.2.0 including a upgrade of
konsole from 1.2.x to 1.3 I have difficulties to use vi in konsole.

It is a very specific case and probable not reproducable for you, but I really
hope someone is still able to find a fix for the problem described in
more details below, as it makes working with konsole impossible!!!

Start konsole
Select the session menu and select the right machine, in this particular
case a solaris-2.5/6 system.  If I start editing a file with _vi_
pieces in the file are missing!!!
Or if I search in the file for a particular string, the cursor jumps but
not to the desired sting but to somewhere else.

This started after the upgrade to kde-3.2 and it forces me to use emacs
while I'm not fluent with emacs at all.  Or it requires me to use xterm,
and than I have to type the "ssh remote machine" command on the command line
and I miss the tabs!!!

It seems related to the remote machine connection.  I can't remember that I
encountered this problem at my local machine.

Sorry for giving such a vague description of the problem, but it is really
there and it is annoying as ....  I still hope that you can find somehing in
the code that is responsible for it (perhaps the tab method is responsible
for it).
Comment 1 Richard Bos 2004-03-13 22:17:43 UTC 
The problem happens when TERM has been defined as xterm.  If it is
changed to vt100 konsole work normal.
Comment 2 Waldo Bastian 2004-03-13 23:05:06 UTC 
Probably some weird sequence in the terminfo for xterm, I fixed some things there yesterday, can you check if konsole from todays KDE_3_2_BRANCH fixes your problem?

Alternatively, can you send the xterm.terminfo file from the system on which you experience problems?
Comment 3 Waldo Bastian 2004-03-15 13:46:32 UTC 
If you run konsole itself from a terminal, does konsole generate any output when you do something in vi that causes the display to get messed up?
Comment 4 Richard Bos 2004-03-15 22:22:11 UTC 
konsole is very quiet.  There is hardly any output.
As I don't use a compiled version I can't test the
version from KDE_3_2_BRANCH.
Comment 5 Waldo Bastian 2004-10-26 22:07:17 UTC 
Assumed to be fixed in KDE 3.3
Comment 6 Richard Bos 2004-10-26 22:34:04 UTC 
It is not fixed, as I still encounter the problem....
I suspect incorrect geometry to me the rootcause.  Most of my konsoles
are put on display by session-management.  for this reason I don't know the
_exact_ size, but I think it is 79x25 or so...  In this case the file is
showed incorrectly (that is with TERM=VT100).  If I alter konsole's to the
standard size to 80x24(vt100) via konsole's menu, the file is showed correctly.
I discovered this quite recently.  Could this be reason that konsole gets
confused?

I can live with it's current behaviour and the workarounds I have, but it
ain't perfect.
Comment 7 Waldo Bastian 2004-10-26 23:09:08 UTC 
What does "echo $COLUMNS x $LINES" say for problematic konsoles?
Comment 8 Richard Bos 2004-11-03 20:32:04 UTC 
Waldo,

sorry for my late response.  I checked the values the day after you asked
for them,  The result is just "x"...
After I changed the terminal geometry to real vt100, the variables are still
not set.