Bug 840672

Summary: module firewall of yast in ncurses only shows startup part
Product: [openSUSE] openSUSE Tumbleweed Reporter: Freek de Kruijf <freek>
Component: YaST2Assignee: Gabriele Mohr <gs>
Status: RESOLVED FIXED QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P5 - None    
Version: 13.1 Milestone 3   
Target Milestone: ---   
Hardware: x86-64   
OS: SUSE Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Freek de Kruijf 2013-09-16 20:55:30 UTC 
User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:22.0) Gecko/20100101 Firefox/22.0

Starting yast as root on a console YaST2 is started in ncurses mode. When selecting the firewall module one can select several subscreens. The default is Start-Up, which is show as it should. However going down to Interfaces, Allowed Services, Masquerading, broadcast, Logging Level and Custom Rules, the subwindow still shows the subwindow of Start-Up.

Reproducible: Always

Steps to Reproduce:
1. Give yast in a root konsole
2. Select Security and Users
3. Select Firewall in the subwindow
4. Press the down arrow to any of the above mentioned items
5. Observe that the subwindow Firewall Configuration: Start-Up does not change
note that the square around the items at the left is redrawn every few seconds.
Actual Results:  
See above

Expected Results:  
Each item chosen in the left panel should have it own subwindow at the right.

The file /var/log/YaST/y2log only gets lines added when choosing Firewall. When going up or down with the arrow buttons, nothing is added to this file.

A bit puzzling lines are:
2013-09-16 22:45:42 <1> eik131(3281) [Ruby] modules/SuSEFirewall.rb:1435 Firewall service is started
2013-09-16 22:45:42 <1> eik131(3281) [ui] YPushButton.cc(setFunctionKey):188 Guessing button role YOKButton for YPushButton "Next" at 0x25612a0 from function key F10
2013-09-16 22:45:42 <1> eik131(3281) [ui] YPushButton.cc(setFunctionKey):188 Guessing button role YCancelButton for YPushButton "Cancel" at 0x25609e0 from function key F9
2013-09-16 22:45:42 <1> eik131(3281) [ui] YPushButton.cc(setFunctionKey):188 Guessing button role YHelpButton for YPushButton "Help" at 0x2951190 from function key F1
2013-09-16 22:45:42 <1> eik131(3281) [ui] YPushButton.cc(setFunctionKey):188 Guessing button role YCancelButton for YPushButton "Abort" at 0x2952080 from function key F9
2013-09-16 22:45:42 <1> eik131(3281) [ui] YPushButton.cc(setFunctionKey):188 Guessing button role YOKButton for YPushButton "Next" at 0x2952860 from function key F10
2013-09-16 22:45:42 <2> eik131(3281) [ncurses] NCTree.cc(DrawPad):511 PadWidget not yet created
2013-09-16 22:45:42 <1> eik131(3281) [ui] YPushButton.cc(setFunctionKey):188 Guessing button role YOKButton for YPushButton "Next" at 0x2952860 from function key F10
2013-09-16 22:45:42 <1> eik131(3281) [ui] YPushButton.cc(setFunctionKey):188 Guessing button role YCancelButton for YPushButton "Cancel" at 0x2952080 from function key F9
2013-09-16 22:45:42 <1> eik131(3281) [Ruby] modules/SuSEFirewall.rb:1433 Checking firewall status...
2013-09-16 22:45:42 <1> eik131(3281) [Ruby] modules/SuSEFirewall.rb:1435 Firewall service is started
Comment 1 Freek de Kruijf 2013-09-17 07:34:16 UTC 
I do not know if it is relevant for this bug, but I observe the following:

eik131:~ # zypper repos
#  | Alias                     | Name                               | Enabled | Refresh
---+---------------------------+------------------------------------+---------+--------
 1 | YaST_Ruby_HEAD            | YaST Ruby HEAD                     | Yes     | Yes    
 2 | openSUSE-13.1-1.17        | openSUSE-13.1-1.17                 | No      | No     
 3 | repo-debug                | openSUSE-13.1-Debug                | Yes     | Yes    
 4 | repo-debug-update         | openSUSE-13.1-Update-Debug         | Yes     | Yes    
 5 | repo-debug-update-non-oss | openSUSE-13.1-Update-Debug-Non-Oss | Yes     | Yes    
 6 | repo-non-oss              | openSUSE-13.1-Non-Oss              | Yes     | Yes    
 7 | repo-oss                  | openSUSE-13.1-Oss                  | Yes     | Yes    
 8 | repo-source               | openSUSE-13.1-Source               | No      | Yes    
 9 | repo-update               | openSUSE-13.1-Update               | Yes     | Yes    
10 | repo-update-non-oss       | openSUSE-13.1-Update-Non-Oss       | Yes     | Yes    
eik131:~ # zypper up
Loading repository data...
Reading installed packages...

The following package updates will NOT be installed:
  flash-player-kde4 libyui-ncurses-pkg5 libyui-qt-pkg5 perl-Bootloader yast2-core yast2-perl-bindings yast2-pkg-bindings 

Nothing to do.
eik131:~ #
Comment 2 Gabriele Mohr 2013-09-17 08:49:30 UTC 
Did you try pressing 'Return' after selecting a new line?
The corresponding sub window should be shown then.
Comment 3 Freek de Kruijf 2013-09-17 11:24:43 UTC 
No. This not what I expect to need to do.
But indeed, when I press Return I get the proper subwindow.
So an acceptable solution would be a warning in the Release Notes, but fixing the bug would be nicer. Lowering the bug to Normal.
Comment 4 Gabriele Mohr 2013-09-18 08:52:31 UTC 
The ncurses behaviour not to show the corresponding sub window immediately is intended. It is like this in all YaST modules which use a list (actually a tree widget) of items on the left with corresponding sub window on the right.
To press Return to activate something is intuitive for a text mode UI. 
The reason for text mode behaviour is that you have to scroll through the list one by one and it might be very time consuming for a sub window to be created and finally to get to the item you are interested in. Only for graphical UIs you have the possibility to click directly on the item you want.
Comment 5 Freek de Kruijf 2013-09-18 09:11:29 UTC 
It is not so intuitive as you mention above. The reason is that going through the menu items on the main page in the left column, immediately shows the sub window. So one would expect this to happen on the next windows as well, at least I do. So I would suggest to show for a short period a dialog with "Press Return to select this Menu Item" if the sub window will only be shown after pressing Return and one arrives at a new item in the list at the left. Any other improvement to enhance the intuitive UI is also OK, like a line on top of the window showing a message like "Select a menu item in the left panel and press Return to enter".
Comment 6 Gabriele Mohr 2013-10-22 11:33:09 UTC 
I will add an additional paragraph to general help of text mode YaST.
Comment 7 Gabriele Mohr 2014-04-02 08:18:05 UTC 
Additional help is added to help popup in menu.rb (package yast2).
Comment 8 Freek de Kruijf 2014-04-02 20:00:09 UTC 
Thanks