Bug 684849 - newwin regression
Summary: newwin regression
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: ncurses
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Miroslav Lichvar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 684854
TreeView+ depends on / blocked
 
Reported: 2011-03-14 16:24 UTC by Jaroslav Škarvada
Modified: 2011-03-31 20:11 UTC (History)
2 users (show)

Fixed In Version: ncurses-5.8-2.20110319.fc15
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-31 20:11:18 UTC


Attachments (Terms of Use)
Proposed fix (602 bytes, patch)
2011-03-14 16:24 UTC, Jaroslav Škarvada
no flags Details | Diff

Description Jaroslav Škarvada 2011-03-14 16:24:55 UTC
Created attachment 484246 [details]
Proposed fix

Description of problem:
The newwin(0,0,0,0) doesn't work, but it should according to man page:
> A new full-screen window is created by calling newwin(0,0,0,0)

Version-Release number of selected component (if applicable):
ncurses-5.8-1.fc15.x86_64

How reproducible:
Always

Steps to Reproduce:
1. yum install powertop
2. powertop
  
Actual results:
There is no tab-bar.

Expected results:
There should be tab-bar.

Additional info:
Apparently this is a regression because the code for auto-detection of window size is still there, but by-passed.

Comment 1 Thomas E. Dickey 2011-03-21 21:16:30 UTC
See

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=616711

I'm considering a 5.9 with this fix, plus the post-5.8
fixes for the Ada95 binding.

Comment 2 Fedora Update System 2011-03-22 15:28:32 UTC
ncurses-5.8-2.20110319.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/ncurses-5.8-2.20110319.fc15

Comment 3 Fedora Update System 2011-03-31 20:11:13 UTC
ncurses-5.8-2.20110319.fc15 has been pushed to the Fedora 15 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.