[Bug 537883] New: YaST Package Management UI becomes unresponsive if a network repository is unavailable
http://bugzilla.novell.com/show_bug.cgi?id=537883 Summary: YaST Package Management UI becomes unresponsive if a network repository is unavailable Classification: openSUSE Product: openSUSE 11.2 Version: Milestone 6 Platform: PC OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: malv_star@hotmail.com QAContact: jsrain@novell.com Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9.1.2) Gecko/20090730 SUSE/3.5.2-1.2 Firefox/3.5.2 The YaST package management system will attempt to refresh those repositories marked as "refresh" when a user starts the "Software Management" or "Online Update" components. If one or more of those repositories is unavailable (causing a network timeout), the user is never able to abort the program during the attempted refresh. For users with large repository collections this could cause long wait times before they are able to exit cleanly. Reproducible: Always Steps to Reproduce: 1. Ensure that at least one network repository marked for refresh is unavailable 2. Start the "Online Update" component in YaST 3. Attempt to click "Abort" while the program is trying to refresh. Actual Results: YaST completely ignores any user attempt to click on "Abort" during the network timeout. The button appears in the UI, but is essentially inaccessible. The user is presented with the option to skip the refresh this time around, but not to prevent the entire software management system from launching. The "Abort" button is therefore entirely superfluous in the event of network timeouts. Expected Results: The abort button should be accessible and allow the user to prevent the software management interface from launching. If the user does not skip the autorefresh (an option they are presented with after the first repository fails to respond), they must wait for the next repository to timeout, skip all refresh attempts and then wait for the software management UI to load before they are able to abort the software installation procedure. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=537883 User malv_star@hotmail.com added comment http://bugzilla.novell.com/show_bug.cgi?id=537883#c1 Malvern Star <malv_star@hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|Milestone 6 |Milestone 7 --- Comment #1 from Malvern Star <malv_star@hotmail.com> 2009-09-17 09:19:11 MDT --- Bug is still present in Milestone 7. It also appears that it is impossible to press "Abort" during the Installation phase if YaST encounters a network connectivity issue. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=537883 zhu rensheng <rszhu@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rszhu@novell.com AssignedTo|bnc-team-screening@forge.pr |yast2-maintainers@suse.de |ovo.novell.com | -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=537883 User m.munnix@redcross.be added comment http://bugzilla.novell.com/show_bug.cgi?id=537883#c2 michel munnix <m.munnix@redcross.be> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |m.munnix@redcross.be --- Comment #2 from michel munnix <m.munnix@redcross.be> 2009-09-27 11:04:59 MDT --- More, if you have a general network problem (proxy misconfigured, plug pulled): after having reached the timeout trying to refresh the first repository, you get an error message and choose abort, instead of aborting it skips to try to refresh the next repository and so on ... -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=537883 User malv_star@hotmail.com added comment http://bugzilla.novell.com/show_bug.cgi?id=537883#c3 --- Comment #3 from Malvern Star <malv_star@hotmail.com> 2009-09-27 11:31:24 MDT --- Confirmed michel's finding. Abort in such situations where you are able to click it simply skips to the next repository instead of aborting the entire process. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=537883 J. Daniel Schmidt <jdsn@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jdsn@novell.com AssignedTo|yast2-maintainers@suse.de |lslezak@novell.com -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=537883 User lslezak@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=537883#c4 Ladislav Slezak <lslezak@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |ASSIGNED --- Comment #4 from Ladislav Slezak <lslezak@novell.com> 2009-10-05 11:16:10 MDT --- I'm not sure if the bug is in Yast scripts, pkg-bindings or in libzypp backend. I'll have to check that... -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=537883 http://bugzilla.novell.com/show_bug.cgi?id=537883#c5 Malvern Star <malv_star@hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|Milestone 7 |Final --- Comment #5 from Malvern Star <malv_star@hotmail.com> 2009-12-26 17:23:52 UTC --- Bug is still present in final obviously. Has there been any progress on solving the issue? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=537883 http://bugzilla.novell.com/show_bug.cgi?id=537883#c6 --- Comment #6 from Ladislav Slezak <lslezak@novell.com> 2010-01-12 10:57:38 UTC --- Sorry, still no progress. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=537883 http://bugzilla.novell.com/show_bug.cgi?id=537883#c7 --- Comment #7 from Malvern Star <malv_star@hotmail.com> 2010-01-15 05:06:15 UTC --- OK, thanks for the update Ladislav. Any rough ideas where the problem might be? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=537883 http://bugzilla.novell.com/show_bug.cgi?id=537883#c8 Ladislav Slezak <lslezak@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |WONTFIX --- Comment #8 from Ladislav Slezak <lslezak@novell.com> 2010-01-15 07:50:45 UTC --- I guess in curl (libcurl) which is used in libzypp for downloading files. I think that the problem is that libcurl doesn't call any callback when there is no response (it is simply blocked by non-working network connection). See https://bugzilla.novell.com/show_bug.cgi?id=447567#c6 for more details. I'm resolving it is WONTFIX - it's out of Yast scope and I'm not sure if such a change in libcurl is possible. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=537883 http://bugzilla.novell.com/show_bug.cgi?id=537883#c9 --- Comment #9 from Malvern Star <malv_star@hotmail.com> 2010-01-23 09:03:54 UTC --- Hold on a second. This bug isn't about the "refresh" issue. If you read my original bug report, you'll see the point I was trying to make was that clicking "Abort" does nothing. Clicking "Abort" should IMMEDIATELY kill all related processes. It does not. This can be fixed without relation to libcurl as it should simply kill all child processes started by the refresh. In short, this can be fixed. I would appreciate it if you would re-open the bug. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=537883 http://bugzilla.novell.com/show_bug.cgi?id=537883#c10 Ladislav Slezak <lslezak@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |lslezak@novell.com Component|YaST2 |libzypp Resolution|WONTFIX | AssignedTo|lslezak@novell.com |zypp-maintainers@forge.prov | |o.novell.com QAContact|jsrain@novell.com |qa@suse.de --- Comment #10 from Ladislav Slezak <lslezak@novell.com> 2010-01-25 15:00:10 UTC --- I can only reopen it and reassign it to libzypp developers. Yast only watches for callbacks events from libzypp while installing packages. If there is no callback for a long time yast cannot do anything because the program control is in libzypp (yast code is not running at that time). For immediate [Abort] functionality libzypp must call the progress callback at least once per second. Which probably means that the download code must run in a separate thread/process so it doesn't block. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=537883 http://bugzilla.novell.com/show_bug.cgi?id=537883#c11 Ján Kupec <jkupec@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jkupec@novell.com --- Comment #11 from Ján Kupec <jkupec@novell.com> 2010-01-26 09:36:53 UTC --- My first thought was this is a UI thing. But second thought, it might be really better to do this in libzypp. Do the network operations in a thread, and report the status more often, so that the UI can abort when requested, or report 'still trying to connect...' and things like that. OTOH i don't recall aria2c ever hanging without reporting progress. And since aria is now the default downloader, we might as well stop worrying about curl. The only thing missing in MediaAria2c is the abort handling, but that's a peace of cake. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=537883 http://bugzilla.novell.com/show_bug.cgi?id=537883#c12 --- Comment #12 from Ján Kupec <jkupec@novell.com> 2010-01-26 09:43:16 UTC --- Malven, to your comment #7 from bug 447567:
... but clicking "Abort" does nothing either if the repository is unavailable. Surely this could easily be fixed by just having the abort button kill all child processes immediately?
Well, it could, if yast would actually run any child processes. But it does not. It just calls a library (libzypp), and that library does not respond. So the solution is either to make the lib respond more often, or yast must call the download functions in separate thread. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=537883 http://bugzilla.novell.com/show_bug.cgi?id=537883#c13 --- Comment #13 from Malvern Star <malv_star@hotmail.com> 2010-01-27 09:41:27 UTC --- Ah, sorry for the misunderstanding there Jan. I could have sworn older versions created several child processes. I just assumed the current version did the same thing. If you think it should be fairly simple, I'd love to see this incredibly frustrating bug fixed. Thanks. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=537883 http://bugzilla.novell.com/show_bug.cgi?id=537883#c14 --- Comment #14 from Ján Kupec <jkupec@novell.com> 2010-01-28 15:29:57 UTC --- @ma: what do you think about running some operations, like the curl downloads, in new threads (c#11)? Another potential candidate for this is the building of the @System.solv, which also takes all ranges of time, without any report. Or should we avoid this and leave it on the UIs? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=537883 http://bugzilla.novell.com/show_bug.cgi?id=537883#c15 --- Comment #15 from Ladislav Slezak <lslezak@novell.com> 2010-01-28 16:07:04 UTC --- Building @System.solv is not that critical. Network can be down forever while building @System.solv is finished in finite time :-) It usually takes few seconds, that's OK. I have never seen any complain about that. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=537883 http://bugzilla.novell.com/show_bug.cgi?id=537883#c16 Michael Andres <ma@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ma@novell.com --- Comment #16 from Michael Andres <ma@novell.com> 2010-02-03 11:40:11 UTC --- (In reply to comment #14)
@ma: what do you think about running some operations, like the curl downloads, in new threads (c#11)? Another potential candidate for this is the building of the @System.solv, which also takes all ranges of time, without any report. Or should we avoid this and leave it on the UIs?
@System.solv: The missing progress is my fault. I lost bug #438622. I'll fix that ASAP. @curl: We are far from being thread safe (but we'll improve this for 11.3). Nevertheless it could be possible to run curl_perform in a thread and do a timed_join to guarantee at least one callback per second. Only join loop and curl callback need to be synchronized. But what I don't know, is how to cleanly abort the other threads curl_perform that's waiting for a connect/data, if the timed callback says 'ABORT'. A commandline tool like aria2c is far easier to handle. You can do a timed read on the pipe, and kill it in case of abort. Maybe it's an option to use 'curl' instead of 'libcurl' in the future. This could also ease the task to implement parallel downloads, which is one of the tops for 11.3. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=537883 http://bugzilla.novell.com/show_bug.cgi?id=537883#c17 Malvern Star <malv_star@hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|libzypp |libzypp Version|Final |Milestone 5 Product|openSUSE 11.2 |openSUSE 11.3 --- Comment #17 from Malvern Star <malv_star@hotmail.com> 2010-04-15 13:23:37 UTC --- Any chance of a fix for this making it into SuSE 11.3? I'm updating the bug to SuSE 11.3 Milestone 5 in hopes it will be fixed for final. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=537883 http://bugzilla.novell.com/show_bug.cgi?id=537883#c18 Malvern Star <malv_star@hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|Milestone 5 |Milestone 6 --- Comment #18 from Malvern Star <malv_star@hotmail.com> 2010-05-02 10:20:29 UTC --- Same again, but still present in Milestone 6. No progress? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=537883 http://bugzilla.novell.com/show_bug.cgi?id=537883#c19 Malvern Star <malv_star@hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- OS/Version|Other |openSUSE 11.3 --- Comment #19 from Malvern Star <malv_star@hotmail.com> 2010-05-02 10:23:16 UTC --- Just moving this to the correct platform. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=537883 http://bugzilla.novell.com/show_bug.cgi?id=537883#c20 Malvern Star <malv_star@hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|Milestone 6 |RC 2 --- Comment #20 from Malvern Star <malv_star@hotmail.com> 2010-07-12 10:55:55 UTC --- Bug is still present in openSuSE 11.3 RC2. Does anyone have an idea on how to fix this? Last relevant comment is from Michael Andres back in February. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=537883 http://bugzilla.novell.com/show_bug.cgi?id=537883#c21 Malvern Star <malv_star@hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|RC 2 |Final --- Comment #21 from Malvern Star <malv_star@hotmail.com> 2010-08-07 16:45:25 UTC --- As expected, this problem persists in 11.3 Final (and of course, 11.2). Is there any chance of a fix for this? Is this problem essentially unsolvable due to the architecture of YaST/libzypp? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=537883 http://bugzilla.novell.com/show_bug.cgi?id=537883#c22 --- Comment #22 from Ladislav Slezak <lslezak@novell.com> 2010-08-09 06:15:54 UTC --- Yes, the problem is in the current libzypp architecture. It is solvable, but I'm afraid that it it would require redesign/reimplementation of whole network related code. But Michael Andres should know more... -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=537883 http://bugzilla.novell.com/show_bug.cgi?id=537883#c23 --- Comment #23 from Malvern Star <malv_star@hotmail.com> 2010-08-09 14:13:14 UTC --- Yikes. Well it's not as if this bug actually breaks YaST, so perhaps it would be an idea to implement these changes for openSuSE 12.0 (whenever that is). That is, put it into the longer-term development plan. Thoughts? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=537883 http://bugzilla.novell.com/show_bug.cgi?id=537883#c24 --- Comment #24 from Michael Andres <ma@novell.com> 2010-08-09 17:31:39 CEST --- It's still on the radar, but lack of resources prevented us from fixing it for 11.3. Sorry. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=537883 http://bugzilla.novell.com/show_bug.cgi?id=537883#c25 --- Comment #25 from Malvern Star <malv_star@hotmail.com> 2010-08-09 16:24:42 UTC --- It's all good. Just wanted to find out how it was going. -- Configure bugmail: http://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=537883 https://bugzilla.novell.com/show_bug.cgi?id=537883#c26 Ladislav Slezak <lslezak@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nothereforever@hotmail.com --- Comment #26 from Ladislav Slezak <lslezak@novell.com> 2010-10-18 16:07:54 UTC --- *** Bug 640461 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=640461 -- 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=537883 https://bugzilla.novell.com/show_bug.cgi?id=537883#c27 --- Comment #27 from Ladislav Slezak <lslezak@novell.com> 2010-10-18 16:11:27 UTC --- The abort problem has been already fixed in aria2c downloader (see bnc#545106), but it still present in the libcurl downloader (and that's the problem - libcurl became the default in 11.3). -- 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=537883 https://bugzilla.novell.com/show_bug.cgi?id=537883#c28 Ladislav Slezak <lslezak@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |andrew@joako.net --- Comment #28 from Ladislav Slezak <lslezak@novell.com> 2010-10-18 16:17:53 UTC --- *** Bug 556668 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=556668 -- 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=537883 https://bugzilla.novell.com/show_bug.cgi?id=537883#c29 --- Comment #29 from Michael Schröder <mls@novell.com> 2010-10-18 16:20:55 UTC --- Huh? 11.3 still uses aria2c for downloading. Factory/11.4 uses a new method, MultiCurl, which should do much better. It does DNS lookups in forked processes, for example. -- 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=537883 https://bugzilla.novell.com/show_bug.cgi?id=537883#c30 --- Comment #30 from Ladislav Slezak <lslezak@novell.com> 2010-10-18 16:33:19 UTC --- Yeah, I see. I was confused by MediaCurl in the log, like: 2010-10-18 18:06:25 <1> dhcp22(6648) [zypp] MediaCurl.cc(MediaCurl):394 MediaCurl::MediaCurl(http://download.opensuse.org/distribution/11.3/repo/oss/, ) 2010-10-18 18:06:25 <1> dhcp22(6648) [zypp] MediaAria2c.cc(MediaAria2c):237 MediaAria2c::MediaAria2c(http://download.opensuse.org/distribution/11.3/repo/oss/, ) ... 2010-10-18 18:06:25 <1> dhcp22(6648) [zypp++] ExternalProgram.cc(start_program):221 Executing 'aria2c'.... You are right, aria2c is used... -- 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=537883 https://bugzilla.novell.com/show_bug.cgi?id=537883#c31 --- Comment #31 from Michael Andres <ma@novell.com> 2010-10-21 18:57:37 CEST --- (In reply to comment #27)
The abort problem has been already fixed in aria2c downloader (see bnc#545106), but it still present in the libcurl downloader
I can not reproduce your problem. For me the downloader aborts if the progress callback returns false. As described in bnc#545106, it may be you listen/send using the wrong progress callback. This is fixed in libzypp-7.9.5. It should be possible to abort download via media::DownloadProgressReport as well as via repo::DownloadResolvableReport. The initial problem of course (aria2c hangs uninterruptible in connect) is still unsolved (unless you disable aria2c). -- 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=537883 https://bugzilla.novell.com/show_bug.cgi?id=537883#c32 Michael Andres <ma@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |WONTFIX --- Comment #32 from Michael Andres <ma@novell.com> 2010-11-02 12:51:33 CET --- For 11.4 aria will no longer be the default. For 11.3 one has do disable the aria backend in case of trouble. -- 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.
participants (1)
-
bugzilla_noreply＠novell.com