|
Bugzilla – Full Text Bug Listing |
| Summary: | NFS Server - Progress bar doesn't have so many steps | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.2 | Reporter: | Lukas Ocilka <locilka> |
| Component: | YaST2 | Assignee: | Michal Zugec <mzugec> |
| Status: | RESOLVED WONTFIX | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Minor | ||
| Priority: | P5 - None | CC: | jsmeix |
| Version: | Alpha 3 plus | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Lukas Ocilka
2006-08-29 07:57:25 UTC
Yes. This is actually a long standing problem. It is because SuSEFirewall::Write*() is called which has its own progress reporting. It should be wrapped like this:
boolean progress_orig = Progress::set (false);
SuSEFirewall::Write ();
Progress::set (progress_orig);
Modules which need the fix:
mvidner: nfs-client nfs-server tftp-server mail
mzugec: http-server. also, iscsi-server wrongly uses Progress::set(true/false)
jsmeix: scanner possibly too, I cannot tell at the 1st glance
In yast2-scanner I show the firewall progress intentionally to have feedback for unexperienced users when the firewall settings are actually changed because those uses don't know about the good old Unix style "no news are good news" ;-) Johannes, that's wrong because it doesn't follow a YaST style. Nobody complains it this (own firewall steps) is missing. You should rather create _ONE_ step for the entire firewall and handle it by yourself - you never know how many steps the firewall's progress has. There is no higher level progress running when the firewall progress runs. Therefore it doesn't matter for yast2-scanner how many steps the firewall progress shows. But if it is forbidden to show a progress of a subsequent module, I will simply run it in the good old Unix style. I simply disabled showing Progress from SuSEFirewall::Read and SuSEFirewall::Write I have fixed my modules, over to Miso for HTTP and iSCSI. move to later mass reopening all 10.2 LATER+REMIND bugs. close all 10.2 LATER/REMIND bugs as WONTFIX. Reopen yourself if you still plan to work on it. |