You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just noticed this minor display issue. It doesn't affect the wipe process, it's more to do if you run nwipe then abort using Control C before initiating a wipe. You will only see it on a high resolution monitor with default text mode set at full screen (as in the latest ShredOS), but not in low res 80 x 30 console windows.
First scenario:
You start nwipe then change your mind and type control C to exit. If you have not selected any drives the main window simply turns blue and contains no text. Program exits. There is no summary table or error table, which is to be expected because no wipe was ever started. This is how it should be.
Second scenario: (the issue)
You start nwipe then select one or more drives, unlike in the first scenerio, but you still do not start a wipe, then you Control C to exit. In the main nwipe window, for less than a second, a message appears that says /dev/sdx 100% complete, if you blink you will miss it. Nwipe then exits. Basically a spurious message appears. The last line of the log states that "Nwipe was aborted by the user prior to the wipe starting". There is no summary table or error table, which is to be expected because no wipe was ever started. So the bug is simply that spurious message that flashes onto the screen for less than a second and then disappears saying 100% complete when nothing was ever started. The expected result should be the same as scenario 1. i.e. remove spurious message on control C.
Third scenario:
You start nwipe then select your drives & method, then start the wipe. Change your mind and abort. Main window will correctly show progress up to the point the control C was issued. The summary table says UABORTED (User ABORTED) This is correct and as to be expected.
Summary:
So in summary, a fix is required for the spurious exit message described in the second scenario, while not changing the exit behaviour of the first and third scenarios.
The text was updated successfully, but these errors were encountered:
I just noticed this minor display issue. It doesn't affect the wipe process, it's more to do if you run nwipe then abort using Control C before initiating a wipe. You will only see it on a high resolution monitor with default text mode set at full screen (as in the latest ShredOS), but not in low res 80 x 30 console windows.
First scenario:
You start nwipe then change your mind and type control C to exit. If you have not selected any drives the main window simply turns blue and contains no text. Program exits. There is no summary table or error table, which is to be expected because no wipe was ever started. This is how it should be.
Second scenario: (the issue)
You start nwipe then select one or more drives, unlike in the first scenerio, but you still do not start a wipe, then you Control C to exit. In the main nwipe window, for less than a second, a message appears that says /dev/sdx 100% complete, if you blink you will miss it. Nwipe then exits. Basically a spurious message appears. The last line of the log states that "Nwipe was aborted by the user prior to the wipe starting". There is no summary table or error table, which is to be expected because no wipe was ever started. So the bug is simply that spurious message that flashes onto the screen for less than a second and then disappears saying 100% complete when nothing was ever started. The expected result should be the same as scenario 1. i.e. remove spurious message on control C.
Third scenario:
You start nwipe then select your drives & method, then start the wipe. Change your mind and abort. Main window will correctly show progress up to the point the control C was issued. The summary table says UABORTED (User ABORTED) This is correct and as to be expected.
Summary:
So in summary, a fix is required for the spurious exit message described in the second scenario, while not changing the exit behaviour of the first and third scenarios.
The text was updated successfully, but these errors were encountered: