Bug 298827

Summary: sw_single: MediaException warning text is unhelpful
Product: [openSUSE] openSUSE 10.3 Reporter: Stanislav Brabec <sbrabec>
Component: libzyppAssignee: Michael Andres <ma>
Status: RESOLVED FIXED QA Contact: Klaus Kämpf <kkaempf>
Severity: Normal    
Priority: P5 - None CC: jsuchome, nospamm
Version: Beta 1   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: failed.png
KDE-Yast2-Error on refreshin repositories

Description Stanislav Brabec 2007-08-09 13:41:08 UTC 
Attached screenshot of error describes situation, when error occurs in one of repositories. Due to concatenation of names, users have no idea, which repository is failing.
Comment 1 Stanislav Brabec 2007-08-09 13:41:55 UTC 
Created attachment 156491 [details]
failed.png
Comment 2 Michael Meeks 2007-08-10 13:40:51 UTC 
Hi Stanislav - do you mean truncation of names ? ultimately, the yast2-gtk dialog code itself will not truncate the error - and this dialog is not created by yast2-gtk (at all).

ie. this looks like a pure sw_single / YCP mis-feature in /usr/share/YaST2/modules/PackageCallbacks.ycp (DoneDownload)

It'd also be really useful to get the relevant yast log files if you could dig them out ?

Thanks.
Comment 3 Peter Buschbacher 2007-08-10 19:04:04 UTC 
On KDE the situation is the same. You even only get the error message, without having an idea of what repo failed and why. I'd like to have one big persistent popup for all messages while refreshing repos.

Peter Buschbacher
Comment 4 Peter Buschbacher 2007-08-10 19:06:24 UTC 
Created attachment 156863 [details]
KDE-Yast2-Error on refreshin repositories
Comment 5 Peter Buschbacher 2007-08-10 22:36:13 UTC 
created own Bug 299532 - "yast2 software management - permanent pop-up for all relevant messages"
Comment 6 Jiří Suchomel 2007-08-13 07:26:54 UTC 
Ladislav, looks like YaST doesn't show all error data it has from libzypp. Please check the place where this is used.

(BTW, the bug caused the error is probably already fixed)
Comment 7 Ladislav Slezák 2007-08-13 15:21:11 UTC 
String "Media Exception" is passed from libzypp in zypp::media::DownloadProgressReport.finish() callback.
Comment 8 Stanislav Visnovsky 2007-08-29 11:22:18 UTC 
The details about the exception should be shown now. However, the
shortening of the path will still happen.

I suggest to put the repository name into the message - this is then a clear enhancement.
Comment 10 Michael Andres 2008-07-10 11:18:52 UTC 
The solution for 11.0 is IMO better, although it could still be improved. The problem is that zypp::media::DownloadProgressReport is a generic report triggered by the media backend whenever some file is downloaded. 

We don't have any context information at that level, telling whether this download is part of a repo refresh or providing a package for installation or....


But now after reporting the media error, yast shows a summary telling which repo failed:

     There was an error in the repository initialization.
     'update-11.0': Valid metadata not found at specified URL(s)
     History:
     - SKIP reqest: User-requested skipping of a file
     - File '/repodata/repomd.xml' not found on medium 
       'http://download.opensuse.org/update/11.0a'