[Bug 1135366] New: UX issue when applying changes with Expert Partitioner
http://bugzilla.suse.com/show_bug.cgi?id=1135366 Bug ID: 1135366 Summary: UX issue when applying changes with Expert Partitioner Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers@suse.de Reporter: jlopez@suse.com QA Contact: jsrain@suse.com Found By: --- Blocker: --- When using the Expert Partitioner in an already installed system, the last screen is a summary about all the actions to apply. But once this summary is accepted, the Expert Partitioner is completely closed, and there is no hint about what is happening under the hood. Were all the changes correctly applied? Has it already finished? Or is it still working? No way to know. Maybe there should be an extra step dialog saying something like: "applying changes". If everything was correct, the user would be informed about it, and if anything was wrong, the error would be informed and the user should stay in the Partitioner to try another different thing. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1135366 http://bugzilla.suse.com/show_bug.cgi?id=1135366#c1 Martin Vidner <mvidner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://trello.com/c/Xpjm7K | |dr CC| |mvidner@suse.com Assignee|yast2-maintainers@suse.de |yast-internal@suse.de --- Comment #1 from Martin Vidner <mvidner@suse.com> --- I see two distinct parts: 1. showing a progress report while YaST is busy 2. if an error occurs, giving the user the possibility to stay in the module and retry or correct things (1) is standard behavior, we should simply do it (2) is unusual in YaST, only the package manager does it IIRC. It is also problematic in that we would go a different way than the usual 1. initialize everything 2. perform changes (mutate internal state) 3. quit, discarding the state to 1. init 2. mutate 3. report a problem 4. further mutate the problematic state, what could possibly go wrong? Or have I misunderstood and the point is simply to report errors? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1135366 http://bugzilla.suse.com/show_bug.cgi?id=1135366#c2 --- Comment #2 from José Iván López González <jlopez@suse.com> --- (In reply to Martin Vidner from comment #1)
I see two distinct parts:
1. showing a progress report while YaST is busy 2. if an error occurs, giving the user the possibility to stay in the module and retry or correct things
(1) is standard behavior, we should simply do it
(2) is unusual in YaST, only the package manager does it IIRC. It is also problematic in that we would go a different way than the usual 1. initialize everything 2. perform changes (mutate internal state) 3. quit, discarding the state to 1. init 2. mutate 3. report a problem 4. further mutate the problematic state, what could possibly go wrong?
Or have I misunderstood and the point is simply to report errors?
Yes, that is my proposal. I see no problem in the partitioner with the retry thingy. In general (and always talking about an already install system) I would never close the partitioner automatically: * if everything was correctly applied, the user is informed about it and he/she can close or continue editing. * if anything was wrong, the user is informed about it and he/she can close o retry/change things. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1135366 http://bugzilla.suse.com/show_bug.cgi?id=1135366#c3 Knut Alejandro Anderssen González <knut.anderssen@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aschnell@suse.com --- Comment #3 from Knut Alejandro Anderssen González <knut.anderssen@suse.com> --- *** Bug 1155289 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1135366 http://bugzilla.suse.com/show_bug.cgi?id=1135366#c4 José Iván López González <jlopez@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from José Iván López González <jlopez@suse.com> --- Added new dialog to show the progress of the changes. * https://build.opensuse.org/request/show/770001 * https://build.opensuse.org/request/show/769098 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1135366 http://bugzilla.suse.com/show_bug.cgi?id=1135366#c5 Martin Vidner <mvidner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pier_andreit@yahoo.it --- Comment #5 from Martin Vidner <mvidner@suse.com> --- *** Bug 1165841 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com