https://bugzilla.novell.com/show_bug.cgi?id=459548 Summary: ncurses YaST: Cannot save changes to software repositories after refreshing Product: openSUSE 11.1 Version: Final Platform: x86 OS/Version: openSUSE 11.0 Status: NEW Severity: Minor Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: bgmerrell@novell.com QAContact: jsrain@novell.com Found By: Integration Test PROBLEM STATEMENT This bug is for ncurses YaST When a refreshes the software repositories from the "Configured Software Repositories" screen, the user is taken to the "Refreshing Repositories" screen and then returned to the configured software repositories screen after the refresh finishes. The problem is, if the user made a change to configured software repos (for example, disabled a repo), when the user is returned to the configured software repos screen after the refresh, several (and sometimes all) of the function key shortcuts are not displayed. REPRO 1. Run 'yast' from the terminal as root 2. Browse to Software -> Software Repositories 3. Notice that the following function key shortcuts are displayed: F1 Help, F3 Add, F4 Edit, F5 Delete, F6 Refresh, F9 Cancel, F10 OK 3. Disable a repo 4. Go to "Refresh" and select "Refresh All Enabled" RESULTS After the refresh finishes, the only disaplyed fuction key shortcuts are "F1 Help" and "F9 Abort". Sometimes no function key shorcuts are displayed. EXPECTED RESULTS I would expecte the original function key shortcuts to be displayed, that is: F1 Help, F3 Add, F4 Edit, F5 Delete, F6 Refresh, F9 Cancel, F10 OK COMMENTS There are a couple of workarounds: 1. The functions key shortcuts are displayed but they appear to still work 2. The user can expand the height of the terminal until the [OK] and [Cancel] (and other) "buttons" are visible. This could be a general problem in ncurses YaST, this is just the first place I saw it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.