GParted will not work whenever computer's primary drive is troubled
Hello; Didn't see this issue in Bugs, so... I managed to mess up the computer's primary storage device (laptop HD). Thereafter , any attempts to use GParted from the UI Menu, have become useless. After invocation ion, the GParted window appears, and displays the fact that it is 'Searching /dev/sd[a-?] partitions at the bottom of the window. As the light on the computer's drive is lit, it would appear that GParted does make an attempt to gain interaction with it. At the conc lusion, a pop up window appears on the UI, whose window label is entitled "Libpart ed Error", and the error within the widow states "Input/Output error during read on /dev/sdb" And, at the bottom of the pop up are 3 selections; 'Retry', 'Cancel', and 'Ignore' . From there it is then not possible to regain interactive control with GParted, a nd all of the associated processes must be 'killed' in order to remove it from sit e.
The bug that I therefore submit, is that the application should continue to work u nder such a condition. Either make the Ignore selection functional, or more simply , do not ask the user for any feedback as to how to proceed; and then continue on in a normal fashion, working with the other devices with which it is able to have such abilities.
This situation occurs via the booting, and logging in from other external devices, to which I have installed persistent versions of (l)ubuntu v18.04.