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.