https://bugzilla.novell.com/show_bug.cgi?id=308603#c2 Jan Kardell changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|jan@mida.se | --- Comment #2 from Jan Kardell 2007-09-08 16:51:34 MST --- Created an attachment (id=162874) --> (https://bugzilla.novell.com/attachment.cgi?id=162874) yast2 logs Logs from a x86_64 system. I have several i586 with identical behavior. I removed a couple of the oldest y2log-x files, the whole blob was to large for bugzilla. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=308603 Klaus Kämpf changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kkaempf@novell.com |dmacvicar@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=308603#c4 Michael Andres changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|ma@novell.com |jsuchome@novell.com --- Comment #4 from Michael Andres 2007-10-30 06:41:29 MST --- @Jiri: Please check, I thought it is already fixed. Providing a package: after sending the 'start()' trigger a sequence of DeltaDownload/DeltaApply/PatchDownload actions may be performed, and lead to the 'finish()' trigger on success. Each Patch/Delta action starts sending it's 'start...()' trigger, followed by 'progress...()'. If the attempt is successfull a 'finish...()' trigger is sent, otherwise 'problem...()' to indicate, that we're going to try something different. This is no error the user should have to confirm, it's just an indication to reset the progress bar as we're starting to try something different. Only if the final attempt to provide the full package fails, reported by a 'problem()' trigger, the user should receive the error popup. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=308603#c6 Michael Andres changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|ma@novell.com | --- Comment #6 from Michael Andres 2007-11-02 06:26:13 MST --- AFAIR we already faced this, so it might be there some fix that didn't make it back into 10.2 branch. But I'm not shure. May even be Ladislav is able to handle this completely inside pkg-bindings/PackageCallbacks.ycp. Inside the DownloadResolvableReport providing some patch.rpm fails. This triggers MediaChangeReport passing MediaChangeReport::NOT_FOUND. But this should not cause any popup to appear. Inside DownloadResolvableReport only MediaChangeReport::WRONG indicating the wrong media is inserted should cause a popup - asking to insert the correct media. Or an error reported in the DoneProvide callback, as this indicates that even downloading the complete package failed. Any other problem reported here is just informal. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=308603 User visnov@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=308603#c8 Stanislav Visnovsky changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |visnov@novell.com Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #8 from Stanislav Visnovsky 2008-04-25 08:19:41 MST --- I believe this is fixed now. Please, reopen if you can reproduce with 11.0. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.