http://bugzilla.opensuse.org/show_bug.cgi?id=1021291 http://bugzilla.opensuse.org/show_bug.cgi?id=1021291#c4 --- Comment #4 from Dr. Werner Fink --- Created attachment 711291 --> http://bugzilla.opensuse.org/attachment.cgi?id=711291&action=edit xz tar archive of /var/log/YaST2/ as well as /var/log/zypper.log -- You are receiving this mail because: You are on the CC list for the bug.

SET_OPTION(CURLOPT_PROGRESSFUNCTION, &progressCallback ); SET_OPTION(CURLOPT_NOPROGRESS, 0L); Libzypp always sets up a custom progress function, which in turn triggers the yast UI progress callback (DownloadProgressReport). The yast callback may abort

http://bugzilla.opensuse.org/show_bug.cgi?id=1021291 http://bugzilla.opensuse.org/show_bug.cgi?id=1021291#c6 Michael Andres changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |IN_PROGRESS Flags|needinfo?(ma@suse.com) | --- Comment #6 from Michael Andres --- According to the log we wait for curl_easy_perform() to return after having downloaded the requested rpm (http://download.opensuse.org/distribution/leap/42.2/repo/oss/suse/noarch/tex...). the transfer by returning non-zero (e.g. after the user pressed sone abort-button). If I got you right, the UI is not responsive. So we receive no progress callback at all from libcurl. Or we do, and libzypp fails to forward the callback to the UI, which may indeed happen if we detect curl delivering old data. Or the UI hangs and does not return from the callback. We can't tell from the log which case actually happened. I'll fix the zypp callback to make sure actually every progress trigger from curl is forwarded to the UI. This will either make the UI responsive or tell us that curl fails to trigger the callback. As the libcurl transfer timeout is 1h, we currently don't know if curl is hanging or still waiting. -- You are receiving this mail because: You are on the CC list for the bug.