Bugzilla – Bug 666429
Check responsiveness for the software management application before download timeout
Last modified: 2015-03-12 12:29:43 UTC
I have tried to update the components for the software "tomcat6" once more with the software management tool from within my KDE session. I became used to the situation that this update process is mostly fast. Now I wondered why the progress bars did not change because of the download try for the package "tomcat6-servlet-2_5-api 6.0.29-37.2" for a while. I would appreciate if I can activate a corresponding log control widget to see potential connection problems for the corresponding installation source. I have tried to skip this part. I pressed the button "Cancel" and it took an unexpectedly long while until the following German text was displayed in a message box. "Fehler Herunterladen fehlgeschlagen: Dateiabruf durch Benutzer unterbrochen Verlauf: - [AbstractCommand.cc:211] Zeitüberschreitung" It seems that I stumbled over another open issue. The application window closed suddenly after an update retry for my installation source "openSUSE BuildService - Java". Are there any chances to improve the handling of download time-outs?
The script "save_y2logs" produced the result "/home/elfring/Projekte/YaST/y2logs20110123.tbz". http://en.opensuse.org/openSUSE:Report_a_YaST_bug#I_reported_a_YaST2_bug.2C_and_now_I_am_asked_to_.22attach_y2logs.22._What_does_that_mean.2C_and_how_do_I_do_that.3F The file size is 11.2 MB now. Unfortunately, this value is bigger than your upload size limit for attachments.
There are some problems with aria which are fixed for 11.4. Workaround: export ZYPP_ARIA2C=0 (or remove/rename the /usr/bin/aria2c binary. Removing the aria2 package fails because libzypp still requires it). libzypp will fallback to libcurl then. On 11.4 a libcurl based implementation supporting zsync and metalink will replace aria2 as default downloader. *** This bug has been marked as a duplicate of bug 555803 ***
(In reply to comment #2) Thanks for your informations. Now I have renamed the download manager program to "/usr/bin/aria2c-11_3". But I find that my issue is not completely resolved so far. 1. How do you think about my feature request? 2. Do the open issues with the current tool "aria2" explain the unexpected close of the application window after the mentioned status display in the message box?
Assigned to zypp maintainer in order to find an answer :-)
Request for a 'log control widget' or closing 'application windows' are IMO UI issues :)
Ladislav, please comment on the UI issues.
Um, I'm little bit confused, what does "log control widget" mean exactly? And "the application window closed suddenly after an update retry" means that yast exited?
(In reply to comment #8) > Um, I'm little bit confused, what does "log control widget" mean exactly? I would appreciate if I can get a bit more feedback on the download activities (from the background) in a direct way by the graphical user interface. > And "the application window closed suddenly after an update retry" means that > yast exited? No. - Only the corresponding software management tool vanished.
(In reply to comment #9) > I would appreciate if I can get a bit more feedback on the download activities > (from the background) in a direct way by the graphical user interface. Um, what exactly is missing? I mean libzypp reports download start/finish and it repeatedly reports progress and download rate. Not sure if libzypp could report something else when there are network/connection problems.
(In reply to comment #10) How do you think about an additional log widget that displays a view with a bit more details about network connection retries and corresponding time-outs to retrieve data from installation sources?
Sorry I do not have time to fix this issue. Moreover adding a logging widget is not a good idea IMHO...