Glenn Holmer | 2 Feb 2009 14:38

window size doesn't change for 132 columns

Hi, we've been using tn5250 for years, but now see an issue.  I only
noticed it recently, but it may have started when we switched to Ubuntu
from openSUSE.  We're running 0.17.3-2, installed from the Ubuntu
repositories.

When I go to a screen that should expand to 132 columns, the window
stays the same size.  It always used to expand horizontally to show all
the characters (at the same size as with 80 columns).  F20 does move the
data over, but only to about column 91.

Where should we look for a solution?

--  
____________________________________________________________
Glenn Holmer                          gholmer@...
Software Engineer                        phone: 414-908-1809
Weyco Group, Inc.                          fax: 414-908-1601

--

-- 
This is the Linux 5250 Development Project (LINUX5250) mailing list
To post a message email: LINUX5250@...
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/linux5250
or email: LINUX5250-request@...
Before posting, please take a moment to review the archives
at http://archive.midrange.com/linux5250.

Dave McKenzie | 2 Feb 2009 15:07

Re: window size doesn't change for 132 columns

I see the same problem using openSuSE 11.0.  The problem started a week
or two ago, and I haven't gotten around to trying to debug it.

I haven't made any change to tn5250 since I compiled 0.17.4 on
2008-10-25. The only changes that have happened to my system recently
are openSuSE updates, which I apply when openSuSE checks for them daily.

It looks like something changed recently in openSuSE.  Maybe the same
changes occurred in Ubuntu.

--Dave

Glenn Holmer wrote:
> Hi, we've been using tn5250 for years, but now see an issue.  I only
> noticed it recently, but it may have started when we switched to Ubuntu
> from openSUSE.  We're running 0.17.3-2, installed from the Ubuntu
> repositories.
> 
> When I go to a screen that should expand to 132 columns, the window
> stays the same size.  It always used to expand horizontally to show all
> the characters (at the same size as with 80 columns).  F20 does move the
> data over, but only to about column 91.
> 
> Where should we look for a solution?
> 
> --  
> ____________________________________________________________
> Glenn Holmer                          gholmer@...
> Software Engineer                        phone: 414-908-1809
> Weyco Group, Inc.                          fax: 414-908-1601
(Continue reading)

Brian Hill | 2 Feb 2009 16:13
Picon

Re: window size doesn't change for 132 columns

Dave McKenzie wrote:
> It looks like something changed recently in openSuSE.  Maybe the same
> changes occurred in Ubuntu.
>
> --Dave
>
> Glenn Holmer wrote:
>   
>> When I go to a screen that should expand to 132 columns, the window
>> stays the same size.  It always used to expand horizontally to show all
>> the characters (at the same size as with 80 columns).  F20 does move the
>> data over, but only to about column 91.

I use Kubuntu and a week or two ago there was an update to the xterm
package(s) - that's when I noticed my 132-column screens no longer
automatically re-sized themselves.

I'm afraid I have no insight about fixing the problem, only confirmation
that it's not tn5250 that caused the problem but a change in the
underlying terminal software.
--

-- 
This is the Linux 5250 Development Project (LINUX5250) mailing list
To post a message email: LINUX5250@...
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/linux5250
or email: LINUX5250-request@...
Before posting, please take a moment to review the archives
at http://archive.midrange.com/linux5250.

(Continue reading)

Carey Evans | 3 Feb 2009 00:36
Picon
Favicon
Gravatar

Re: window size doesn't change for 132 columns

The security vulnerability that triggered this is listed here:
  http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2008-2383

and the xterm changelog entry for it is here:

  http://invisible-island.net/xterm/xterm.log.html#xterm_238

It looks like we need to add the lines below to the bottom of
/usr/share/tn5250/XTerm, or wherever it gets installed, although I don't
know if this will work with all the patched versions of xterm:

xt5250.VT100*allowWindowOps: True
xt5250.VT100*allowFontOps: True
--

-- 
This is the Linux 5250 Development Project (LINUX5250) mailing list
To post a message email: LINUX5250@...
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/linux5250
or email: LINUX5250-request@...
Before posting, please take a moment to review the archives
at http://archive.midrange.com/linux5250.

Dave McKenzie | 3 Feb 2009 02:26

Re: window size doesn't change for 132 columns

I added the two lines to my ~/.Xdefaults and it fixed the problem.

This is tn5250 0.17.4 on openSuSE 11.0.  The xterm package is
xterm-235-12.2, built on 2009/01/07.

Thanks.

--Dave

Carey Evans wrote:
> The security vulnerability that triggered this is listed here:
>   http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2008-2383
> 
> and the xterm changelog entry for it is here:
> 
>   http://invisible-island.net/xterm/xterm.log.html#xterm_238
> 
> It looks like we need to add the lines below to the bottom of
> /usr/share/tn5250/XTerm, or wherever it gets installed, although I don't
> know if this will work with all the patched versions of xterm:
> 
> xt5250.VT100*allowWindowOps: True
> xt5250.VT100*allowFontOps: True
--

-- 
This is the Linux 5250 Development Project (LINUX5250) mailing list
To post a message email: LINUX5250@...
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/linux5250
or email: LINUX5250-request@...
Before posting, please take a moment to review the archives
(Continue reading)

Brian Hill | 3 Feb 2009 04:46
Picon

Re: window size doesn't change for 132 columns

Carey Evans wrote:
> It looks like we need to add the lines below to the bottom of
> /usr/share/tn5250/XTerm, or wherever it gets installed, although I don't
> know if this will work with all the patched versions of xterm:
>
> xt5250.VT100*allowWindowOps: True
> xt5250.VT100*allowFontOps: True
This worked on my Kubuntu 8.04 system.  (xterm 229-1ubuntu1.1 and tn5250
0.17.3 - both from the repositories).

Thank you Carey!

--

-- 
This is the Linux 5250 Development Project (LINUX5250) mailing list
To post a message email: LINUX5250@...
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/linux5250
or email: LINUX5250-request@...
Before posting, please take a moment to review the archives
at http://archive.midrange.com/linux5250.

Glenn Holmer | 3 Feb 2009 14:39

Re: window size doesn't change for 132 columns

On Tue, 2009-02-03 at 12:36 +1300, Carey Evans wrote:
> The security vulnerability that triggered this is listed here:
>   http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2008-2383
> 
> and the xterm changelog entry for it is here:
> 
>   http://invisible-island.net/xterm/xterm.log.html#xterm_238
> 
> It looks like we need to add the lines below to the bottom of
> /usr/share/tn5250/XTerm, or wherever it gets installed, although I don't
> know if this will work with all the patched versions of xterm:
> 
> xt5250.VT100*allowWindowOps: True
> xt5250.VT100*allowFontOps: True

Thanks, that fixes it on Ubuntu 8.04 (GNOME) as well.  It's great to
have this terminal emulator, it's one of those things you use every day
and never give a thought to until something like this comes up.

-- 
____________________________________________________________
Glenn Holmer                          gholmer@...
Software Engineer                        phone: 414-908-1809
Weyco Group, Inc.                          fax: 414-908-1601

--

-- 
This is the Linux 5250 Development Project (LINUX5250) mailing list
To post a message email: LINUX5250@...
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/linux5250
(Continue reading)

Ken Koehler | 12 Feb 2009 17:02
Picon

Windows Issues 2 and 3 - Copy and Resize Height

   I am using the Windows version of v0.17.4 exclusively. I've run into 3
   problems.

   1) Using "+resize_fonts" there is a problem when the system switches
   between 80 and 132 column. The resizing progressively creeps with each
   switch.

   2) You can copy outsize the limits of the screen data, thereby causing the
   program to abort.

   3) When you manually resize beyond a certain height it'll flip-out and
   make the bottom of the window extend below the desktop.

   Per Scott Klement I'm submitting my changes to win32\winterm.c in unified
   diff format.

   Issue #1 is very complex and I'll address it in it's own posting.
   Below I'm addressing issues #2 and #3.

   For #2 I imposed a MIN function to prevent the copy from attempting to
   read outside the screen buffer limits.
   For #3 I just had to straighten out the number of rows used in passing
   parameters.
    - When dealing with the 5250 screen buffer it should be 80x24 and 132x27.
    - When dealing with display sizing you want 1 greater row to allow for
   the status line, therefore 80x(24+1) and 132x(27+1).
   Some of the sizing was passed as 24 and some as 25 rows so the routines
   fought in a loop.
   I #define'd the row values to minimize this confusion in the future.

(Continue reading)

Ken Koehler | 21 Feb 2009 19:15
Picon

Windows Issue 4 - Aborts under WinXP

   A user was having problems where TN5250 v0.17.4 aborted reguarly.
   After grilling the user, getting a trace from his session and googling for
   WinXP and BitBlt, where the error ocurrs, I figured it all out.

   In short: WinXP "protects" the screen while Ctr-Alt-Del panel shows, when
   manually Locked by the user, when screensaver prompts for password. While
   protected WinXP issues constant WM_PAINT events to the application. When
   TN5250 tries to repaint the screen WinXP punishes it for trying to write
   to a protected screen (BitBlt fails with 6 Invalid Handle). When the
   screen is no longer protected everything works fine again.

   I'm new to Windows screen handling so I'm not sure what the best way to
   handle this is.
   - Looping forever with a Sleep() worked fine but that doesn't sound like
   good programming.
   - Bailing from the above loop and ignoring the error worked fine. Sounds
   sloppy.
   - Bail out of the WM_PAINT (winterm.c) with a non-zero return code. Sounds
   most proper but I can't even try that till next week.

   Does someone with windows screen handling experience have advice on the
   most proper way of correcting the problem?

   ------- Click on this link, and when the site opens, click on the purple
   box that says: Feed an Animal for free.
   http://www.theanimalrescuesite.com
   Verification: http://www.snopes.com/inboxer/charity/animalrescue.asp

    
--

-- 
(Continue reading)


Gmane